[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
IPv6 Confusion
- Subject: IPv6 Confusion
- From: jbates at brightok.net (Jack Bates)
- Date: Wed, 18 Feb 2009 13:53:41 -0600
- In-reply-to: <[email protected]>
- References: <6CDE22DE80A63A4DACF4FE2C916519A53F022F784D@BLV11EXVS01.corp.dm.local> <[email protected]> <6CDE22DE80A63A4DACF4FE2C916519A53F022F788E@BLV11EXVS01.corp.dm.local> <050701c99135$df0f0ed0$9d2d2c70$@net> <[email protected]> <056801c9914d$7c2a0e10$747e2a30$@net> <[email protected]> <[email protected]>
Kevin Loch wrote:
> Just how DO we get the message to the IETF that we need all the tools we
> have in v4 (DHCP, VRRP, etc) to work with RA turned off?
You don't, because there isn't really a technical reason for turning off
RA. RA is used as a starting point. It can push you to DHCPv6 or any
number of other options (such as SLAAC). The same argument goes for
multicast versus broadcast. The idea is to add an extra level that
allows for better manipulation and versatility.
Of course, better support and vendor implementation of all the different
options would be nice.
Most networks have broadcast controls that are mostly vendor specific
hacks. Now they'll have multicast controls, which is good to have anyways.
If you want to get into something irksome, please point out that looking
at a much of link local addresses/interfaces for next hopes in IGP's is
rather annoying. Only reason to even have global routed IP's on the
router is for traceroutes, but you can't just "look up route, ping next
hop IP from remote location to verify next hop was reachable".
-Jack