| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hello! YANGsters has been talking about an issue related to MAC Address definition in the IETF and IEEE YANG files. Looking at IEEE 802.3.2-2019, the https://github.com/YangModels/yang/blob/master/standard/ieee/published/802.3/ieee802-ethernet-link-oam.yang module uses yang:mac-address from IETF 6991 ietf-yang-types module as the datatype for mac addresses instead of ieee:mac-address from ieee802-types module. The yang:mac-address definition uses a format that is not same as the ieee:mac-address. The canonical forms differ: IEEE: ieee:mac-address has a canonical form of: “-“ as the separator and upper case letters for the hex digits. IETF: yang:mac-address has a canonical form of: “:” as the separator and lower case letters for the hex digits. Within the descriptions used in IEEE 802.3-2018 Annex 31B.1 (for example), the format used is upper case letters and “-“ (or the IEEE definition). So the YANG doesn’t match the Standard. Consistency between the formats used in YANG and the descriptive text would aid clarity. Alignment between the 802 and 802.3.2 would is desired. The discussion in YANGsters has also been about what to do about the fact that the IETF definition and canonical form for mac-address is different than the IEEE definition. YANGsters in the discussion felt it best to coordinate with 802.3 to get your perspective on alignment within the IEEE and then discuss the IETF issue next. If you need further information here is a pointer to some material presented on a YANGsters call: http://www.ieee802.org/1/files/public/docs2020/yangsters-smansfield-mac-address-0420-v01.pdf regards, -scott. To unsubscribe from the STDS-802-3-YANG list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-YANG&A=1 |
Attachment:
smime.p7s
Description: S/MIME cryptographic signature