Stream Control Transmission Protocol (SCTP) Network Address Translation Support
draft-ietf-tsvwg-natsupp-05

The information below is for an old version of the document
Document Type Expired Internet-Draft (tsvwg WG)
Last updated 2013-08-29 (latest revision 2013-02-25)
Stream IETF
Intended RFC status Proposed Standard
Formats
Expired & archived
plain text pdf html
Stream WG state WG Document Dec 2015
Document shepherd None
IESG IESG state Expired (IESG: Dead)
Telechat date
Responsible AD Spencer Dawkins
Send notices to tsvwg-chairs@tools.ietf.org, draft-ietf-tsvwg-natsupp@tools.ietf.org

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-tsvwg-natsupp-05.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 (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 the protocol extensions required for the SCTP endpoints to help NATs provide similar features of NAPT in the single-point and multi-point traversal scenario.

Authors

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