Re: Deprecating IPv6 (Re: draft-bourbaki-6man-classless-ipv6-00)

On Wed, Jun 7, 2017 at 1:43 PM james woodyatt <jhw@google.com> wrote:

> On Jun 7, 2017, at 13:21, james woodyatt <jhw@google.com> wrote:
>
>
> I see no dogs wagging. From my perspective, I see a wagging tail on a dog
> that doesn’t even know it has one.
>
>
> Furthermore, I should clarify that I’m taking no position whatsoever
> against what I view to be an effort to update IPv6 Address Assignment to
> End Sites [RFC 6177] to drop the following reaffirmation on page 3:
>
>       A key principle for address management is that end sites always be
>       able to obtain a reasonable amount of address space for their
>       actual and planned usage, and over time ranges specified in years
>       rather than just months.  In practice, that means at least one
>       /64, and in most cases significantly more.  One particular
>       situation that must be avoided is having an end site feel
>       compelled to use IPv6-to-IPv6 Network Address Translation or other
>       burdensome address conservation techniques because it could not
>       get sufficient address space.
>
>
> I no longer feel this must be avoided. It’s too late to stop that from
> happening. It now seems perfectly acceptable that end sites should feel
> compelling to use IPv6-to-IPv6 Network Address Translation or other
> burdensome address conservation techniques because it cannot get sufficient
> address space.
>

I am unfamiliar with thread () in the real world and don't yet feel
compelled to believe a widely deployed ietf standards track specifications
should bend due some niche design choices that may or may not achieve a
significant deployment.

Thread () makes design choices and they deal with them.  Same for ietf.

I believe i am agreeing with Fred

>
> --james woodyatt <jhw@google.com>
>
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>