RFC 3940:Negative-acknowledgment (NACK)-Oriented R...
RFC-Ref

Negative-acknowledgment (NACK)-Oriented Reliable Multicast (NORM) Protocol


1. Introduction and Applicability
2. Statement of Intent
2.1. NORM Delivery Service Model
2.2. NORM Scalability
2.3. Environmental Requirements and Considerations
3. Architecture Definition
3.1. Protocol Operation Overview
3.2. Protocol Building Blocks
3.3. Design Tradeoffs
4. Conformance Statement
5. Message Formats
5.1. NORM Common Message Header and Extensions
5.2. Sender Messages
5.2.1. NORM_DATA Message
5.2.2. NORM_INFO Message
5.2.3. NORM_CMD Messages
5.2.3.1. NORM_CMD(FLUSH) Message
5.2.3.2. NORM_CMD(EOT) Message
5.2.3.3. NORM_CMD(SQUELCH) Message
5.2.3.4. NORM_CMD(CC) Message
5.2.3.5. NORM_CMD(REPAIR_ADV) Message
5.2.3.6. NORM_CMD(ACK_REQ) Message
5.2.3.7. NORM_CMD(APPLICATION) Message
5.3. Receiver Messages
5.3.1. NORM_NACK Message
5.3.2. NORM_ACK Message
5.4. General Purpose Messages
5.4.1. NORM_REPORT Message
6. Detailed Protocol Operation
6.1. Sender Initialization and Transmission
6.1.1. Object Segmentation Algorithm
6.2. Receiver Initialization and Reception
6.3. Receiver NACK Procedure
6.4. Sender NACK Processing and Response
6.4.1. Sender Repair State Aggregation
6.4.2. Sender FEC Repair Transmission Strategy
6.4.3. Sender NORM_CMD(SQUELCH) Generation
6.4.4. Sender NORM_CMD(REPAIR_ADV) Generation
6.5. Additional Protocol Mechanisms
6.5.1. Greatest Round-trip Time Collection
6.5.2. NORM Congestion Control Operation
6.5.2.1. NORM_CMD(CC) Transmission
6.5.2.2. NORM_CMD(CC) Feedback Response
6.5.2.3. Congestion Control Rate Adjustment
6.5.3. NORM Positive Acknowledgment Procedure
6.5.4. Group Size Estimate
7. Security Considerations
8. IANA Considerations
9. Suggested Use
10. Acknowledgments (and these are not Negative)
11. References
11.1. Normative References
11.2. Informative References
12. Authors' Addresses
13. Full Copyright Statement
14. Intellectual Property
15. Acknowledgement

Google
Web
RFC-Ref