[rfc-dist] BCP 127 RFC 4787 on Network Address Translation (NAT) Behavioral Requirements for Unicast UDP
rfc-editor at rfc-editor.org
Wed Jan 31 18:17:44 PST 2007
A new Request for Comments is now available in online RFC libraries.
Title: Network Address Translation (NAT) Behavioral
Requirements for Unicast UDP
Author: F. Audet, Ed.,
Status: Best Current Practice
Date: January 2007
Mailbox: audet at nortel.com,
fluffy at cisco.com
I-D Tag: draft-ietf-behave-nat-udp-08.txt
This document defines basic terminology for describing different
types of Network Address Translation (NAT) behavior when handling
Unicast UDP and also defines a set of requirements that would allow
many applications, such as multimedia communications or online
gaming, 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.
BEST CURRENT PRACTICE:
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 list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info at RFC-EDITOR.ORG
Subject: getting rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
The RFC Editor Team
USC/Information Sciences Institute
More information about the rfc-dist