[133156] in North American Network Operators' Group
Re: Pointer for documentation on actually delivering IPv6
daemon@ATHENA.MIT.EDU (James Hess)
Sun Dec 5 16:32:25 2010
In-Reply-To: <4CFB09C2.5090905@amplex.net>
Date: Sun, 5 Dec 2010 15:32:18 -0600
From: James Hess <mysidia@gmail.com>
To: Mark Radabaugh <mark@amplex.net>
Cc: nanog@merit.edu
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Sat, Dec 4, 2010 at 9:40 PM, Mark Radabaugh <mark@amplex.net> wrote:
> of running RIPng. =A0The thought of letting Belkin routers (if you can ca=
ll
> them that) into the routing table scares me no end.
I think that indeed looks scary. I wouldn't be too concerned about the
Belkin routers.
How many SP routers are really designed to deal with mass numbers of
RIP adjacencies?
RIPng sounds like a plan to deploy 2 or 3 IPv6 end networks, not really b=
etter
than static manual configuration, and with significant disadvantages.
So I would suggest static manual configuration of the port on
routers facing the
CPE, no RIPng. If there are routes to be exchanged with a downstream user=
,
use a proper EGP as one would the IPv4.
Use a CPE of a type that scripts can be written to configure, for
large scale deployments.
If there is an inexpensive CPE with an implementation of DHCPv6 PD
that works without issues,
I would love to hear about who makes it, and what the device is...
> Is this way easier than I think it is? =A0 Did somebody already write the=
book
> that I can't find?
--=20
-JH
