Versions: 00 01 02 03 04 draft-ietf-tsvwg-rfcerrata Network Working Group R. Stewart Internet-Draft Netflix, Inc. Intended status: Standards Track M. Tuexen Expires: January 3, Muenster Univ. Sciences K. This document provides deltas to RFC and is organized in a time based way.

Author:Mibei Daramar
Language:English (Spanish)
Published (Last):24 November 2007
PDF File Size:4.48 Mb
ePub File Size:17.69 Mb
Price:Free* [*Free Regsitration Required]

Stewart, Ed. Request for Comments: September Obsoletes: , Category: Standards Track Stream Control Transmission Protocol Status of This Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements.

Please refer to the current edition of the "Internet Official Protocol Standards" STD 1 for the standardization state and status of this protocol.

Distribution of this memo is unlimited. SCTP is a reliable transport protocol operating on top of a connectionless packet network such as IP. It offers the following services to its users: -- acknowledged error-free non-duplicated transfer of user data, -- data fragmentation to conform to discovered path MTU size, -- sequenced delivery of user messages within multiple streams, with an option for order-of-arrival delivery of individual user messages, -- optional bundling of multiple user messages into a single SCTP packet, and -- network-level fault tolerance through supporting of multi-homing at either or both ends of an association.

The design of SCTP includes appropriate congestion avoidance behavior and resistance to flooding and masquerade attacks. Key Terms Association Startup and Takedown Sequenced Delivery within Streams User Data Fragmentation Acknowledgement and Congestion Avoidance Chunk Bundling Packet Validation Path Management Serial Number Arithmetic Changes from RFC Chunk Field Descriptions Reporting of Unrecognized Parameters Initiation INIT Optional or Variable-Length Parameters Invalid Stream Identifier Missing Mandatory Parameter Stale Cookie Error Out of Resource Unresolvable Address Unrecognized Chunk Type Invalid Mandatory Parameter Unrecognized Parameters No User Data Cookie Received While Shutting Down Restart of an Association with New Addresses User-Initiated Abort Protocol Violation Association Initialization Normal Establishment of an Association Handle Stream Parameters Handle Address Parameters Generating State Cookie State Cookie Processing State Cookie Authentication An Example of Normal Association Establishment An Example of a Association Restart Other Initialization Issues Selection of Tag Value Path Verification User Data Transfer Management of Retransmission Timer RTO Calculation Retransmission Timer Rules Handle T3-rtx Expiration Failover from an Inactive Destination Address Stream Identifier and Stream Sequence Number Ordered and Unordered Delivery CRC32c Checksum Calculation Fragmentation and Reassembly Congestion Control Congestion Avoidance Fast Retransmit on Gap Reports Path MTU Discovery Fault Management Endpoint Failure Detection Path Failure Detection Path Heartbeat Handle "Out of the Blue" Packets Verification Tag Exceptions in Verification Tag Rules Termination of Association Abort of an Association Shutdown of an Association Interface with Upper Layer Security Considerations Security Objectives Countering Insider Attacks Protecting against Data Corruption in the Network Protecting Confidentiality Protecting against Blind Denial-of-Service Attacks Blind Masquerade Improper Monopolization of Services Network Management Considerations Parameters Necessary per Association i.

Per Transport Address Data General Parameters Needed IANA Considerations Payload Protocol Identifiers Port Numbers Registry Explicit Congestion Notification ICMP Handling Introduction This section explains the reasoning behind the development of the Stream Control Transmission Protocol SCTP , the services it offers, and the basic concepts needed to understand the detailed description of the protocol.

However, an increasing number of recent applications have found TCP too limiting, and have incorporated their own reliable data transfer protocol on top of UDP [ RFC ]. The limitations that users have wished to bypass include the following: -- TCP provides both reliable data transfer and strict order-of- transmission delivery of data.

Some applications need reliable transfer without sequence maintenance, while others would be satisfied with partial ordering of the data. In both of these cases, the head-of-line blocking offered by TCP causes unnecessary delay.

Applications must add their own record marking to delineate their messages, and must make explicit use of the push facility to ensure that a complete message is transferred in a reasonable time. It performs this service within the context of an association between two SCTP endpoints. This section provides a consolidated list of the key terms and their definitions. Each user message occupies its own DATA chunk. Typically, message authentication codes are used between two parties that share a secret key in order to validate information transmitted between these parties.

The term "MAC" has different meanings in different contexts.


Modernizing email and calendars for users and developers

Versions: 00 01 02 03 04 05 Network Working Group R. Stewart Internet-Draft Netflix, Inc. Obsoletes: if approved M. Sciences Expires: September 10, K. SCTP is a reliable transport protocol operating on top of a connectionless packet network such as IP.


Google Network Working Group R. Stewart Internet-Draft Netflix, Inc. Obsoletes: if approved M. Sciences Expires: October 9, K.

Related Articles