Stream Control Transmission Protocol (SCTP) Network Address Translation Support

The information below is for an old version of the document
Document Type None Internet-Draft (tsvwg WG)
Last updated 2016-01-06 (latest revision 2015-07-05)
Replaces draft-ietf-behave-sctpnat, draft-stewart-natsupp-tsvwg
Stream IETF
Intended RFC status Proposed Standard
Expired & archived
pdf htmlized bibtex
Additional URLs
- Mailing list discussion
Stream WG state (None) (wg milestone: Feb 2020 - Submit 'SCTP NAT Sup... )
Document shepherd No shepherd assigned
IESG IESG state Unknown state
Consensus Boilerplate Unknown
Telechat date
Responsible AD Spencer Dawkins
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


The Stream Control Transmission Protocol (SCTP) provides a reliable communications channel between two end-hosts in many ways similar to the Transmission Control Protocol (TCP). With the widespread deployment of Network Address Translators (NAT), specialized code has been added to NAT for TCP that allows multiple hosts to reside behind a NAT and yet use only a single globally unique IPv4 address, even when two hosts (behind a NAT) choose the same port numbers for their connection. This additional code is sometimes classified as Network Address and Port Translation (NAPT). This document describes the protocol extensions required for the SCTP endpoints and the mechanisms for NATs necessary to provide similar features of NAPT in the single-point and multi-point traversal scenario.


Randall Stewart (
Michael Tüxen (
Irene Ruengeler (

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