Stream Control Transmission Protocol (SCTP) Network Address Translation Support
draft-ietf-tsvwg-natsupp-12
| Document | Type | Expired Internet-Draft (tsvwg WG) | |
|---|---|---|---|
| Last updated | 2019-01-03 (latest revision 2018-07-02) | ||
| Replaces | draft-stewart-natsupp-tsvwg, draft-ietf-behave-sctpnat | ||
| Stream | IETF | ||
| Intended RFC status | Proposed Standard | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | WG state | WG Document (wg milestone: Apr 2019 - Submit 'SCTP NAT Sup... ) | |
| Document shepherd | Gorry Fairhurst | ||
| IESG | IESG state | Expired (IESG: Dead) | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Spencer Dawkins | ||
| Send notices to | "Gorry Fairhurst" <gorry@erg.abdn.ac.uk> | ||
https://www.ietf.org/archive/id/draft-ietf-tsvwg-natsupp-12.txt
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 Stewart
(randall@lakerest.net)
Michael Tüxen
(tuexen@fh-muenster.de)
Irene Ruengeler
(i.ruengeler@fh-muenster.de)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)