%% You should probably cite draft-ietf-tsvwg-natsupp-23 instead of this revision. @techreport{ietf-tsvwg-natsupp-02, number = {draft-ietf-tsvwg-natsupp-02}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-tsvwg-natsupp/02/}, author = {Randall R. Stewart and Michael Tüxen and Irene Ruengeler}, title = {{Stream Control Transmission Protocol (SCTP) Network Address Translation Support}}, pagetotal = 15, year = 2012, month = mar, day = 12, 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.}, }