RFC-Ref is not longer maintained; use RFC browser at: http://zvon.org/comp/r/ref-RFC.html
RFC 2960:Stream Control Transmission Protocol
RFC-Ref

RFC - 2960

Stream Control Transmission Protocol

Original: ftp://ftp.isi.edu/in-notes/rfc2960.txt
Authors: R. Stewart [Motorola], Q. Xie [Motorola], K. Morneault [Cisco], C. Sharp [Cisco], H. Schwarzbauer [Siemens], T. Taylor [Nortel Networks], I. Rytina [Ericsson], M. Kalla [Telcordia], L. Zhang [UCLA], V. Paxson [ACIRI]
Date: October 2000
Category: Proposed Standard



Updated by:
RFC-3309prop Stream Control Transmission Protocol (SCTP) Checksum Change

Referred by: 67 RFC
Refers to: 24 RFC

Status

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.

Copyright Notice

Copyright (C) The Internet Society (2000). All Rights Reserved.

Abstract

This document describes the Stream Control Transmission Protocol (SCTP). SCTP is designed to transport PSTN signaling messages over IP networks, but is capable of broader applications.

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.


About Resource

Google
Web
RFC-Ref