Posting only as an interested individual: It definitely seems like this discussion is degenerating, but I think we have made some useful progress in understanding what the key issues are in this debate:
- What are the security impacts, if any, of site local addresses. - How important are site-local addresses as a tool to allow site administrators to have address independence from their ISPs, and are there other ways to get this benefit? - What level of impact, if any, will the widespread use of site-local addresses have on: - Applications (current and future) - Transport Protocols - Security Protocols - Network Management Protocols - Should site-local addresses be placed in the DNS, and if so, how? - What level of complexity do site-local addresses add to router/routing protocol implementations? - Is there a good way to limit the use of site-local addresses (to non-globally attached networks, special uses, etc.) that will maximize the benefits and minimize the problems? Did I miss any of the big issues? Unfortunately, we haven't made much progress in resolving any of these issues, and it doesn't look like we will resolve them by continuing to send each other the same points in e-mail over and over again... I have offered to write a document that explains my thoughts on the above issues, with a little help from my friends. It might also be useful for folks who believe that we should not place any limitations on the use of site-local addresses to write a similar document. What do you guys think? Margaret -------------------------------------------------------------------- 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] --------------------------------------------------------------------
