RFC 5740: NACK-Oriented Reliable Multicast (NORM) Transport Protocol
In plain English — editorial summary, not part of the RFC
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 data objects or streams over generic IP multicast routing and forwarding services. NORM uses a selective, negative acknowledgment mechanism for transport reliability and offers additional protocol mechanisms to allow for operation with minimal a priori coordination among senders and receivers. A congestion control scheme is specified to allow the NORM protocol to fairly share available network bandwidth with other transport protocols such as Transmission Control Protocol (TCP). It is capable of operating with both reciprocal multicast routing 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 of applications or possibly other higher-level transport protocols to utilize its service in different ways. The protocol leverages the use of FEC-based (forward error correction) repair and other IETF Reliable Multicast Transport (RMT) building blocks in its design. This document obsoletes RFC 3940. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5740
- Published
- November 2009
- Authors
- B. Adamson; C. Bormann; M. Handley; J. Macker
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 96
- Also known as
- —
- Obsoletes:
- RFC 3940
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5775Asynchronous Layered Coding (ALC) Protocol InstantiationCurrent
April 2010
- RFC 3695Compact Forward Error Correction (FEC) SchemesObsoleted
February 2004
- RFC 3452Forward Error Correction (FEC) Building BlockObsoleted
December 2002
- RFC 7411Multicast Listener Extensions for Mobile IPv6 (MIPv6) and Proxy Mobile IPv6 (PMIPv6) Fast HandoversCurrent
November 2014
- RFC 3259A Message Bus for Local CoordinationCurrent
May 2002
- RFC 2429RTP Payload Format for the 1998 Version of ITU-T Rec. H.263 Video (H.263+)Obsoleted
October 1998
- RFC 5651Layered Coding Transport (LCT) Building BlockCurrent
October 2009
- RFC 5445Basic Forward Error Correction (FEC) SchemesCurrent
March 2009
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?