[167822] in North American Network Operators' Group
Re: turning on comcast v6
daemon@ATHENA.MIT.EDU (Blake Dunlap)
Mon Dec 30 15:20:14 2013
In-Reply-To: <6E9E84B3-0354-4E58-A5A0-3C28B3BAF61A@uchicago.edu>
From: Blake Dunlap <ikiris@gmail.com>
Date: Mon, 30 Dec 2013 14:19:27 -0600
To: Ryan Harden <hardenrm@uchicago.edu>
Cc: Jamie Bowden <jamie@photon.com>,
North American Network Operators' Group <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
The better question is are you using RIP or ICMP to set gateways in your
network now?
If you don't use those now, why is RA a better solution in ipv6?
-Blake
On Mon, Dec 30, 2013 at 1:20 PM, Ryan Harden <hardenrm@uchicago.edu> wrote:
> On Dec 30, 2013, at 12:58 PM, Lee Howard <Lee@asgard.org> wrote:
>
> >>
> >>
> >> 'Rewrite all of your tools and change your long standing business
> >> practices=B9 is a very large barrier to entry to IPv6. If adding gatew=
ay
> as
> >> an optional field will help people get over that barrier, why not add
> it?
> >> Sure it doesn=B9t fit into the =B3IPv6 way,=B2 but bean counters don=
=B9t care
> >> much for that when you have to ask for developer time to rewrite
> >> everything.
> >
> >
> > Well, the tools have to be rewritten to support IPv6 fields, sockets, a=
nd
> > structures anyway. However, there's a difference between, "Make sure y=
ou
> > call IP family agnostic libraries and increase field sizes, then let it
> > run" and "Rebuild your network security." DHCP+RA just works in most
> > networks; this is a use case where it could be made to work, but only b=
y
> > changing the network.
>
> Updating tools to add a box for IPv6 fields and tweaking the backend to
> generate a config file for DHCPv6 which is very similar to DHCP(for v4) i=
s
> a lot different/easier than having to rewrite and/or split your backend t=
o
> generate output in a completely different format. However, I'm not as
> familiar with RADVD as I am with isc-dhcpd so that might be a bad argumen=
t.
>
> And you don't have to support IPv6 from top to bottom to roll out IPv6 to
> users. So rewriting for socket support isn't necessary day one. You can
> route IPv6 for users so they can reach the IPv6 world quickly, then add
> local services as time/money allows. The biggest driver for IPv6 will be
> external resources available only via IPv6, not local. (Of course this is
> from the point of view where your business' primary service isn't outward
> facing resources.)
>
> I'm sure DHCP+RA works for most, but there are IPv4 shops who swear by
> fully dynamic DHCP, some who do DHCP-Reservations, and some who go static
> only. Just like some shops are EIGRP, some OSPF, and some ISIS. IMO IPv6
> needs to be flexible enough to handle the fact that not everyone builds
> identical architectures nor do they have the exact same needs. Being able
> to use DHCPv6+RA, RA only, or DHCPv6 only should all be viable options.
> Forcing everyone down the same path will just lead to stupid proprietary
> solutions to a problem that shouldn't exist in the first place.
>
> /Ryan
>
