[rfc-dist] RFC 3715 on IPsec-Network Address Translation (NAT) Compatibility Requirements
rfc-editor@rfc-editor.org (rfc-editor@rfc-editor.org) Fri, 12 March 2004 23:32 UTC
From: rfc-editor@rfc-editor.org
Date: Fri, 12 Mar 2004 15:32:00 -0800
Subject: [rfc-dist] RFC 3715 on IPsec-Network Address Translation (NAT) Compatibility Requirements
Message-ID: <200403122332.i2CNW1k11490@gamma.isi.edu>
--NextPart A new Request for Comments is now available in online RFC libraries. RFC 3715 Title: IPsec-Network Address Translation (NAT) Compatibility Requirements Author(s): B. Aboba, W. Dixon Status: Informational Date: March 2004 Mailbox: bernarda@microsoft.com, ietf-wd@v6security.com Pages: 18 Characters: 43476 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ipsec-nat-reqts-06.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3715.txt 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 document is a product of the IP Security Protocol 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 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 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. 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. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <040312153037.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3715 --OtherAccess Content-Type: Message/External-body; name="rfc3715.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <040312153037.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart--
- [rfc-dist] RFC 3715 on IPsec-Network Address Tran… rfc-editor@rfc-editor.org