Re: RFC 5006 status

[Brian E Carpenter <brian.e.carpenter@gmail.com>]

Fred,

>> Let me repeat: I'm an operational person, and not a researcher or
>> vendor.  We funny operational people are not searching for the "most
>> religiously perfect" solution for things.  We need something that
>> *works*, and we need it in a timely fashion.
>            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 
> Where is this pressure for this coming from? Are there
> customers waiting frustrated at your doorstep because
> you are not yet able to provide them a service they are
> longing to pay for? (Note: I am a firm believer in the
> need to move to IPv6 and have been pushing for it for
> close to 15 years now. But, I still don't see the
> developing business cases yet.)

If you have a defective egg, you may not get a chicken
at all.

The time pressure is at http://www.potaroo.net/tools/ipv4/,
and the ISPs we've surveyed have given 2011 as the most
common date when they want to offer IPv6 as a standard
service. [Shameless plug for my presentation in v6ops
and iepg.]

Getting back to the purpose of this thread, I've seen enough
responses describing operational value in 5006 to convince me
that we should standardise it for use in simple deployments.
I can't see a downside, quite regardless of who chooses to
deploy DHCPv6; that is a separate question entirely.

    Brian