UDP Encapsulation of SCTP Packets for End-Host to End-Host Communication
draft-ietf-tsvwg-sctp-udp-encaps-11

The information below is for an old version of the document
Document Type Active Internet-Draft (tsvwg WG)
Last updated 2013-02-19
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html
Stream WG state WG Document
Consensus Unknown
Document shepherd None
IESG IESG state IESG Evaluation::AD Followup
Telechat date
Needs 4 more YES or NO OBJECTION positions to pass.
Responsible AD Martin Stiemerling
IESG note Gorry Fairhurst (gorry@erg.abdn.ac.uk) is the document shepherd.
Send notices to tsvwg-chairs@tools.ietf.org, draft-ietf-tsvwg-sctp-udp-encaps@tools.ietf.org
Network Working Group                                          M. Tuexen
Internet-Draft                          Muenster Univ. of Appl. Sciences
Intended status: Standards Track                              R. Stewart
Expires: August 23, 2013                                  Adara Networks
                                                       February 19, 2013

UDP Encapsulation of SCTP Packets for End-Host to End-Host Communication
                draft-ietf-tsvwg-sctp-udp-encaps-11.txt

Abstract

   This document describes a simple method of encapsulating SCTP Packets
   into UDP packets and its limitations.  This allows the usage of SCTP
   in networks with legacy NAT not supporting SCTP.  It can also be used
   to implement SCTP on hosts without directly accessing the IP-layer,
   for example implementing it as part of the application without
   requiring special privileges.

   Please note that this document does not provide all techniques
   necessary for building a complete NAT-capable application using SCTP.
   This document focuses on the functionality required within the SCTP
   stack and making this available via an API.  It does not cover
   mechanism to determine whether UDP encapsulation is required to reach
   the peer and, if UDP encapsulation is used, which remote UDP port
   number can be used.

   This document covers only end-hosts and not tunneling (egress or
   ingress) end-points.

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 August 23, 2013.

Copyright Notice

Tuexen & Stewart         Expires August 23, 2013                [Page 1]
Internet-Draft      UDP Encapsulation of SCTP Packets      February 2013

   Copyright (c) 2013 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.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Conventions  . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  Use Cases  . . . . . . . . . . . . . . . . . . . . . . . . . .  3
     3.1.  Portable SCTP Implementations  . . . . . . . . . . . . . .  3
     3.2.  Legacy NAT Traversal . . . . . . . . . . . . . . . . . . .  4
   4.  Unilateral Self-Address Fixing (UNSAF) Considerations  . . . .  4
   5.  SCTP over UDP  . . . . . . . . . . . . . . . . . . . . . . . .  4
     5.1.  Architectural Considerations . . . . . . . . . . . . . . .  4
     5.2.  Packet Format  . . . . . . . . . . . . . . . . . . . . . .  5
     5.3.  Encapsulation Procedure  . . . . . . . . . . . . . . . . .  6
     5.4.  Decapsulation Procedure  . . . . . . . . . . . . . . . . .  6
     5.5.  ICMP Considerations  . . . . . . . . . . . . . . . . . . .  7
     5.6.  Path MTU Considerations  . . . . . . . . . . . . . . . . .  7
     5.7.  Handling of Embedded IP-addresses  . . . . . . . . . . . .  8
     5.8.  ECN Considerations . . . . . . . . . . . . . . . . . . . .  8
   6.  Socket API Considerations  . . . . . . . . . . . . . . . . . .  8
     6.1.  Get or Set the Remote UDP Encapsulation Port Number
           (SCTP_REMOTE_UDP_ENCAPS_PORT)  . . . . . . . . . . . . . .  8
   7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  9
   8.  Security Considerations  . . . . . . . . . . . . . . . . . . .  9
   9.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . .  9
   10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10
     10.1. Normative References . . . . . . . . . . . . . . . . . . . 10
     10.2. Informative References . . . . . . . . . . . . . . . . . . 11
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11
Show full document text