> > Regarding your #4, I do not believe we are ready to specify > a mandatory > way > > to > > learn a network translator's prefix. And I say that as author of > > draft-wing-behave-learn-prefix (which proposes using DHCPv6 > and DNS) and > my > > awareness of draft-bcx-behave-learn-address (which proposes > using IPv6 > RAs). > > If my memory is correct, using IPv6 RA for prefix64-learning > was initially > proposed in [I-D.wing-behave-learn-prefix]. However, it was > removed from the > -04 version of that draft. > > [I-D.wing-behave-learn-prefix] > Wing, D., Wang, X., and X. Xu, "Learning the IPv6 Prefix > of an IPv6/IPv4 Translator", > draft-wing-behave-learn-prefix-02 (work in progress), > May 2009.
Using Router Advertisements was added in -02 (using text from draft-bcx-behave-learn-address) , and removed in -04. It was removed because feedback I received was that we should build a mechanism to send DHCP messages in Router Advertisements, rather than trying to specify half a dozen documents which effectively duplicate DHCP options in RAs. I thought an editing team was starting to work on such a document (to standardize how to send DHCP in RAs), and pinged two of the authors just yesterday, but I haven't heard back. -d > Xiaohu > > > Furthermore, analysis of a network trace (e.g., using > tcpdump) might be > > performed on a different network anyway, so learning the > prefix of *my* > > network's NAT64 isn't helpful; I need to tell my tool the > prefix of the > NAT64 > > that was being used when the network trace was collected > (example: a > customer > > of Cisco's sends us a network trace, and we need to analyze > it. The tool > > would need to be told the customer's NAT64 prefix (which > could be the WKP > or > > their NSP) not Cisco's NAT64 prefix (which could be the WKP > or our NSP). > > > > Hope that helps. > > -d > > > > -------------------------------------------------------------------- > > IETF IPv6 working group mailing list > > [email protected] > > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 > > -------------------------------------------------------------------- > -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
