Stream Control Transmission Protocol (SCTP) Network Address Translation
draft-ietf-behave-sctpnat-08
| The information below is for an old version of the document | |||
|---|---|---|---|
| Document | Type | Expired Internet-Draft (behave WG) | |
| Last updated | 2013-08-29 (latest revision 2013-02-25) | ||
| Replaces | draft-stewart-behave-sctpnat | ||
| Replaced by | draft-ietf-tsvwg-natsupp | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | WG state | WG Document | |
| Document shepherd | None | ||
| IESG | IESG state | Expired | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ietf-behave-sctpnat-08.txt
Abstract
Stream Control Transmission Protocol [RFC4960] provides a reliable communications channel between two end-hosts in many ways similar to TCP [RFC0793]. 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 or NAPT. To date, specialized code for SCTP has NOT yet been added to most NATs so that only pure NAT is available. The end result of this is that only one SCTP capable host can be behind a NAT. This document describes an SCTP specific variant of NAT which provides 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.)