To keep them, we need to document and resolve the issues that they cause, update all of the IPv6 routing protocols to document how site-boundaries are maintained, and document how address selection will be performed in several upper layer protocols (at least SCTP, SIP and FTP). We might also need to provide guidance to non-IETF applications protocol developers and/or application developers for how to handle site-local addresses in non-IETF applications. And, we'd need to specify split DNS.
This is assuming that it is possible to "live with" site-locals. We may wind up writing lots of documents that essentially say "lots of apps will break; tough luck!".
I propose that site-locals change so many fundamental assumptions that applications make that the IAB need to study the issue and make a recommendation -- i.e I don't think that the inclusion of site-locals in the core architecture of the Internet should be at the sole discression of the ipv6 or any other wg.
Leif
-------------------------------------------------------------------- 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] --------------------------------------------------------------------
