Time | Item | Who | Notes |
---|
| Admin | Kam | Record the meeting London Dec. 4 - 8, 2017 meeting (Invited by ITU-T) 2018 Face-to-Face meeting proposal - Proposed meetings: Face-to-Face Meetings
- 3 meetings have been planned.
- The dates of these 3 meeting are pretty firm now because they are selected so to avoid conflict with other SDO meetings.
|
| Layer examples | Xiang/Kam | - Previous discussion
- No further updates yet
- Discussion
- Kam asked for suggestion of example figures of devices (line cards)
|
| Ethernet OAM in G.8052.1 and IEEE 802 | Kam | - G.8052.1 Ethernet OAM UML & YANG
- G.8052 v2.04 OAM
 - The OAM details are in the MepSource/Sink/Bidirectional, ETH_TTPSource/Sink/Birectional, ETH_CTPSource/Sink/Bidirectional, MeasurementJobControl classes
- These classes will be pruned for the non OAM artifacts
 - IEEE YANG models
- Links of the latest drafts are to be provided

- Touch point of the G.8052.1 and IEEE OAM models
- The G.8052.1 Mep and ETH TP are the touch point objects to the IEEE OAM model, in particular to the IEEE MEP and Component classes
- Three possible approaches for the touch point mechanism
- Spec approach: The G.8052.1 Mep and ETH TTP/CTP decorate the IEEE MEP and Component
 - Subclassing approach: The G.8052.1 Mep and ETH TTP/CTP are subclassed from IEEE MEP and Component
- Reference approach: The G.8052.1 Mep and ETH TTP/CTP point to the IEEE MEP and Component for the needed properties
- Issues occurring during "re-engineering" of IEEE YANG modules to UML
 - YANG module name has number directly following a character: ieee802-dot1ag-cfm
The tool inserts a "-" between characters and numbers: ieee-802-dot1ag-cfm - IEEE and IETF YANG modules use the same container name with different properties in augments
Scott mentioned that this is already known and will be changed - Mapping tool maps all object classes into YANG groupings and inserts these groupings via "uses" into container or lists
The "hand crafted" YANG modules add the properties directly via "leaf"
|