[rfc-dist] BCP 142, RFC 5382 on NAT Behavioral Requirements for TCP

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Thu Oct 16 15:08:17 PDT 2008


A new Request for Comments is now available in online RFC libraries.

        BCP 142        
        RFC 5382

        Title:      NAT Behavioral Requirements for TCP 
        Author:     S. Guha, Ed.,
                    K. Biswas, B. Ford,
                    S. Sivakumar, P. Srisuresh
        Status:     Best Current Practice
        Date:       October 2008
        Mailbox:    saikat at cs.cornell.edu, 
                    kbiswas at cisco.com, 
                    baford at mpi-sws.org,
                    ssenthil at cisco.com, 
                    srisuresh at yahoo.com
        Pages:      31
        Characters: 50306
        See Also:   BCP0142

        I-D Tag:    draft-ietf-behave-tcp-08.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5382.txt

This document defines a set of requirements for NATs that handle TCP
that would allow many applications, such as peer-to-peer applications
and online games to work consistently.  Developing NATs that meet
this set of requirements will greatly increase the likelihood that
these applications will function properly.  This document specifies 
an Internet Best Current Practices for the Internet Community, 
and requests discussion and suggestions for improvements.

This document is a product of the Behavior Engineering for Hindrance Avoidance Working Group of the IETF.


BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for 
improvements. Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute




More information about the rfc-dist mailing list