Stream Control Transmission Protocol (SCTP) Network Address Translation Support
draft-ietf-tsvwg-natsupp-11
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
---|---|---|---|
Authors | Randall R. Stewart , Michael Tüxen , Irene Ruengeler | ||
Last updated | 2018-01-04 (Latest revision 2017-07-03) | ||
Replaces | draft-stewart-natsupp-tsvwg, draft-ietf-behave-sctpnat | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Formats | |||
Reviews |
YANGDOCTORS Early review
(of
-16)
by Radek Krejčí
Ready w/nits
|
||
Additional resources | Mailing list discussion | ||
Stream | WG state | WG Document | |
Document shepherd | Gorry Fairhurst | ||
IESG | IESG state | Expired (IESG: Dead) | |
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | Spencer Dawkins | ||
Send notices to | "Gorry Fairhurst" <gorry@erg.abdn.ac.uk> |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
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.
Authors
Randall R. Stewart
Michael Tüxen
Irene Ruengeler
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)