IPsec-Network Address Translation (NAT) Compatibility Requirements

Metadata

Publisher: IETF
Doc Type: Informational
Pages: 18
Abstract: 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.
Publication Date: 2004-03-01
Status Note: Informational
DOI: 10.17487/RFC3715
Link: https://doi.org/10.17487/RFC3715
Author(s): Dr. Bernard D. Aboba
William Dixon
Keyword(s): VPN, Intranet

Latest version of IETF RFC 3715

Document Versions — IETF RFC 3715

▶ IETF RFC 3715 (2004-03-01)

THIS DOC [ACTIVE] [LATEST VERSION]

Normative Reference(s)

IETF RFC 791 [Active*]
IETF RFC 793 [Superseded*]
IETF RFC 2119 [Active*]
IETF RFC 2401 [Superseded*]
IETF RFC 2402 [Superseded*]
IETF RFC 2406 [Superseded*]
IETF RFC 2407 [Superseded*]
IETF RFC 2409 [Superseded*]
IETF RFC 2663 [Active*]
IETF RFC 3022 [Active*]

Bibliographic Reference(s)

Kent, S., "Authenticated Source Addresses", IPsec WG Archive ( ftp://ftp.ans.net/pub/archive/IPsec ), Message- Id: <v02130517ad121773c8ed@[128.89.0.110]>, January 5, 1996. EXTERNAL
Stewart, R., et al., "Stream Control Transmission Protocol (SCTP) Dynamic Address Reconfiguration", Work in Progress. EXTERNAL
IETF RFC 2408 [Superseded*]
IETF RFC 2960 [Superseded*]
IETF RFC 3056 [Active*]
IETF RFC 3102 [Active*]
IETF RFC 3103 [Active*]
IETF RFC 3104 [Active*]
IETF RFC 3193 [Active*]
IETF RFC 3309 [Superseded*]
IETF RFC 3456 [Active*]

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC3715.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree

Reference this Doc

Plain text (ISO 690 compliant)

Preview:

IETF RFC 3715, IPsec-Network Address Translation (NAT) Compatibility Requirements. Available at https://doi.org/10.17487/RFC3715

Snippet:

IETF RFC 3715, IPsec-Network Address Translation (NAT) Compatibility Requirements. Available at https://doi.org/10.17487/RFC3715

HTML (ISO 690 compliant)

Preview:

IETF RFC 3715, IPsec-Network Address Translation (NAT) Compatibility Requirements. Available at https://doi.org/10.17487/RFC3715

Snippet:

<span class="citation"><cite>IETF RFC 3715</cite>, IPsec-Network Address Translation (NAT) Compatibility Requirements. Available at <a href="https://doi.org/10.17487/RFC3715" target="_blank" rel="noopener">https://doi.org/10.17487/RFC3715</a></span>

SMPTE's HTML Pub

Preview:

IETF RFC 3715, IPsec-Network Address Translation (NAT) Compatibility Requirements
doi: 10.17487/RFC3715
url: https://doi.org/10.17487/RFC3715

Snippet:

<li>
<cite id="bib-rfc3715">IETF RFC 3715</cite>, IPsec-Network Address Translation (NAT) Compatibility Requirements
<span class="doi">10.17487/RFC3715</span>
</li>

Referenced By

IETF RFC 3947 [Active*]
IETF RFC 3948 [Active*]
IETF RFC 4306 [Superseded*]
IETF RFC 5406 [Active*]
IETF RFC 5996 [Superseded*]
IETF RFC 6269 [Active*]
IETF RFC 7296 [Active*]