[rfc-dist] RFC 4960 on Stream Control Transmission Protocol

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Fri Sep 21 15:22:17 PDT 2007

A new Request for Comments is now available in online RFC libraries.

        RFC 4960

        Title:      Stream Control Transmission Protocol 
        Author:     R. Stewart, Ed.
        Status:     Standards Track
        Date:       September 2007
        Mailbox:    rrs at cisco.com
        Pages:      152
        Characters: 346022
        Obsoletes:  RFC2960, RFC3309

        I-D Tag:    draft-ietf-tsvwg-2960bis-05.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4960.txt

This document obsoletes RFC 2960 and RFC 3309.  It
describes the Stream Control Transmission Protocol (SCTP).  SCTP is
designed to transport Public Switched Telephone Network (PSTN)
signaling messages over IP networks, but is capable of broader

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

--  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.  [STANDARDS TRACK]

This document is a product of the Transport Area Working Group
Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

The RFC Editor Team
USC/Information Sciences Institute


More information about the rfc-dist mailing list