| 45 min | Ethernet CFM | Kam | - IEEE 802.1Qcp Bridge
- The YANG is considered complete.
- It is waiting for publication
- IEEE 802.1Qcx CFM YANG
- Further updates posted on June 25th
- 4 modules:
- Manual translated UML: To be done
- ITU-T G.8052.1 UML
- Yet to confirm on the MIP (Full, Half, and RAPS capable Half) and Mac Address of MEP & MIP
- Karm shared the Terminaton Point augmentation and P&R
- Augmentation: g8052.1-tp.png
- P&R:
- The following attributes will be refactored by moving to EthCsfPac
- _csfReport:CsfReportSink_Pac / csfReport:Boolean
- _csfRdiFdiEnable:CsfRdiFdiEnableSink_Pac / csfRdiFdiEnable
- _csfConfig:CsfConfigSource_Pac / csfConf
- _csfRdiFdiEnable:CsfRdiFdiEnableSource_Pac / csfRdiFdiEnable
- Given that CFM provides only the highest priority (critical) defects, the G.8052 currentProblemList should be retained.
- Italo Comment: provide the rationale of pruning/retaining for the attributes in an additional column or excel.
- Italo Comment: Relationship between the ITU-T MEG and IEEE MaintenanceDomain (MD) & MaintenanceAssociation (MA):
- Kam shared the following: While in the IEEE CFM model the MEG is not explicitly defined, the MEG concept was explained in the following figure from Marc Holness, in which a <MD,MA> pair represents a Maintenance Group (MEG).
 - When a MEP is created, it will reference an Interface and a Maintenance Group. From IEEE 802.1Q perspective, the Interface would be a Bridge-Port
- Akira comment: How will IEEE CFM do the performance monitoring (PM).
- Scott: IEEE will not do PM
- Kam: Ethernet PM is defined in ITU-T. People should use the ITU-T PM, which is G.8052.1 doing to augment the IEEE CFM with the Ethernet PM.
|
