Due to a ransomware attack, the wiki was reverted to a July 2022 version. . We apologize for the lack of a more recent valid backup.



19 December 2017




  • Ethernet OAM Information/Data Models

Discussion Items

  • 2017 YearEnd call plan
    • Discussed and agreed on the following plan:
      • Keep Dec. 19 OT-IM call
      • Keep Dec. 21 OIMT calls
      • Cancel Dec. 26 OT-IM call
      • Cancel Dec. 28 OIMT calls
      • Cancel Jan. 2 call (Not available: Yuji, Rod, Andrea, Aikra)
      • Keep Jan. 4 calls (Not available: Rod)
 Ethernet OAM IM/DMKam
  • G.8052.1 UML
    • Kam presented the further update on the ETH TTP & CTP pruning
      • Sketch PR TP
      • Need to check if IEEE YANG already has support for lpDirection, terminationState, and layerProtocolName
      • Prunned out the alarm related attributes of TTP (i.e., alarmStatus, currentProblemList, and alarmSeverityAssignmentProfliePointer).
        • OAM related alarm is covered by the fault causes at the MEP, such as cUNP, cMMG, etc.)
      • Need to verify if the attributes _multiplexing, _ethCtpSink, _MepSink, _vlanConfig, _filterConfig, and ieeecompoinet are covered in the IEEE bridge DM.
        For example, the multiplexing attribute (EthServerTtpSink_Pac) consists of: PriorityRegenerate, portVid, priorityCodePointConfig, etherType, frametypeConfig, and filterConfig).



IEEE 802 YANG OAM Modules in Scope:

Findings during re-engineering of ieee802-dot1ag-cfm.yang into UML

  • Issues with the YANG files (because the YANG files are still drafts)
    • No such paths:

      1. ieee802-dot1ag-cfm.yang::path "/dot1q:bridges/dot1q:bridge/lldp:lldp/lldp:port/lldp:remote-systems-data/lldp:chassis-id"

      2. ieee802-dot1ag-cfm.yang::path "/dot1q:bridges/dot1q:bridge/lldp:lldp/lldp:port/lldp:remote-systems-data/lldp:port-id"

      3. ieee802-dot1ab-lldp.yang::augment "/dot1q:bridges-state/dot1q:bridge"

    • Errors

      1. ieee802-dot1ag-cfm.yang::container fault-alarm--mep-highest-pr-defect

      2. ieee802-dot1ag-cfm.yang::”Automagically

  • Mapping Issues
    1. How to model YANG Built-In Type “bits”?
      Example: mep-defects modeled as a list of enumeration
      typedef mep-defects {
          type bits {
            bit b-def-rdi-ccm {
              position 0;

It was agreed, that a mapping from UML to YANG "bits" built-in-type is necessary.
A third way of enumeration mapping needs to be defined. I.e., enumerations can be mapped to YANG by either using the “enumeration” built-in type or via the “identity”/"base" statement or via the “bits” built-in type.

The YANG “bits” built-in type represents a bit set where each bit has an assigned name and shall be used when the enumeration is fixed and an efficient data modeling is preferred.

The Enumeration property “isLeaf” and the attribute property OpenInterfaceModel_Profile::OpenInterfaceModelAttribute::encoding together are used to direct the mapping tool to perform the appropriate mapping. isLeaf = true AND encoding = NA -> maps to typedef with enum statement; isLeaf = true AND encoding = BITS -> maps to typedef with bits built-in type; isLeaf = false -> maps to identity/base.

Using “bits” (isLeaf = true, encoding = BITS)

typedef enumeration-1 {
     type bits {
          bit LITERAL_1 {
               position 0;
          bit LITERAL_2 {
               position 1;
          bit LITERAL_3 {
               position 2;

container class-h {
            leaf attribute-1 {
                        type enumeration-1;
                        default LITERAL_2;

Action Items


  • Scott MansfieldBernd Zeuner, and Hing-Kam Lam: Use the 2 January 2018 Tuesday OT-IM slot to continue re-engineering the IEEE 802.1Q CFM YANG (draft) into Papyrus UML. Note that although there will be no official OT-IM call on Jan. 2nd, 2018, people are welcome to join Scott/Bernd/Kam's call. Same GoToMeeting bridge.