RFC 6951: UDP Encapsulation of Stream Control Transmission Protocol (SCTP) Packets for End-Host to End-Host Communication
In plain English — editorial summary, not part of the RFC
This document describes a simple method of encapsulating Stream Control Transmission Protocol (SCTP) packets into UDP packets and its limitations. This allows the usage of SCTP in networks with legacy NATs that do not support SCTP. It can also be used to implement SCTP on hosts without directly accessing the IP layer, for example, implementing it as part of the application without requiring special privileges. Please note that this document only describes the functionality required within an SCTP stack to add on UDP encapsulation, providing only those mechanisms for two end-hosts to communicate with each other over UDP ports. In particular, it does not provide mechanisms to determine whether UDP encapsulation is being used by the peer, nor the mechanisms for determining which remote UDP port number can be used. These functions are out of scope for this document. This document covers only end-hosts and not tunneling (egress or ingress) endpoints.
Document record
- Document ID
- RFC6951
- Published
- May 2013
- Authors
- M. Tuexen; R. Stewart
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 12
- Also known as
- —
- Updated by:
- RFC 8899
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6937Proportional Rate Reduction for TCPObsoleted
May 2013
- RFC 6928Increasing TCP's Initial WindowCurrent
April 2013
- RFC 6994Shared Use of Experimental TCP OptionsCurrent
August 2013
- RFC 6904Encryption of Header Extensions in the Secure Real-time Transport Protocol (SRTP)Current
April 2013
- RFC 7007Update to Remove DVI4 from the Recommended Codecs for the RTP Profile for Audio and Video Conferences with Minimal Control (RTP/AVP)Current
August 2013
- RFC 7022Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names (CNAMEs)Current
September 2013
- RFC 7053SACK-IMMEDIATELY Extension for the Stream Control Transmission ProtocolObsoleted
November 2013
- RFC 6792Guidelines for Use of the RTP Monitoring FrameworkCurrent
November 2012
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?