Modified Network Address Translation - Protocol Translation
draft-van-beijnum-modified-nat-pt-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Iljitsch van Beijnum | ||
| Last updated | 2007-11-19 | ||
| 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
A smooth transition from IPv4 to IPv6 requires that either all hosts are upgraded to dual stack before the first hosts can become IPv6- only, or that there be some mechanism for IPv6-only hosts to talk to IPv4-only hosts. Expecting the former within a reasonable timeframe isn't realistic, based on current adoption of dual stack combined with the latest projections for the IPv4 depletion that point to a date early in the next decade. And the IETF has recently deprecated the main mechanism that allows the latter: NAT-PT. This document proposes modifications to NAT-PT that address the reasons why the mechanism was deprecated. This should allow future deployment of the modified NAT-PT as an IPv4-to-IPv6 transition mechanism, giving operators the option of running their networks largely IPv6-only.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)