20 likes | 207 Views
Transfer of Ethernet MIB work to IEEE 802.3. Benoit Claise, Dan Romascanu. History, Present and Future. There was once a hubmib WG RFC 2108 – Ethernet Repeater Devices RFC 3621 - Power Ethernet MIB RFC 3635 - Ethernet-like Interface Types RFC 3637 - Ethernet WAN Interface Sublayer
E N D
Transfer of Ethernet MIB work to IEEE 802.3 Benoit Claise, Dan Romascanu
History, Present and Future • There was once a hubmib WG • RFC 2108 – Ethernet Repeater Devices • RFC 3621 - Power Ethernet MIB • RFC 3635 - Ethernet-like Interface Types • RFC 3637 - Ethernet WAN Interface Sublayer • RFC 4836 - Ethernet Medium Attachment Units (MAUs) • RFC 4837 - Ethernet Passive Optical Networks (EPON) • RFC 4878 - Operations, Administration, and Maintenance (OAM) Functions on Ethernet-Like Interfaces • RFC 5066 - Ethernet in the First Mile Copper (EFMCu) Interfaces MIB • WG terminated in 2006, mail list kept active, work transferred to IEEE 802.3.1 • Process similar to RFC 4663 but no RFC was written • Some problems surfaced as result of RFC5066 transfer issues (in ADSLMIB WG) and as part of the IETF-IEEE relation context • Most solved in direct interaction with the IEEE 802.3.1 WG • Proposal – write an informational document similar to 4663 for the Ethernet MIB transferred • Co-authored with IEEE 802.3.1 chair • A table mapping the old IETF MIB names with the corresponding new IEEE ones • Clarifications/rules on the IETF-IEEE interactions, mailing lists, reviews • Clarifications on the intellectual property considerations • Make the IETF RFCs Historical? – OPEN ISSUE • Is the OPSAWG interested in taking this work as a chartered item?