> From: "Templin, Fred L" <[EMAIL PROTECTED]> > > I am talking about a "laptop" that connects an arbitrarily- > complex internal network of virtual hosts and routers, and > an arbitrarily-complex set of external devices attached on, > e.g., Ethernet, Bluetooth, etc. ...
so, there's a routing protocol here? > So, it can't just be link-local-for-all, because then there > is no opportunity for off-link communications when in fact > the laptop may connect many links. if the laptop is going to connect to many links, then it will get an address assigned for each of those links, by DHCP or stateless autoconf or even manual config. giving the laptop its own UA will only make sense if there's a routing protocol by which that UA-block is advertised into the networks the laptop connects with. so can you explain the routing? > Also, if my laptop ever > needs to connect up with other sites (be it planned or ad-hoc; > via phisical links or virtual) it will need to have something > like ULA-C to avoid collisions. And, I don't want to have to > inject a globally-routable prefix into the DFZ for it. forget the DFZ for a minute. you will have to inject your UA into the network(s) you attach to. how's that going to work? (and what's the horizon of that injection?) -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
