Browse Prior Art Database

UDP Encapsulation of Stream Control Transmission Protocol (SCTP) Packets for End-Host to End-Host Communication (RFC6951)

IP.com Disclosure Number: IPCOM000227942D
Original Publication Date: 2013-May-01
Included in the Prior Art Database: 2013-May-30
Document File: 24 page(s) / 26K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

M. Tuexen: AUTHOR [+2]

Abstract

This document describes a simple method of encapsulating SCTP packets into UDP packets. SCTP, as defined in [RFC4960], runs directly over IPv4 or IPv6. There are two main reasons for encapsulating SCTP packets:

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 10% of the total text.

Internet Engineering Task Force (IETF)                         M. Tuexen Request for Comments: 6951              Muenster Univ. of Appl. Sciences Category: Standards Track                                     R. Stewart ISSN: 2070-1721                                           Adara Networks                                                                 May 2013

 UDP Encapsulation of Stream Control Transmission Protocol (SCTP) Packets                  for End-Host to End-Host Communication

Abstract

   This document describes a simple method of encapsulating Stream    Control Transmission Protocol (SCTP) packets into UDP packets and its    limitations.  This allows the usage of SCTP in networks with legacy    NATs that do not support 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 only describes the functionality    required within an SCTP stack to add on UDP encapsulation, providing    only those mechanisms for two end-hosts to communicate with each    other over UDP ports.  In particular, it does not provide mechanisms    to determine whether UDP encapsulation is being used by the peer, nor    the mechanisms for determining which remote UDP port number can be    used.  These functions are out of scope for this document.

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

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc6951.

Tuexen & Stewart             Standards Track                    [Page 1]
 RFC 6951            UDP Encapsulation of SCTP Packets           May 2013

 Copyright Notice

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