[Docs] [txt|pdf] [Tracker] [Email] [Diff1] [Diff2] [Nits]

Versions: 00 01 02 03 04 05 06 07

Network Working Group                                          M. Tuexen
Internet-Draft                        Muenster Univ. of Applied Sciences
Intended status: Standards Track                              R. Stewart
Expires: May 20, 2008                                Cisco Systems, Inc.
                                                       November 17, 2007


                   UDP Encapsulation of SCTP Packets
                  draft-tuexen-sctp-udp-encaps-02.txt

Status of this Memo

   By submitting this Internet-Draft, each author represents that any
   applicable patent or other IPR claims of which he or she is aware
   have been or will be disclosed, and any of which he or she becomes
   aware will be disclosed, in accordance with Section 6 of BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

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

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on May 20, 2008.

Copyright Notice

   Copyright (C) The IETF Trust (2007).

Abstract

   This document describes a simple method of encapsulating SCTP
   Packets.  This makes it possible to use SCTP in networks with legacy
   NAT not supporting SCTP.







Tuexen & Stewart          Expires May 20, 2008                  [Page 1]


Internet-Draft      UDP Encapsulation of SCTP Packets      November 2007


Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . 3
   3.  Architecture  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   4.  Port Number Table . . . . . . . . . . . . . . . . . . . . . . . 3
   5.  Encapsulating procedures  . . . . . . . . . . . . . . . . . . . 4
   6.  Decapsulating procedures  . . . . . . . . . . . . . . . . . . . 4
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
   8.  Security Considerations . . . . . . . . . . . . . . . . . . . . 5
   9.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 5
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . . . 5
     10.1.  Normative References . . . . . . . . . . . . . . . . . . . 5
     10.2.  Informative References . . . . . . . . . . . . . . . . . . 5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 5
   Intellectual Property and Copyright Statements  . . . . . . . . . . 7



































Tuexen & Stewart          Expires May 20, 2008                  [Page 2]


Internet-Draft      UDP Encapsulation of SCTP Packets      November 2007


1.  Introduction

   This document describes a simple method of encapsulating SCTP
   Packets.  This makes it possible to use SCTP in networks with legacy
   NAT not supporting SCTP.  This described method interworks without
   any problems with the NAT mechanism described in
   [I-D.stewart-behave-sctpnat].  For general NAT considerations
   regarding SCTP see [I-D.xie-behave-sctp-nat-cons].


2.  Conventions

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].


3.  Architecture

   The basic architecture is shown in the following figure.

                  +----------------+   +----------------+
                  | Encapsulating/ |   | Encapsulating/ |
                +-| Decapsulating  |---| Decapsulating  |-+
                | |     Point      |   |     Point      | |
   +----------+ | +----------------+   +----------------+ | +----------+
   |          |-+                                         +-|          |
   |   SCTP   |                                             |   SCTP   |
   | Endpoint |                                             | Endpoint |
   |          |-+                                         +-|          |
   +----------+ | +----------------+   +----------------+ | +----------+
                | | Encapsulating/ |   | Encapsulating/ | |
                +-| Decapsulating  |---| Decapsulating  |-+
                  |     Point      |   |     Point      |
                  +----------------+   +----------------+

   On each path there is a pair of encapsulating/decapsulating points
   (EDPs).  When the left SCTP endpoint sends an SCTP packet to the
   right SCTP endpoint, the first EDP on the path encapsulates the SCTP
   packet and the second EDP decapsulates it.  Between the EDP a UDP
   packet is sent which can be processed by legacy NATs.  The EDPs on
   different paths do not need to be synchronized.


4.  Port Number Table

   Every EDP maintains an encapsulating table (ET) where each row
   consists of the following entries:



Tuexen & Stewart          Expires May 20, 2008                  [Page 3]


Internet-Draft      UDP Encapsulation of SCTP Packets      November 2007


   1.  Source Address

   2.  Source Port

   3.  Destination Address

   4.  Destination Port

   5.  Time Stamp

   Please note that the port numbers in the ET are used to build the UDP
   header while encapsulating.  A row SHOULD be deleted when the time
   stamp is older than T1 seconds.  The default value for T1 is 300
   seconds.


5.  Encapsulating procedures

   When an EDP has to encapsulate an SCTP packet it looks up the source
   and destination port number in the row with matching source and
   destination addresses of the ET.  If no matching row is found, the
   IANA registered value 9899 is used for the source and destination
   port as the result of the lookup procedure.  If a matching row was
   found, the time stamp of that row is set to the current time.

   The EDP inserts then an UDP header between the IP and SCTP header of
   the SCTP packet using the source port and the destination port from
   the above lookup procedure.  Furthermore the length and the checksum
   field of the UDP header have to be set accordingly.  Finally the IP
   header is updated to indicate that it now encapsulates an UDP packet.


6.  Decapsulating procedures

   When an EDT has to decapsulate an SCTP packet, it removes the UDP
   header from the packet.  The IP header is updated to indicate that it
   now encapsulates an SCTP packet.  If the source and destination port
   numbers are not both equal to 9899, the EDP performs a lookup in the
   ET to find a row with the source address of the packet being the
   destination address in the row and the destination address of the
   packet being the source address in the row.  If such a row is found,
   the port numbers are updated.  If no row is found, a new one is
   created using the addresses and the port numbers from the packet by
   exchanging the source and destination information.  In both cases the
   time stamp of the row is set to the current time.






Tuexen & Stewart          Expires May 20, 2008                  [Page 4]


Internet-Draft      UDP Encapsulation of SCTP Packets      November 2007


7.  IANA Considerations

   This document does not require any actions from IANA.


8.  Security Considerations

   This section is not complete yet.


9.  Acknowledgments

   The authors wish to thank Irene Ruengeler for her invaluable
   comments.


10.  References

10.1.  Normative References

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.

   [RFC4960]  Stewart, R., "Stream Control Transmission Protocol",
              RFC 4960, September 2007.

10.2.  Informative References

   [I-D.xie-behave-sctp-nat-cons]
              Xie, Q., "SCTP NAT Traversal Considerations",
              draft-xie-behave-sctp-nat-cons-02 (work in progress),
              November 2006.

   [I-D.stewart-behave-sctpnat]
              Stewart, R. and M. Tuexen, "Stream Control Transmission
              Protocol (SCTP) Network Address Translation",
              draft-stewart-behave-sctpnat-02 (work in progress),
              May 2006.













Tuexen & Stewart          Expires May 20, 2008                  [Page 5]


Internet-Draft      UDP Encapsulation of SCTP Packets      November 2007


Authors' Addresses

   Michael Tuexen
   Muenster Univ. of Applied Sciences
   Stegerwaldstr. 39
   48565 Steinfurt
   Germany

   Email: tuexen@fh-muenster.de


   Randall R. Stewart
   Cisco Systems, Inc.
   4875 Forest Drive
   Suite 200
   Columbia, SC  29206
   USA

   Email: rrs@cisco.com
































Tuexen & Stewart          Expires May 20, 2008                  [Page 6]


Internet-Draft      UDP Encapsulation of SCTP Packets      November 2007


Full Copyright Statement

   Copyright (C) The IETF Trust (2007).

   This document is subject to the rights, licenses and restrictions
   contained in BCP 78, and except as set forth therein, the authors
   retain all their rights.

   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
   THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
   OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
   THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.


Intellectual Property

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; nor does it represent that it has
   made any independent effort to identify any such rights.  Information
   on the procedures with respect to rights in RFC documents can be
   found in BCP 78 and BCP 79.

   Copies of IPR disclosures made to the IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use of
   such proprietary rights by implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   http://www.ietf.org/ipr.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at
   ietf-ipr@ietf.org.


Acknowledgment

   Funding for the RFC Editor function is provided by the IETF
   Administrative Support Activity (IASA).





Tuexen & Stewart          Expires May 20, 2008                  [Page 7]


Html markup produced by rfcmarkup 1.129c, available from https://tools.ietf.org/tools/rfcmarkup/