Stream Control Transmission Protocol
draft-ietf-tsvwg-rfc4960-bis-06
|
| Document |
Type |
|
Active Internet-Draft (tsvwg WG)
|
|
Last updated |
|
2020-07-09
(latest revision 2020-04-07)
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
Proposed Standard
|
|
Formats |
|
plain text
pdf
htmlized (tools)
htmlized
bibtex
|
| Stream |
WG state
|
|
WG Document
(wg milestone:
Sep 2020 - Submit "Stream Contr...
)
|
|
On Agenda |
|
tsvwg at IETF-108
|
|
Document shepherd |
|
Gorry Fairhurst
|
| IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Yes
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
Gorry Fairhurst <gorry@erg.abdn.ac.uk>
|
Network Working Group R. Stewart
Internet-Draft Netflix, Inc.
Obsoletes: 4960 (if approved) M. Tuexen
Intended status: Standards Track Muenster Univ. of Appl. Sciences
Expires: October 9, 2020 K. Nielsen
Kamstrup A/S
April 7, 2020
Stream Control Transmission Protocol
draft-ietf-tsvwg-rfc4960-bis-06
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.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
Stewart, et al. Expires October 9, 2020 [Page 1]
Internet-Draft Stream Control Transmission Protocol April 2020
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 9, 2020.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 5
1.1. Motivation . . . . . . . . . . . . . . . . . . . . . . . 6
1.2. Architectural View of SCTP . . . . . . . . . . . . . . . 6
1.3. Key Terms . . . . . . . . . . . . . . . . . . . . . . . . 7
1.4. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 11
1.5. Functional View of SCTP . . . . . . . . . . . . . . . . . 11
1.5.1. Association Startup and Takedown . . . . . . . . . . 12
1.5.2. Sequenced Delivery within Streams . . . . . . . . . . 13
1.5.3. User Data Fragmentation . . . . . . . . . . . . . . . 13
Stewart, et al. Expires October 9, 2020 [Page 2]
Internet-Draft Stream Control Transmission Protocol April 2020
1.5.4. Acknowledgement and Congestion Avoidance . . . . . . 13
1.5.5. Chunk Bundling . . . . . . . . . . . . . . . . . . . 14
1.5.6. Packet Validation . . . . . . . . . . . . . . . . . . 14
Show full document text