Skip to main content

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

Document Type Expired Internet-Draft (tsvwg WG)
Expired & archived
Authors Randall R. Stewart , Michael Tüxen , Irene Ruengeler
Last updated 2022-04-28 (Latest revision 2021-10-25)
Replaces draft-stewart-natsupp-tsvwg, draft-ietf-behave-sctpnat
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Proposed Standard
Formats
Yang Validation 0 errors, 0 warnings
Reviews
Additional resources Yang catalog entry for ietf-nat-sctp@2019-11-18.yang
Yang impact analysis for draft-ietf-tsvwg-natsupp
Mailing list discussion
Stream WG state Waiting for WG Chair Go-Ahead
Revised I-D Needed - Issue raised by WG
Document shepherd Gorry Fairhurst
Shepherd write-up Show Last changed 2020-11-18
IESG IESG state Expired (IESG: Dead)
Action Holders
(None)
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD Martin Duke
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 functions for TCP that allows multiple hosts to reside behind a NAT function and yet share a single IPv4 address, even when two hosts (behind a NAT function) 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 needed for the SCTP endpoints and the mechanisms for NAT functions necessary to provide similar features of NAPT in the single point and multipoint traversal scenario. Finally, a YANG module for SCTP NAT is defined.

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.)