Correct. That is NOT the issue. 3041 and 3041 bis use "randomly" generated identifiers that are "local" (not "global" as mac-derived identifiers are) and there are some RFCs that RESERVE certain ranges within this "local" space. We need some place to document that list of reserved ranges so that a "randomly" generated identifiers don't use those reserved ranges. Any future assignment of reserved local identifiers always run the risk of having existing implementations generate identifiers that may conflict.
- Bernie -----Original Message----- From: Christian Huitema [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 27, 2007 12:38 AM To: Suresh Krishnan Cc: Alexandru Petrescu; ipv6@ietf.org Subject: RE: Reserved interface identifier registry > Not really. You are assuming here that all IIDs are generated from MAC > addresses. IIDs can be generated using other methods like CGA, Privacy > Addresses etc. Hence reserving a range of MACs/OUIs is not sufficient. Actually, the non Mac derived identifier include a bit that indicate that "this is not a reserved value", and thus don't conflict with MAC-derived identifiers. -- Christian Huitema -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 -------------------------------------------------------------------- -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
