On Thursday, August 28, 2003, at 02:45 AM, Brian E Carpenter wrote:



4 Deprecation


   This document formally deprecates the IPv6 site-local unicast prefix
   defined in [RFC3513], i.e. 1111111011 binary or FEC0::/10. The
   special behavior of this prefix MUST no longer be supported in new
   implementations.

What does this last sentence exactly means? no special rules in address selection?
no special site ID treatment? It would be better to reference particular sections
of existing RFCs that gets obsoleted.


Btw, how can an IETF document say: an MUST not support X" ? This makes little sense to me...
Now, what is a new implementation?


I would rather like to see some text like:
The following section of RFC x,y,z.... are obsoleted:

section a.b.c of RFC XXXX
.....


 The prefix MUST NOT be reassigned for other use
   except by a future IETF standards action. Future versions of the
   addressing architecture [RFC3513] will include this information.

   However, router implementations SHOULD be configured to prevent
   routing of this prefix by default.

This seems to contradict the initial sentence I have just commented on.



- Alain.


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