Hi,
From IEEE Std 802-2001: 3.1.4 canonical format: The format of a MAC data frame in which the octets of any MAC addresses conveyed in the MAC user data field have the same bit ordering as in the Hexadecimal Representation. 3.1.8 hexadecimal representation: The representation of a sequence of octet values in which the values of the individual octets are displayed in order from left to right, with each octet value represented as a two-digit hexadecimal numeral, and with the resulting pairs of hexadecimal digits separated by hyphens. The order of the hexadecimal digits in each pair, and the mapping between the hexadecimal digits and the bits of the octet value, are derived by interpreting the bits of the octet value as a binary numeral using the normal mathematical rules for digit significance. If we substitute the IEEE 802 text as quoted above for "Canonical format" in the suggested revised RFC 3580 text, as a sanity check, does it say what we expect?
The previous discussion also was about capital vs. non-capital being in mixed use right now. The text above leaves capitalisation undefined. Could we maybe add a sentence about hex digits being represented in capitals to make that clear? Further to this, neither the erratum nor this text here has a normative wording as per 2119, which I think is what Avi was originally aiming for? In any case, IMHO, an erratum just to reshuffle the text is a bit overkill. If it were to introduce normative wording though, I'd feel better about issuing it.
Yeah, let's limit the errata to things that are actually wrong or missing,as opposed to engaging in unnecessary re-wording.
Agree. Greetings, Stefan Winter -- Stefan WINTER Ingenieur de Recherche Fondation RESTENA - Réseau Téléinformatique de l'Education Nationale et de la Recherche 6, rue Richard Coudenhove-Kalergi L-1359 Luxembourg Tel: +352 424409 1 Fax: +352 422473 -- to unsubscribe send a message to radiusext-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: <http://psg.com/lists/radiusext/>