> Posting only as an interested individual: > - 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?
Yes: What is the *overall* complexity of site-local as represented by the set of your questions and the lack of consensus about its functions shown by the 100's of messages in this thread? When we get a feature with this much divergence and impact, it tells us that we have a problematic design, and a good plan is often to give it up. Documenting the issues (your two documents) is a good way to go for doing so, that said. Also, could folks wear appropriate hats? Why did you not wear your wg chair hat in constructing the summary, Margaret? However, I am really not wearing an IESG hat here, since Transport AD has no special info about this (other than being averse to complexity as much as possible). Allison -------------------------------------------------------------------- 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] --------------------------------------------------------------------
