I agree that site-locals are a headache and should be carefully
considered.

However, for the purposes of the address architecture document
the new paragraph is sufficient.  It states the fundamental design
assumptions behind site-locals and that should be enough to caution
people to their use.

Stating that "more experience is needed" leads me to compare this
with flowlabel definition and really don't want to go there.

I also agree with Margarett that we shouldn't try to define the usage
of this address here.

-vlad

Keith Moore wrote:

I suggest

Site-local addresses are designed to be used for addressing inside of
networks which have no connections to external networks. Other networks
need to provide global addresses to their nodes. Use of site-local
addresses on networks with external connectivity (especially in the absence of global addresses) is known to cause problems for some applications, and such use is currently not recommended. This recommendation
may be changed once the implications of application use of site-locals are better understood. When using site-local addresses, a subnet ID may be up to 54-bits long, but it is recommended to use at most 16-bit subnet IDs, for convenience of subnet management.
--------------------------------------------------------------------
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]
--------------------------------------------------------------------



--
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Vladislav Yasevich		Tru64 UNIX - IPv6 Project Lead
Hewlett Packard 		Tel: (603) 884-1079
Nashua, NH 03062		ZKO3-3/T07


--------------------------------------------------------------------
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]
--------------------------------------------------------------------

Reply via email to