<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-behave-sctpnat" target="https://datatracker.ietf.org/doc/html/draft-ietf-behave-sctpnat-05">
   <front>
      <title>Stream Control Transmission Protocol (SCTP) Network Address Translation</title>
      <author initials="R. R." surname="Stewart" fullname="Randall R. Stewart">
         </author>
      <author initials="M." surname="Tüxen" fullname="Michael Tüxen">
         </author>
      <author initials="I." surname="Ruengeler" fullname="Irene Ruengeler">
         </author>
      <date month="June" day="26" year="2011" />
      <abstract>
	 <t>   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 or 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 an SCTP specific variant of NAT which
   provides similar features of NAPT in the single point and multi-point
   traversal scenario.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-behave-sctpnat-05" />
   
</reference>
