Stream Control Transmission Protocol
draft-ietf-tsvwg-rfc4960-bis-04

Document Type Expired Internet-Draft (tsvwg WG)
Last updated 2020-01-27 (latest revision 2019-07-26)
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream WG state WG Document (wg milestone: Sep 2020 - Submit "Stream Contr... )
Document shepherd Gorry Fairhurst
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to Gorry Fairhurst <gorry@erg.abdn.ac.uk>

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-tsvwg-rfc4960-bis-04.txt

Abstract

This document obsoletes RFC 4960, if approved. 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 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: o acknowledged error-free non-duplicated transfer of user data, o data fragmentation to conform to discovered path MTU size, o sequenced delivery of user messages within multiple streams, with an option for order-of-arrival delivery of individual user messages, o optional bundling of multiple user messages into a single SCTP packet, and o 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.

Authors

Randall Stewart (randall@lakerest.net)
Michael Tüxen (tuexen@fh-muenster.de)
Karen Nielsen (kee@kamstrup.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)