Network Address Translation issues with IPsec
draft-moskowitz-net66-vpn-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Robert Moskowitz | ||
| Last updated | 1998-02-12 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| 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) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document looks at a number of issues surrounding the need for network address translation (NAT) when IPsec is used to create virtual private networks (VPN). This document only looks at simple VPNs. That is VPNs consisting of a single IPsec tunnel as compared to VPNs consisting of \021chained\022 and/or \021nested\022 IPsec tunnels and/or transports. It proposes a method to vastly reduce the extent that NAT is needed in a VPN.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)