The authors of RFC 4291 chose not to use the upper case normative keyword convention defined in RFC 2119. Therefore, 'required' means what in means in plain English (i.e. REQUIRED in RFC2119ish).
Brian On 2011-07-15 19:03, Washam Fan wrote: > Hi, > > I quoted this paragraph from RFC4291: > > For all unicast addresses, except those that start with the binary > value 000, Interface IDs are required to be 64 bits long and to be > constructed in Modified EUI-64 format. > > But I am not sure how to interpret the text in a correct way. > > If I assign an ordinary unicast address (except reserved anycast > addresses mentioned in RFC5453) to an interface and the address > doesn't start with 000, MUST the prefix be 64 bits? MUST the IID be > constructed in Modified EUI-64 format? > > We are providing WebUI for our customer to manually assign IPv6 > addresses, we want to do hygiene check before the actual move. > > Thanks in advance > washam > -------------------------------------------------------------------- > IETF IPv6 working group mailing list > [email protected] > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 > -------------------------------------------------------------------- > -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
