Framework for IPv4/IPv6 Translation
draft-baker-behave-v4v6-framework-02
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Fred Baker , Xing Li , Congxiao Bao | ||
| Last updated | 2009-07-06 (Latest revision 2009-02-24) | ||
| Replaced by | draft-ietf-behave-v6v4-framework | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-behave-v6v4-framework | |
| 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 note describes a framework for IPv4/IPv6 translation. This is in the context of replacing NAT-PT, which was deprecated by RFC 4966, and to enable networks to have IPv4 and IPv6 coexist in a somewhat rational manner while transitioning to an IPv6 network.
Authors
Fred Baker
Xing Li
Congxiao Bao
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)