RFC 3941: Negative-Acknowledgment (NACK)-Oriented Reliable Multicast (NORM) Building Blocks
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 5401.
Current version: RFC 5401 — Multicast Negative-Acknowledgment (NACK) Building Blocks
In plain English — editorial summary, not part of the RFC
This document discusses the creation of negative-acknowledgment (NACK)-oriented reliable multicast (NORM) protocols. The rationale for NORM goals and assumptions are presented. Technical challenges for NACK-oriented (and in some cases general) reliable multicast protocol operation are identified. These goals and challenges are resolved into a set of functional "building blocks" that address different aspects of NORM protocol operation. It is anticipated that these building blocks will be useful in generating different instantiations of reliable multicast protocols. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC3941
- Published
- November 2004
- Authors
- B. Adamson; C. Bormann; M. Handley; J. Macker
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- tsv
- Pages
- 36
- Also known as
- —
- Obsoleted by:
- RFC 5401
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 3940Negative-acknowledgment (NACK)-Oriented Reliable Multicast (NORM) ProtocolObsoleted
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?