Hi,
> I think we take the opposite view - that we're putting an IPv6 overlay
> on an existing infrastructure and it helps to align the numbering as
> much as possible. (Currently we have about 700 IPv4 routes.)
we overlay - with the relationship as described
> So you have overlapping sets of 3-figure VLAN numbers? You don't carry
> VLANs across domains?
no and no
(even if we did have overlapping, we would have eg
6323 and 8323 - the initial number would show that its a different park)
> Absolutely - KISS, or at least KIASAPBNSTPS.
;-)
> Interesting, not least because the first one tells me there's still (as
> at April '11) no one method of host configuration that works for
> everything, except for SLAAC. At first glance excellent documents,
> though.
correct. and in fact SLAAC still doesnt deliver at this point in time
(you need dual-stack with DHCPv4 to deliver DNS/NTP details) - this should
be fixed in most vendors kit (and client updates) sometime over the ....
next few years I guess....
DHCPv6 is okay - does the job (though most clients dont accept/support the
default router option) but still a lot of clients dont support it.
alan
|