[167811] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: turning on comcast v6

daemon@ATHENA.MIT.EDU (Justin M. Streiner)
Mon Dec 30 12:39:41 2013

Date: Mon, 30 Dec 2013 09:12:06 -0500 (EST)
From: "Justin M. Streiner" <streiner@cluebyfour.org>
To: North American Network Operators' Group <nanog@nanog.org>
In-Reply-To: <CEDF00D7.3DAAC%Lee@asgard.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

On Tue, 24 Dec 2013, Lee Howard wrote:

>>> I used to run an enterprise network. It was very different from an ISP
>>> network. I didn't say, "You're wrong!" I said, "What's missing?"
>>
>> default route information via DHCPv6.  That's what I'm still waiting for.
>
> Why?
> You say, "The protocol suite doesn't meet my needs; I need default gateway
> in DHCPv6."  So the IETF WG must change for you to deploy IPv6.  Why?

DHCPv6 + RA works for that, but still, that really should have been part 
of the protocol from day one.  I see no good reason for it not to be in 
there.

I suspect that will eventually be fixed, but it will be a long time before 
the majority of DHCPv6 client and server implementations are upgraded to 
support it.

jms


home help back first fref pref prev next nref lref last post