RFC 8261: Datagram Transport Layer Security (DTLS) Encapsulation of SCTP Packets
In plain English — editorial summary, not part of the RFC
The Stream Control Transmission Protocol (SCTP) is a transport protocol originally defined to run on top of the network protocols IPv4 or IPv6. This document specifies how SCTP can be used on top of the Datagram Transport Layer Security (DTLS) protocol. Using the encapsulation method described in this document, SCTP is unaware of the protocols being used below DTLS; hence, explicit IP addresses cannot be used in the SCTP control chunks. As a consequence, the SCTP associations carried over DTLS can only be single-homed.
Document record
- Document ID
- RFC8261
- Published
- November 2017
- Authors
- M. Tuexen; R. Stewart; R. Jesup; S. Loreto
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 10
- Also known as
- —
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8260Stream Schedulers and User Message Interleaving for the Stream Control Transmission ProtocolCurrent
November 2017
- RFC 8257Data Center TCP (DCTCP): TCP Congestion Control for Data CentersCurrent
October 2017
- RFC 8267Network File System (NFS) Upper-Layer Binding to RPC-over-RDMA Version 1Current
October 2017
- RFC 8269The ARIA Algorithm and Its Use with the Secure Real-Time Transport Protocol (SRTP)Current
October 2017
- RFC 8275Allowing Inheritable NFSv4 Access Control Entries to Override the UmaskCurrent
December 2017
- RFC 8246HTTP Immutable ResponsesCurrent
September 2017
- RFC 8276File System Extended Attributes in NFSv4Current
December 2017
- RFC 8285A General Mechanism for RTP Header ExtensionsCurrent
October 2017
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?