Analysis of solution proposals for hosts to learn NAT64 prefix
draft-korhonen-behave-nat64-learn-analysis-02
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Jouni Korhonen , Teemu Savolainen | ||
| Last updated | 2011-05-27 (Latest revision 2011-02-22) | ||
| Replaced by | draft-ietf-behave-nat64-learn-analysis | ||
| 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-nat64-learn-analysis | |
| 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
Hosts and applications may benefit from the knowledge if an IPv6 address is synthesized, which would mean a NAT64 is used to reach the IPv4 network or Internet. This document analyses a number of proposed solutions for communicating whether the synthesis is taking place, used address format, and the IPv6 prefix used by the NAT64 and DNS64. This enables both NAT64 avoidance and intentional utilization by allowing local IPv6 address synthesis.
Authors
Jouni Korhonen
Teemu Savolainen
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)