RFC 3715: IPsec-Network Address Translation (NAT) Compatibility Requirements
In plain English — editorial summary, not part of the RFC
This document describes known incompatibilities between Network Address Translation (NAT) and IPsec, and describes the requirements for addressing them. Perhaps the most common use of IPsec is in providing virtual private networking capabilities. One very popular use of Virtual Private Networks (VPNs) is to provide telecommuter access to the corporate Intranet. Today, NATs are widely deployed in home gateways, as well as in other locations likely to be used by telecommuters, such as hotels. The result is that IPsec-NAT incompatibilities have become a major barrier in the deployment of IPsec in one of its principal uses. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3715
- Published
- March 2004
- Authors
- B. Aboba; W. Dixon
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- sec
- Pages
- 18
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4555IKEv2 Mobility and Multihoming Protocol (MOBIKE)Current
June 2006
- RFC 4834Requirements for Multicast in Layer 3 Provider-Provisioned Virtual Private Networks (PPVPNs)Current
April 2007
- RFC 3709Internet X.509 Public Key Infrastructure: Logotypes in X.509 CertificatesObsoleted
February 2004
- RFC 3706A Traffic-Based Method of Detecting Dead Internet Key Exchange (IKE) PeersCurrent
February 2004
- RFC 3739Internet X.509 Public Key Infrastructure: Qualified Certificates ProfileCurrent
March 2004
- RFC 3740The Multicast Group Security ArchitectureCurrent
March 2004
- RFC 3741Exclusive XML Canonicalization, Version 1.0Current
March 2004
- RFC 3686Using Advanced Encryption Standard (AES) Counter Mode With IPsec Encapsulating Security Payload (ESP)Current
January 2004
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?