Just a quick comment below >There was a bunch of stuff about the M and O flags in RFC2462, almost >all of which was removed in RFC4862. In RFC2462, the word >"should" (*not* capitalised) was used, along with phrases like "is to >be".
=> "should" does not need to be capitalised to indicate that it's a keyword. It's a common misunderstanding. Hesham > >Then there is RFC 4861 (neighbor discovery) which says: > > M 1-bit "Managed address configuration" flag. When > set, it indicates that addresses are available via > Dynamic Host Configuration Protocol [DHCPv6]. >[...] > O 1-bit "Other configuration" flag. When set, it > indicates that other configuration information is > available via DHCPv6. > >Anyway, I've been working on the basis that the M and O flags are >advisory and not prescriptive. That is, they do not *require* the host >to do anything. > >Regards, K. > >-- >~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >Karl Auer (ka...@biplane.com.au) >http://www.biplane.com.au/kauer > >GPG fingerprint: AE1D 4868 6420 AD9A A698 5251 1699 7B78 4EEE 6017 >Old fingerprint: DA41 51B1 1481 16E1 F7E2 B2E9 3007 14ED 5736 F687 >-------------------------------------------------------------------- >IETF IPv6 working group mailing list >ipv6@ietf.org >Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 >-------------------------------------------------------------------- -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
