I was always under the assumption that the prefix is fe80::/64, and not fe80::/10. However, the latest and the best version of the Addressing Architecture [RFC 3513] states the prefix as fe80::/10. Does it mean that fe81::/16 can also be used as a link local prefix (note : section 2.5.6 in RFC 3513 says that the next 54 bits after the prefix should be zero)?
A grep for fe80 in my rfc repository yields (note: the fe80::/64, and fe80::/10) ---- rfc2464.txt:179: the prefix FE80::/64. rfc2467.txt:252: prefix FE80::/64. rfc2470.txt:299: prefix FE80::/64. rfc2491.txt:1259: token, as defined above, to the prefix FE80::/64. rfc2497.txt:135: prefix FE80::/64. rfc2529.txt:184: the prefix FE80::/64. rfc2529.txt:296: cases with the prefix FE80::/64. Note that the prefix- rfc2546.txt:98: The link-local prefix (FE80::/10) MUST NOT be advertised rfc2590.txt:480: above, to the prefix FE80::/64 [AARCH]. rfc2740.txt:1751: Link-local Interface Address = fe80:0001::RT3 rfc2772.txt:156: This link-local prefix (FE80::/10) MUST NOT be advertised through rfc2893.txt:966: the prefix FE80::/64. rfc3146.txt:152: the prefix FE80::/64. rfc3484.txt:1034: fe80::/10 33 1 rfc3513.txt:327: Link-local unicast 1111111010 FE80::/10 ---- Am I missing something? Thanks, CP -------------------------------------------------------------------- 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] --------------------------------------------------------------------
