Having the routers cache id-to-loc mappings is one thing; having them perform id-to-loc mappings is something else entirely. Yes, the hosts will still generate such requests, but those requests don't have to traverse the entire network if the local router knows what to do with them.
You're making a host of assumptions here. One of them is that even though the info is requested per-host, it exists as per-site. This doesn't follow: it could very well be that each host has its own mapping, mostly independent from that of other hosts in the same site. This would probably be necessary in a mobility setup.
But a lot is being assumed by the above statement.
Ah. :-)
I am fairly convinced that id-to-loc mapping needs to be more like mobile-ip where you send a packet to the id and get a redirect to the loc if the network can't route to the id,
But what if the network silently (or seemingly silently, re ICMP filtering) drops your packet?
-------------------------------------------------------------------- IETF IPv6 working group mailing list [EMAIL PROTECTED] Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
