Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 2
Next »
Date
27 March 2018
Attendees
Goals
- Packet Examples
- IEEE 802.1Qcp CFM Data Model
Discussion Items
Time | Item | Who | Notes |
---|
20 | Packet Examples | Xiang | |
| IEEE 802.1Qcp CFM Data model | Kam/Bernd | - March 19 Joint discussion in the Q14/15 virtual meeting
- Reviewed the 2018-03-12 CFM YANG and the re-engineered UML (CD06r1)
- Bernd noted that the re-engineered UML is purposely to be as close as possible to the YANG tree structure, so the output UML is not optimal from UML modelling perspective. For examples some object classes (such as cfm-stacks, default-md-levels, config-errors, maintenance-domains) are unnecessary (every leaf has to be unnecessarily wrapped in a container)
- Main changes wrt. the February 21st version:
- MEP is now under the MD/MA/MAComponent
- ContinuityCheck, Loopback and Linktrace belong to Mep
- xxxNameType und xxxNameFormatType combined to xxxNameChoice
- Main editorial changes: Convert tabs into spaces, replace "IEEE 802.1Q-2017 Clause xxx" by "xxx of IEEE Std 802.1Q-2018".
- Need to understand
- MaintenanceAssociationComponent
- Why still 7 unused type definitions
- March 20 off-line discussion with Marc Holness, BZ, SM, ND, KL
- MaintenanceDomain:
- Confirm the use of mdIndex for key. This is to support G.8013, in which MD name is null
- Since mdIndex is the key, it should be mandatory, i.e., Integer [1].
- MaintenanceAssociation:
- Confirm the use of maIndex for key, although there is already the attribute maNameChoice which can meet the G.8013 needs. This is to have consistent approach as MD indexing.
- MainenanceAssociationComponent
- Marc clarify the purpose of this object class. In certain bridges, there are multiple components. For examples, in Provider Backbone Bridge (PPB), there are I component, B component. Most common is VLAN component. Note that BBF will not use component. Alternative approach for not using this class could either be a default component instance or allow direct association from Mep to MaintenanceAssociation.
- Agreed that the maintenanceGroup attribute is useful. In G.8052, there is such an attribute even though no explicit MaintenanceGroup object class is defined.
- Agreed that the G.8013/Y.1731 CCM-based LM (proactive) be modelled by using Spec class on the ContinuityCheck (i.e., augmenting/decorating the ContinuityCheck class with the LM related attributes/properties).
- Agree that the G.8013/Y.1731 measurement jobs (such as DM, LM, SLM, …) could be modelled by using the Specifying/decorating the CFM Mep class
- In the next meeting, aim to illustrate how instances of Mep and Mip are created
|
Action Items