> From: Tim Chown <[EMAIL PROTECTED]> > I think a site getting global connectivity would find it hard to migrate > instantly from site-locals to globals. The suggestion to prefer globals > over site locals in the default address selection spec, along with Brian's > suggested text a couple of mails back, seems good.
Why should it be a problem? - existing connections can continue to use the site locals, presense of global connectivity should not touch them in any way. - as far as I know, source address selection prefers site local if destination is site local, and global if destination is global. So, if your application gets site local address from your "two-faced DNS", it works; if your application gets global address due to current global connectivity, global address is used as a source too. - when global connection goes down, all applications using the global addresses will fail, but those using site locals continue to work. - it seems that it would be advantageous for nodes within the site to use sitelocals whenever possible, especially if your global connection is via flaky connection. -------------------------------------------------------------------- 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] --------------------------------------------------------------------
