RFC 3235: Network Address Translator (NAT)-Friendly Application Design Guidelines
In plain English — editorial summary, not part of the RFC
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 memo provides information for the Internet community.
Document record
- Document ID
- RFC3235
- Published
- January 2002
- Authors
- D. Senie
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- tsv
- Pages
- 13
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3989Middlebox Communications (MIDCOM) Protocol SemanticsObsoleted
February 2005
- RFC 5189Middlebox Communication (MIDCOM) Protocol SemanticsCurrent
March 2008
- RFC 5389Session Traversal Utilities for NAT (STUN)Obsoleted
October 2008
- RFC 6773DCCP-UDP: A Datagram Congestion Control Protocol UDP Encapsulation for NAT TraversalCurrent
November 2012
- RFC 3519Mobile IP Traversal of Network Address Translation (NAT) DevicesCurrent
May 2003
- RFC 3620The TUNNEL ProfileUpdated
October 2003
- RFC 4890Recommendations for Filtering ICMPv6 Messages in FirewallsCurrent
May 2007
- RFC 5575Dissemination of Flow Specification RulesObsoleted
August 2009
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?