RE: Geoff Huston's draft and the intended use of the hinden/templin address space

[Nir Arad]

Michel,   The notion of subnets still exists in any address scoping suggestion. The point you raised below only means that the particular VLAN to which this host belongs, spans one subnet of one scope, and one subnet of the other.   The control device could reside in another VLAN, which only spans one subnet of one of the scopes.   Per my suggestion, "scopes don't communicate" is only refering layer-3 processing of IPv6 packets. Hosts in different scopes can still communicate using IPv4 or other protocols, and there is nothing on IPv6 scoped addresses that me or anyone else can do to stop it.   Regards, -- Nir Arad Marvell Semiconductor Israel http://www.marvell.com/     > Nir Arad wrote: > Excellent scenario, and a simple solution: > The administrator needs to define 2 address scopes. > The control device has an address in scope 1. > The host has addresses in both scopes 1 and 2, as well as a global > unicast address. The DFZ host has an address of scope 2, and a > global unicast address. > All requirements met. Then unless each host has two NICs (which is not acceptable as it doubles the size of the local network) the host interface is in two scopes simultaneously which means the entire VLAN spans two scopes which makes your proposal that scopes don't communicate together void. Michel.