IPSEC-NAT Compatibility Requirements
draft-aboba-nat-ipsec-04
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Dr. Bernard D. Aboba | ||
| Last updated | 2001-05-30 (Latest revision 2000-11-27) | ||
| Stream | (None) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
https://www.ietf.org/archive/id/draft-aboba-nat-ipsec-04.txt
Abstract
Perhaps the most common use of IPsec is in providing virtual private networking capabilities. One very popular use of VPNs is to provide tele-commuter access to the corporate Intranet. Today NATs are widely deployed in home gateways, as well as in other locations likely to be used by tele-commuters, 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.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)