What should a node do upon reception of a prefix option with the prefix length set to a value >64?
The issue can be stated more accurately to say: What should a host do upon reception of a prefix option with the prefix length set to a value != 64? So far I haven't received any comments on this issue. It seems that there are few options to consider: 1. A host should ignore this field if it's not set to 64 and form an address based on the leading 64 bits. 2. A host should ignore the field if not set to 64 and log an error. The host MUST NOT form an address based on this prefix. 3. This field should be removed and a 64-bit prefix always assumed by hosts. 4. Leave this field as is and design a mechanism that allows the host to form an address based on the length of the interface identifier (i.e. 128 - prefixlen). Realistically I don't think we should go with option 1. Option 4 requires more work and I don't know how we can proceed with this dependency on another spec. In any case, options 2,3,and 4 are the most realistic. Note that none of the options above are backward compatible. In a sense, we can't be backward compatible because this seems like a bug given the current address architecture RFC. Which option should we pick to solve this problem? Other options are certainly welcome. Hesham -------------------------------------------------------------------- IETF IPv6 working group mailing list [EMAIL PROTECTED] Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
