Mysterious missing DHCPv6 feature, was Re: How does one obtain an IPv6 DNS server when VPNing to an ASA?

Mark Smith nanog at 85d5b20a518b8f6864949bd940457dc124746ddc.nosense.org
Tue May 18 14:17:55 CEST 2010


On Mon, 17 May 2010 15:49:31 -0700 (PDT)
David Barak <thegameiam at yahoo.com> wrote:

> 
> --- On Mon, 5/17/10, Mark Smith 
> > What I think is hampering deployment is people constantly
> > discussing
> > and debating design decisions that they don't agree with,
> > 10 to 15
> > years after they were made, rather than accepting them, and
> > getting on
> > with deploying it. It may not be perfect in their opinion
> > (and it
> > isn't in mine), but then usually nothing ever is - it's all
> > about trade
> > offs. The pressing problem is deployment.
> > 
> 
> toMAYto toMAHto.
> 
> One of the things about IPv4+DHCP which helped it really take off is the ability of providers + enterprises to regulate and monetize their interactions with their downstreams.  The IPv6 designers, in their infinite wisdom, chose to {ignore |disregard} the desires of organizations which have made significant infrastructure investments in this.  In that vein, they chose to make centralized decisions necessarily decentralized.  This is viewed as an improvement by some, but certainly not by all.
> 

So where are your posts to the IETF IPv6 mailing lists, stating these
desires?

> Are you honestly suggesting that this should be swallowed without comment?  What if the design decisions are in fact bad?  Why not try to fix the brokenness?
> 

How do you know existing methods are broken? Have you deployed them? 


> David Barak
> Need Geek Rock?  Try The Franchise: 
> http://www.listentothefranchise.com
> 
> 
> 
>       


More information about the ipv6-ops mailing list