> > ... You just ASSUME something I think we all understand is not > > possible to guaranty. There will be collision, deal with it. > > Let me make the point again. > It is a fact (not an assumption) that RFC4291-conforming IIDs either have > u=0, in which case other bits may have any values, or, if they have have g=1, > have a specified structure. So far the only such structure is that of IEEE > derived IIDs. With it, g=0 because these IIDs are those of unicast addresses.
However, there is nothing which enforces RFC4291-conforming IIDs for (for instance) statically configured IPv6-addresses. So in what way do well defined u/g values for RFC4291-conforming IIDs help you? Steinar Haug, AS 2116 -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
