Achieving Addressing Functions in IPv6 without using NAT
draft-daley-ipv6-nonat6-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Greg Daley | ||
| Last updated | 2009-07-13 | ||
| 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
Proposals have been made to include Network Address Translation (NAT) in IPv6. Network Address Translation substitutes a source address in the outbound Packet headers at the Internet Egress point for one present at the network edge. It then matches the responding packets by destination address, and restores the original headers. NAT itself is not a feature. It is a mechanism which provides features at an application cost. This document identifies features which are supplied by NAT in IPv4 and how these features may be provisioned in IPv6. Both NAT and application-friendly alternatives are presented.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)