Re: [v6ops] draft-ietf-v6ops-464xlat WGLC

Draft says (almost the same text in two places, here only once):

   The CLAT MAY discover the Pref64::/n of the PLAT via some method such
   as DHCPv6 option, TR-069, DNS APL RR [RFC3123] or
   [I-D.ietf-behave-nat64-discovery-heuristic].

The heuristic is on Standard Track at Behave WG, while RFC3123 is
experimental and for DHCPv6 option afaik there are no proposals on the
table. About TR-069 I have no idea if it touches this topic (reference
missing at least).

Furthermore, the
http://tools.ietf.org/html/draft-ietf-behave-nat64-learn-analysis-03 (RFC
Editor's queue) determined the heuristic as way to go, so should the text
in draft say instead something like this:

--
The CLAT MAY discover the Pref64::/n of the PLAT via
[I-D.ietf-behave-nat64-discovery-heuristic]. In the future some other
mechanisms, such as one using DNS APL RR [RFC3123] or a new DHCPv6 option,
will possibly be defined.
--

If you want for some reason list undefined options (I'd rather drop them
and just say):
--
The CLAT MAY discover the Pref64::/n of the PLAT via
[I-D.ietf-behave-nat64-discovery-heuristic].
--

?

Best regards,

Teemu

2012/8/21 Fred Baker (fred) <fred@cisco.com>

> This is to open a two week Working Group last Call on
>
> http://tools.ietf.org/html/draft-ietf-v6ops-464xlat
>   "464XLAT: Combination of Stateful and Stateless Translation", Masataka
>   Mawatari, Masanobu Kawashima, Cameron Byrne, 19-Aug-12
>
> Please read it now. We are interested in, among other things, technical
> commentary on the draft and the working group's perception on its
> usefulness to its target audience.
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>