On 04 Mar 2011, at 11:01 , Sander Steffann wrote: > And existing hosts/implementations will ignore the new flag anyway, > so how can an enterprise 'guarantee' that privacy extensions > will not be used?
As with any proposed change/addition to existing IPv6 specs, implementation support appears over time. While any proposed change/addition is not available universally on Day 1, it is also likely that an adopted change/addition will appear in various products over time. > My feeling is that this I-D will only cause confusion > without solving the problem. Noted. Of course, that argument (i.e. not all implementations will support feature X on day 1) equally can be applied to all proposed IPv6 specification additions/changes. So my takeaway from your note (and jhw's note :-) is that you all are among the folks who would like to see IPv6 specs freeze more than they have so far. :-) Cheers, Ran -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
