RFC 3940: Negative-acknowledgment (NACK)-Oriented Reliable Multicast (NORM) Protocol
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 5740.
Current version: 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 is designed to 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 repair and other IETF reliable multicast transport (RMT) building blocks in its design. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC3940
- Published
- November 2004
- Authors
- B. Adamson; C. Bormann; M. Handley; J. Macker
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- tsv
- Pages
- 80
- Also known as
- —
- Obsoleted by:
- RFC 5740
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3941Negative-Acknowledgment (NACK)-Oriented Reliable Multicast (NORM) Building BlocksObsoleted
November 2004
- RFC 5776Use of Timed Efficient Stream Loss-Tolerant Authentication (TESLA) in the Asynchronous Layered Coding (ALC) and NACK-Oriented Reliable Multicast (NORM) ProtocolsCurrent
April 2010
- RFC 6642RTP Control Protocol (RTCP) Extension for a Third-Party Loss ReportCurrent
June 2012
- RFC 3926FLUTE - File Delivery over Unidirectional TransportObsoleted
October 2004
- RFC 3910The SPIRITS (Services in PSTN requesting Internet Services) ProtocolCurrent
October 2004
- RFC 3980T11 Network Address Authority (NAA) Naming Format for iSCSI Node NamesObsoleted
February 2005
- RFC 3989Middlebox Communications (MIDCOM) Protocol SemanticsObsoleted
February 2005
- RFC 4008Definitions of Managed Objects for Network Address Translators (NAT)Obsoleted
March 2005
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?