Hi Keith,
One comment:
Usage alters to meet the demands of the users. That's nothing new.
| on the contrary, having an enterprise use both SLs and globals creates
| significant new problems of its own, and results in even less
| flexibility than if SLs were used only by isolated networks.
Nothing that IPv4 doesn't have as well (if perhaps less commonly).
there's a reason that most v4 hosts don't have multiple addresses with varying
scopes - it doesn't work well, and it creates problems for apps. putting
sitelocals in v6 is trying to impose those problems on all host.
I'd suggest that there has not been much of demand for this kind of
functionality. Most hosts have had only a single interface, so there is
not a lot of reason to give a single interface multiple addresses.
Already we are seeing laptops with multiple interfaces (Ethernet, WLAN,
Bluetooth, etc.) - I think it is only a matter of time that applications
start to take advantage of this.
One use case for this kind of functionality would be a cell phone that
has some sort of expensive cellular data connnection but also has WLAN /
Bluetooth interfaces. In a WLAN hotspot, data could/should go over that
interface as opposed to the cellular interface. However, the cellular
interface might be used to provide WAN coverage ...
A lot of this is OS / implementation specific stuff, but I don't understand
why this should not be supported in standards.
br,
John