Movatterモバイル変換


[0]ホーム

URL:


Search RFCs

Advanced Search

RFC Editor

RFC 9260

Stream Control Transmission Protocol,June 2022

File formats:

icon for HTMLicon for text fileicon for v3pdficon for XMLicon for inline errata
Also available:XML file for editing
 
Status:
PROPOSED STANDARD
Obsoletes:
RFC 4460,RFC 4960,RFC 6096,RFC 7053,RFC 8540
Authors:
R. Stewart
M. Tüxen
K. Nielsen
Stream:
IETF
Source:
tsvwg (wit)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC9260

Discuss this RFC: Send questions or comments to the mailing listtsvwg@ietf.org

Other actions:View Errata  | Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 9260


Abstract

This document describes the Stream Control Transmission Protocol(SCTP) and obsoletes RFC 4960. It incorporates the specification ofthe chunk flags registry from RFC 6096 and the specification of the Ibit of DATA chunks from RFC 7053. Therefore, RFCs 6096 and 7053 arealso obsoleted by this document. In addition, RFCs 4460 and 8540,which describe errata for SCTP, are obsoleted by this document.

SCTP was originally designed to transport Public Switched TelephoneNetwork (PSTN) signaling messages over IP networks. It is also suitedto be used for other applications, for example, WebRTC.

SCTP is a reliable transport protocol operating on top of aconnectionless packet network, such as IP. It offers the followingservices to its users:

The design of SCTP includes appropriate congestion avoidance behaviorand resistance to flooding and masquerade attacks.


For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.




IABIANAIETFIRTFISEISOCIETF Trust
ReportsPrivacy StatementSite MapContact Us

Advanced Search

[8]ページ先頭

©2009-2026 Movatter.jp