Erik Nordmark <[EMAIL PROTECTED]> writes: > I think our choices are: > 1. Do nothing > 2. Reserve a quarter of the IID space i.e. universal=1, group=1 becomes > explicitly reserved. > 3. Reserve half of the IID space i.e. all addresses with group=1 become > explicitly reserved.
Hi Erik, I have a side remark with respect to the u/g bits, and this might be because of a not so solid understanding of why they're there. Since u and g have approximately the same semantics that can be found in the 8bit prefix of the addres I was believing that they're necessary only for Ethernet-derived environments, where they can be exploited by specific Ethernet optimizations for multicast, etc. When other than Ethernet link layers are involved, probably the functionality of the u/g bits can be derived from the 8bit prefix? Maybe it's the 8bit prefix that should be tweaked to obtain the reservations proposed? Please take this as an aside only, I might be completely wrong of the rationale behind the u/g. Alex -------------------------------------------------------------------- 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] --------------------------------------------------------------------
