Gentlemen,
I notice that many of previously assigned values for other address
schemes have been removed and replaced by "unassigned".
I am not sure I fully understand the distinction between reserved and
unassigned. It would seem to me that in neither case is it safe to
use one of the values for any purpose whatsoever, since a reserved
value might subsequently become unreserved, and an unassigned value
might subsequently become assigned. In either case, any intermediate
use will lead to a potential encoding clash.
I see that the IPX class has been replaced by unassigned, also some
other previous classes like geographic and provider-based have also
been removed.
This seems to imply that these schemes are not seen as being used in
the foreseeable future, and even their use as previously specified
might lead to an encoding clash at some later date. Presumably these
values could be used for some other completely different scheme in
the future, unrelated to their previous incarnation.
Is my interpretation and conclusion correct?
On the other hand, I could see how these values might say reserved
rather than unassigned. If a value is reserved is interpreted as
never will be assigned, then it would be safe to use in its original
context. But if this were the case why not leave them in as before?
Regards
Keith
At 1:57 PM -0700 06/10/2000, Bob Hinden wrote:
>Erik, Thomas,
>
>The chairs of the IP Next Generation working group, on behalf of the
>working group, request that the following document be published as
>an Draft Standard:
>
> Title : IP Version 6 Addressing Architecture
> Author(s) : B. Hinden, S. Deering
> Filename : draft-ietf-ipngwg-addr-arch-v3-02.txt
> Pages : 25
> Date : 05-Oct-00
>
>A working group last call for this document was completed on April
>10, 2000 and the document was discussed at the Adelaide IETF
>meeting. The -02 version of the draft resolves issues raised during
>the working group last call and subsequent discussion.
>
>This document will obsolete RFC2373. Changes from RFC2373 are
>listed in Appendix B.
>
>Bob Hinden / Steve Deering
>IPng Working Group Co-Chairs
>
>--------------------------------------------------------------------
>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]
>--------------------------------------------------------------------
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
