Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Obsoletes:

RFC 3940

Authors:

B. Adamson
C. Bormann
M. Handley
J. Macker

Stream:

IETF

Source:

rmt (tsv)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC5740

Discuss this RFC: Send questions or comments to the mailing listrmt@ietf.org

Other actions:View Errata  | Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 5740

Abstract

This document describes the messages and procedures of the Negative-ACKnowledgment (NACK) Oriented Reliable Multicast (NORM) protocol.This protocol can provide end-to-end reliable transport of bulk dataobjects or streams over generic IP multicast routing and forwardingservices. NORM uses a selective, negative acknowledgment mechanismfor transport reliability and offers additional protocol mechanismsto allow for operation with minimal a priori coordination amongsenders and receivers. A congestion control scheme is specified toallow the NORM protocol to fairly share available network bandwidthwith other transport protocols such as Transmission Control Protocol(TCP). It is capable of operating with both reciprocal multicastrouting among senders and receivers and with asymmetric connectivity(possibly a unicast return path) between the senders and receivers.The protocol offers a number of features to allow different types ofapplications or possibly other higher-level transport protocols toutilize its service in different ways. The protocol leverages theuse of FEC-based (forward error correction) repair and other IETFReliable Multicast Transport (RMT) building blocks in its design.This document obsoletes RFC 3940. [STANDARDS-TRACK]

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.