Liaison statement
Liaison response to ITU-T SG15 and MEF on YANG for CFM
Additional information about IETF liaison relationships is available on the
IETF webpage
and the
Internet Architecture Board liaison webpage.
State | Posted |
---|---|
Submitted Date | 2017-06-19 |
From Group | IEEE-802-1 |
From Contact | Glenn Parsons |
To Group | OPS |
To Contacts | Warren Kumari <warren@kumari.net> Benoit Claise <bclaise@cisco.com> |
Cc | Benoit Claise <bclaise@cisco.com> Eric Gray <Eric.Gray@Ericsson.com> The IETF Chair <chair@ietf.org> Warren Kumari <warren@kumari.net> |
Response Contact | Paul Nikolich <p.nikolich@ieee.org> Glen Parsons <glenn.parsons@ericsson.com> John Messenger <jmessenger@advaoptical.com> |
Purpose | For information |
Attachments | liaison-response-CFM-YANG-0517-v01 |
Body |
We are thankful for the MEF Forum and ITU-T SG15 liaison responses to our March 16, 2017 liaison on progressing information and data modeling for Ethernet OAM. We are appreciative of MEF Forum and ITU-T SG15 expressions of support for, and acceptance of our proposal. We also took MEF Forum and ITU-T SG15 feedback into consideration during the development at our May 2017 interim meeting of the Project Authorization Request for a new IEEE 802.1 project 802.1Qcx “YANG Data Model for Connectivity Fault Management”. As such, we plan for project 802.1Qcx to: • Specify a UML information model and YANG data model for IEEE Std 802.1Q-specified CFM compatible with naming conventions used in IEEE 802.1, ITU-T SG15 and MEF Forum; • Cover OpCode values 0-31 and 96-255 per ITU-T SG15 proposal as we also agree that YANG modules should be developed within the organization that has responsibility for the corresponding protocol; • Specify YANG modules providing as much independence as possible from the underlying data plane to allow applicability over the various transport networks that can support an Ethernet service; • Be developed taking as input MEF 38 and MEF 39, as well as the corresponding errata that MEF previously identified and communicated to us; • Be progressed following the IEEE 802 standard development process and leverage GitHub (https://github.com/YangModels/yang/tree/master/standard/ieee/802.1) in support of agile and collaborative development of the modules to be integrated in the final specification. Regarding the MEF Forum work above the Network Element level that could have overlap in the objects and parameters with our work, we will share our work as it progresses to facilitate alignment. We look forward to joint participation in the development of information and data modeling for CFM. IEEE 802.1 meets next 10-13 July 2017 in Berlin, Germany and 5-8 September 2017 in St. John’s, Newfoundland, Canada. |