Subject: [BEHAVE] Fwd: I-D Action:draft-korhonen-behave-nat64-learn-analysis-02.txt

From: jouni korhonen <[email-masked]>
Date: Tue, 22 Feb 2011 16:46:03 +0200

Folks,

We have update the draft based on the comments we received. 

* Some more meat added to Issue#4.

* We clarified the Issue#5 regarding multiple NSPs. Learning one NSP is enough for a host to do the synthesis but in order to avoid NAT64 the host should learn all NSPs in the access network.

* We added a paragraph regarding referral objects.

* We added a new section for "Learning the IPv6 Prefix of a Network's NAT64 using Access Technology Specific Methods".

* We lifted up our solution recommendation/proposal so that even lazy readers can spot it out in conclusions ;) Some more tweaking in conclusions like stating that no DNS based solution comes without real standards effort..

- Jouni & Teemu

Begin forwarded message:

> From: [email-masked]
> Date: February 22, 2011 4:00:01 PM GMT+02:00
> To: [email-masked]
> Subject: I-D Action:draft-korhonen-behave-nat64-learn-analysis-02.txt
> Reply-To: [email-masked]
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> 
> 	Title           : Analysis of solution proposals for hosts to learn NAT64 prefix
> 	Author(s)       : J. Korhonen, T. Savolainen
> 	Filename        : draft-korhonen-behave-nat64-learn-analysis-02.txt
> 	Pages           : 26
> 	Date            : 2011-02-22
> 
> 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.