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

The information below is for an old version of the document
Document Type Active Internet-Draft (tsvwg WG)
Last updated 2012-10-21
Stream IETF
Intended RFC status Proposed Standard
Formats pdf htmlized bibtex
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists (IESG: Dead)
Consensus Boilerplate Unknown
Telechat date
Responsible AD Martin Stiemerling
Send notices to tsvwg-chairs@tools.ietf.org, draft-ietf-tsvwg-natsupp@tools.ietf.org
Network Working Group                                         R. Stewart
Internet-Draft                                            Adara Networks
Intended status: Standards Track                               M. Tuexen
Expires: April 24, 2013                                     I. Ruengeler
                                        Muenster Univ. of Appl. Sciences
                                                        October 21, 2012

Stream Control Transmission Protocol (SCTP) Network Address Translation
                                Support
                    draft-ietf-tsvwg-natsupp-04.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 NAT's provide similar features of NAPT in the
   single-point and multi-point traversal scenario.

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 http://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 April 24, 2013.

Stewart, et al.          Expires April 24, 2013                 [Page 1]
Internet-Draft              SCTP NAT Support                October 2012

Copyright Notice

   Copyright (c) 2012 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
   (http://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.

Stewart, et al.          Expires April 24, 2013                 [Page 2]
Internet-Draft              SCTP NAT Support                October 2012

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Conventions  . . . . . . . . . . . . . . . . . . . . . . . . .  5
   3.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  5
   4.  Data Formats . . . . . . . . . . . . . . . . . . . . . . . . .  6
     4.1.  Modified Chunks  . . . . . . . . . . . . . . . . . . . . .  6
       4.1.1.  Extended ABORT Chunk . . . . . . . . . . . . . . . . .  6
       4.1.2.  Extended ERROR Chunk . . . . . . . . . . . . . . . . .  7
     4.2.  New Error Causes . . . . . . . . . . . . . . . . . . . . .  7
       4.2.1.  V-Tag and Port Number Collision Error Cause  . . . . .  7
       4.2.2.  Missing State Error Cause  . . . . . . . . . . . . . .  8
       4.2.3.  Port Number Collision Error Cause  . . . . . . . . . .  8
     4.3.  New Parameters . . . . . . . . . . . . . . . . . . . . . .  9
       4.3.1.  Disable Restart Parameter  . . . . . . . . . . . . . .  9
       4.3.2.  V-Tags Parameter . . . . . . . . . . . . . . . . . . .  9
   5.  Problem Space and Procedures . . . . . . . . . . . . . . . . . 11
     5.1.  Problem Space Overview . . . . . . . . . . . . . . . . . . 11
     5.2.  Association Setup Considerations . . . . . . . . . . . . . 11
     5.3.  Handling of Internal Port Number and Verification Tag
           Collisions . . . . . . . . . . . . . . . . . . . . . . . . 11
     5.4.  Handling of Internal Port Number Collisions  . . . . . . . 12
     5.5.  Handling of Missing State  . . . . . . . . . . . . . . . . 13
     5.6.  Multi Point Traversal Considerations . . . . . . . . . . . 15
   6.  Socket API Considerations  . . . . . . . . . . . . . . . . . . 15
Show full document text