A new Request for Comments is now available in online RFC libraries.
RFC 3235
Title: Network Address Translator (NAT)-Friendly
Application Design Guidelines
Author(s): D. Senie
Status: Informational
Date: January 2002
Mailbox: [EMAIL PROTECTED]
Pages: 13
Characters: 29588
Updates/Obsoletes/SeeAlso: NONE
I-D Tag: draft-ietf-nat-app-guide-07.txt
URL: ftp://ftp.rfc-editor.org/in-notes/rfc3235.txt
This document discusses those things that application designers might
wish to consider when designing new protocols. While many common
Internet applications will operate cleanly in the presence of Network
Address Translators, others suffer from a variety of problems when
crossing these devices. Guidelines are presented herein to help
ensure new protocols and applications will, to the extent possible, be
compatible with NAT (Network Address Translation).
This document is a product of the Network Address Translators Working
Group of the IETF.
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. 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 [EMAIL PROTECTED] Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [EMAIL PROTECTED]
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [EMAIL PROTECTED] with the message body
help: ways_to_get_rfcs. For example:
To: [EMAIL PROTECTED]
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to [EMAIL PROTECTED] Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo
Submissions for Requests for Comments should be sent to
[EMAIL PROTECTED] Please consult RFC 2223, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
...
Below is the data which will enable a MIME compliant Mail Reader
implementation to automatically retrieve the ASCII version
of the RFCs.
rfc3235.txt
Description: message/external-body
