Pierre Pfister <[email protected]> wrote: >> To quote from the charter: >> >> Prefix configuration, routing, and security related work shall not >> cause any changes that are not backwards compatible to existing IPv6 >> hosts. There may be host visible changes in the work on naming and >> discovery protocols, however. >> >> "backwards compatible" doesn't mean that we can't write down things >> where a smarter newer host can get better service. It means that >> existing hosts must get some kind of service, regardless.
> In a multi-homing case, multiple ISP would provide multiple
> prefixes. It is expected that, with colored prefixes, each prefixes
> will be attached dedicated services. When there is a single ISP,
> DHCP-PD can serve the prefixes correctly to the host. But in a
There are a number of possibilities where "backwards compatible" might mean
different things. Let's take your voice application example:
> For instance, if a prefix is for general purpose, and another is for voice
> applications, then hosts may only get addresses for voice application, and
> would therefore not being able to access the internet.
So, prior to homenet, what happens? (If the answer is no v6, then stop.)
If it that the phones get plugged into the voip router, and the computers
get plugged into the internet router, and the two are not connected, then
that is in fact still an option.
If the routers are upgraded with homenet, and now interconnected then to
remain backwards compatible I would expect:
1) the phones without required upgrades to remain plugged into the voice
router.
2) hosts that can accept two prefixes and pick the right prefix can
run the soft voice application.
3) hosts that can not accept two prefixes (really? that's in the spec
for a long time), would have a problem. They weren't to spec.
4) hosts that can accept two prefixes would attempt to use the voice
prefix for internet access, get a no-route-to-host, and happy
eyeballs would do the right thing.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | network architect [
] [email protected] http://www.sandelman.ca/ | ruby on rails [
pgpVDMxkaQKln.pgp
Description: PGP signature
_______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
