(B
(B
(B > The above text seems to assume that the "Prefix Length" in terms of
(B > RFC2461 (and its bis) is somehow tied with the address
(B > architecture...
(B >
(B > Again, I'd still like to see a consensus on the assumption itself.
(B
(B=> It's not an assumption it's a fact, more below.
(B
(B > Of course, others may have different opinions, and so it's probably
(B > too early to make a concrete suggestion. But, for what it's worth,
(B > I'd rather suggest, assuming we agree the original intention makes
(B > sense, that rfc2461bis clarify that
(B >
(B > - a prefix for on-link determination is irrelevant to the address
(B > architecture, particularly for the purpose of stateless address
(B > autoconfiguration,
(B > - thus the prefix length can be an arbitrary number between 0 and 128
(B >
(B > (with this approach, we won't have to be bothered with a particular
(B > hard-coded leading bits like "000")
(B
(B=> The above doesn't make sense to me. This is not about on-link
(Bdetermination
(Bor hardcoding bits in the IP stack or stateless address autoconfig.
(BThis is about two things:
(B
(B1. The ADDRARCH RFC specifies that the only prefixes with variable lengths
(Bare the ones with 000 in the leading bits. This is a fact.
(B2. The IAB in their response to Robert Elz' appeal clearly stated that there
(Bis
(Ban inconsistency between RFC 2461 and ADDRARCH and that it should be
(Baddressed. This is also a fact.
(B
(BI asked the WG in Seoul what to do about the above and the answer was
(Bthat some prefixes are not fixed (i.e. 000 prefixes). No one
(Bobjected to this interpretation as it seems to avoid other drastic measures.
(B
(BThe last bullet above seems to ignore ADDRARCH. I'm not sure that
(Bwe want to reenter this discussion to respin ADDRARCH.
(B
(BHesham
(B
(B===========================================================
(BThis email may contain confidential and privileged material for the sole use
(B of the intended recipient. Any review or distribution by others is strictly
(B prohibited. If you are not the intended recipient please contact the sender
(B and delete all copies.
(B===========================================================
(B
(B
(B--------------------------------------------------------------------
(BIETF IPv6 working group mailing list
(B[EMAIL PROTECTED]
(BAdministrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
(B--------------------------------------------------------------------
