[136372] in North American Network Operators' Group
Re: quietly....
daemon@ATHENA.MIT.EDU (George Herbert)
Wed Feb 2 15:16:53 2011
In-Reply-To: <01B5A647-AB05-4435-88FE-2F7535A644B2@muada.com>
Date: Wed, 2 Feb 2011 12:15:01 -0800
From: George Herbert <george.herbert@gmail.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Wed, Feb 2, 2011 at 8:55 AM, Iljitsch van Beijnum <iljitsch@muada.com> w=
rote:
> On 2 feb 2011, at 17:14, Dave Israel wrote:
>
>>> I understand people use DHCP for lots of stuff today. But that's mainly=
because DHCP is there, not because it's the best possible way to get that =
particular job done.
>
>> So what if I want to assign different people to different resolvers by p=
olicy?
>
> For the record: I'm not saying that DHCPv6 is never useful. DHCPv6 is int=
ended as a stateful configuration provisioning tool, i.e., to give differen=
t hosts different configurations. If that's what you need then DHCP fits th=
e bill. However, in most small scale environments this is not what's needed=
so DHCP doesn't fit the bill.
There are all sized enivronments. Political battles having partly
crippled DHCPv6 in ways that end up significantly limiting IPv6 uptake
into large enterprise organizations ... it's hard to describe how
frustrating this is without resorting to thrown fragile objects
against hard walls. As an active consultant to medium and large
enterprises, this is driving me nuts.
This single item is in my estimation contributing at least 6, perhaps
12 months to the worldwide average delay in IPv6 uptake. I know
several organizations that would have been there six months ago had
DHCPv6 not had this flaw. They're currently 6-12 months from getting
there.
This was predicted. That the right people didn't believe it suggests
that perhaps the right people are the wrong people.
> Also, the examples mentioned are about enterprise networks with stable sy=
stems. Here, DHCP works well. However, with systems that connect to differe=
nt networks, things don't always work so well. I may want to use the DHCP-p=
rovided NTP servers at work, but syncing with a random NTP server when I co=
nnect to a wifi hotspot is not such a great idea.
That's a problem with insufficiently configurable network location
profiles on your OS (not having a "listen to DHCP NTP here, but not
elsewhere" button).
--=20
-george william herbert
george.herbert@gmail.com
