Date: Sun, 17 Mar 2002 09:07:07 -0800
From: "Tony Hain" <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
| Yes this is a fact of life for the end user of the space, but the
| documents are targeted at various vendors supplying that end user. While
| the end user can choose to set the bits any way they like, their vendors
| are expected to follow a consistent set of rules so the end user knows
| what they are getting.
Wonderful. That's the right approach - can we all agree on that?
First, that would answer Alberto's question the same way I did - he
can config his DHCP server to return the u (& g) bits in any state he
likes.
Second, it will mean that the gibberish in 2373bis about u==1 implying
a globally unique IID can go in the trash where it belongs, and we
can keep the u bit the same as it was in 2373. That is, we tell the
implementors what they're supposed to do, but not go on to ascribe some
unrealisable meaning to the value of the bit if seen in an address.
kre
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
