Skip to main content

Network Address Translator (NAT)-Friendly Application Design Guidelines

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3235.
Author Daniel Senie
Last updated 2013-03-02 (Latest revision 2001-11-30)
RFC stream Internet Engineering Task Force (IETF)
Additional resources Mailing list discussion
Stream WG state WG Document
Document shepherd (None)
IESG IESG state RFC 3235 (Informational)
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to (None)
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
        Pages:      13
        Characters: 29588
        Updates/Obsoletes/SeeAlso:  NONE

        I-D Tag:    draft-ietf-nat-app-guide-07.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 IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        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 RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.