Document Action: 'IPsec-NAT Compatibility Requirements' to Informational RFC
The IESG <iesg-secretary@ietf.org> Fri, 05 December 2003 16:15 UTC
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11352 for <ietf-announce-web-archive@odin.ietf.org>; Fri, 5 Dec 2003 11:15:24 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14) id 1ASIKb-0000tF-Vc for ietf-announce-list@asgard.ietf.org; Fri, 05 Dec 2003 10:57:25 -0500
Received: from apache by asgard.ietf.org with local (Exim 4.14) id 1ASIJi-0000na-6o; Fri, 05 Dec 2003 10:56:30 -0500
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce:;
Cc: Internet Architecture Board <iab@iab.org>, RFC Editor <rfc-editor@rfc-editor.org>, ipsec@lists.tislabs.com
Subject: Document Action: 'IPsec-NAT Compatibility Requirements' to Informational RFC
Message-Id: <E1ASIJi-0000na-6o@asgard.ietf.org>
Date: Fri, 05 Dec 2003 10:56:30 -0500
Sender: owner-ietf-announce@ietf.org
Precedence: bulk
The IESG has approved following document: - 'IPsec-NAT Compatibility Requirements ' <draft-ietf-ipsec-nat-reqts-06.txt> as an Informational RFC This document is the product of the IP Security Protocol Working Group. The IESG contact persons are Russ Housley and Steve Bellovin. Technical Summary Perhaps the most common use of IPsec is in providing virtual private networking capabilities. One very popular use of 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 to deployment of IPsec in one of its principal uses. This draft describes known incompatibilities between NAT and IPsec, and describes the requirements for addressing them. Working Group Summary The IPsec came to consensus on this document. Protocol Quality This document was reviewed by Russell Housley for the IESG.