Stream Control Transmission Protocol (SCTP) Network Address Translation Support
draft-ietf-tsvwg-natsupp-22
|
Document |
Type |
|
Active Internet-Draft (tsvwg WG)
|
|
Authors |
|
Randall Stewart
,
Michael Tüxen
,
Irene Ruengeler
|
|
Last updated |
|
2020-11-24
(latest revision 2020-11-16)
|
|
Replaces |
|
draft-ietf-behave-sctpnat, draft-stewart-natsupp-tsvwg
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
Proposed Standard
|
|
Formats |
|
plain text
html
xml
pdf
htmlized (tools)
htmlized
bibtex
|
|
Yang Validation |
|
☯
0 errors, 0 warnings.
draft-ietf-tsvwg-natsupp-22.txt:
xym 0.4.10:
Extracting 'ietf-nat-sctp@2020-11-02.yang'
Removed 0 empty lines
ietf-nat-sctp@2019-11-18.yang:
pyang 2.4.0: pyang --verbose --ietf -p {libs} {model}:
# module search path: a/www/ietf-ftp/yang/rfcmod/:/a/www/ietf-ftp/yang/draftmod/:/a/www/ietf-ftp/yang/ianamod/:/a/www/ietf-ftp/yang/catalogmod/:.:/var/lib/wwwrun/yang/modules:/a/www/ietf-datatracker/7.24.0/env/share/yang/modules
# read ietf-nat-sctp@2019-11-18.yang (CL)
# read /a/www/ietf-datatracker/7.24.0/env/share/yang/modules/ietf/ietf-nat.yang
# read /a/www/ietf-ftp/yang/rfcmod/ietf-nat@2019-01-10.yang
# read /a/www/ietf-datatracker/7.24.0/env/share/yang/modules/ietf/ietf-inet-types.yang
# read /a/www/ietf-ftp/yang/catalogmod/ietf-inet-types@2020-07-06.yang
# read /a/www/ietf-datatracker/7.24.0/env/share/yang/modules/ietf/ietf-yang-types.yang
# read /a/www/ietf-ftp/yang/catalogmod/ietf-yang-types@2020-07-06.yang
# read /a/www/ietf-datatracker/7.24.0/env/share/yang/modules/ietf/ietf-interfaces.yang
# read /a/www/ietf-ftp/yang/rfcmod/ietf-interfaces@2018-02-20.yang
yanglint SO 1.6.7: yanglint --verbose -p {tmplib} -p {rfclib} -p {draftlib} -p {ianalib} -p {cataloglib} {model} -i:
No validation errors
|
|
Reviews |
|
|
|
Additional Resources |
|
|
Stream |
WG state
|
|
Submitted to IESG for Publication
(wg milestone:
Sep 2020 - Submit 'SCTP NAT Sup...
)
|
|
Document shepherd |
|
Gorry Fairhurst
|
|
Shepherd write-up |
|
Show
(last changed 2020-11-18)
|
IESG |
IESG state |
|
AD Evaluation
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
Magnus Westerlund
|
|
Send notices to |
|
"Gorry Fairhurst" <gorry@erg.abdn.ac.uk>
|
Network Working Group R. R. Stewart
Internet-Draft Netflix, Inc.
Intended status: Standards Track M. Tüxen
Expires: 20 May 2021 I. Rüngeler
Münster Univ. of Appl. Sciences
16 November 2020
Stream Control Transmission Protocol (SCTP) Network Address Translation
Support
draft-ietf-tsvwg-natsupp-22
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.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on 20 May 2021.
Stewart, et al. Expires 20 May 2021 [Page 1]
Internet-Draft SCTP NAT Support November 2020
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. Code Components
extracted from this document must include Simplified BSD License text
as described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Motivation and Overview . . . . . . . . . . . . . . . . . . . 6
4.1. SCTP NAT Traversal Scenarios . . . . . . . . . . . . . . 6
4.1.1. Single Point Traversal . . . . . . . . . . . . . . . 7
4.1.2. Multipoint Traversal . . . . . . . . . . . . . . . . 7
4.2. Limitations of Classical NAPT for SCTP . . . . . . . . . 8
4.3. The SCTP-Specific Variant of NAT . . . . . . . . . . . . 8
5. Data Formats . . . . . . . . . . . . . . . . . . . . . . . . 13
5.1. Modified Chunks . . . . . . . . . . . . . . . . . . . . . 13
5.1.1. Extended ABORT Chunk . . . . . . . . . . . . . . . . 13
5.1.2. Extended ERROR Chunk . . . . . . . . . . . . . . . . 14
5.2. New Error Causes . . . . . . . . . . . . . . . . . . . . 14
5.2.1. VTag and Port Number Collision Error Cause . . . . . 14
5.2.2. Missing State Error Cause . . . . . . . . . . . . . . 15
5.2.3. Port Number Collision Error Cause . . . . . . . . . . 15
5.3. New Parameters . . . . . . . . . . . . . . . . . . . . . 16
5.3.1. Disable Restart Parameter . . . . . . . . . . . . . . 16
5.3.2. VTags Parameter . . . . . . . . . . . . . . . . . . . 17
6. Procedures for SCTP Endpoints and NAT Functions . . . . . . . 18
6.1. Association Setup Considerations for Endpoints . . . . . 19
6.2. Handling of Internal Port Number and Verification Tag
Collisions . . . . . . . . . . . . . . . . . . . . . . . 19
6.2.1. NAT Function Considerations . . . . . . . . . . . . . 19
6.2.2. Endpoint Considerations . . . . . . . . . . . . . . . 20
6.3. Handling of Internal Port Number Collisions . . . . . . . 20
Show full document text