> I am _not_ operating under the assumption that all > globally-unique addresses will appear in global routing > tables. If I want to have a private network, I should be > able to get a globally unique (routable, but _not_ > necessarily globally routed) address, and _not_ have my ISP > advertise that prefix into the global routing tables. If my > ISP's policy (or some higher-level policy) requires that I > get a second /48 in order to have address space that isn't > advertised, I could just get a second /48...
So we have a site with a globally-routable /48 prefix. Are you saying that instead of using site-local addresses in addition to its global addresses, the site could use a second /48 global prefix that is not globally routable and is filtered at the site boundary? This would be silly. It would be just like site-locals except with a non-standard prefix. It would work worse than site-locals because Default Address Selection wouldn't work properly and because of Keith's issue of distributed apps that do referrals - those apps wouldn't be able to distinguish the two kinds of addresses to do the right thing. Rich -------------------------------------------------------------------- IETF IPng Working Group Mailing List IPng Home Page: http://playground.sun.com/ipng FTP archive: ftp://playground.sun.com/pub/ipng Direct all administrative requests to [EMAIL PROTECTED] --------------------------------------------------------------------
