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.

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

 | 2am PDT | 5am EDT | 09:00 UTC | 10:00 BST | 11:00 CEST | 12:00 EEST | 14:30 IST | 17:00 CST | 18:00 JST |

Web Conference:



(please feel free to correct and update your names (wink) Thank you very much!!!) 

Discussion items

00:00chair topic 
no update 



Next meetings

2021-08-11: Martin Skorupski

2021-08-19: Martin Skorupski

2021-08-29: Martin Skorupski

2021-09-01: Martin Skorupski

00:20WireInterface #27

transceiverIsOnList cannot be addressed

Duplicate with #28 → closed

00:10WireInterface #28

wavelengthList cannot be addressed

Decision: approved as proposed (including a change in the description of  transceiverConfigurationType::transceiverIsOn)

00:25WireInterface #29

receiveSignalIsDetectedList is unordered

Duplicate with #30 → closed

00:35WireInterface #30

rxLevelCurList is unordered

Decision: approved as proposed

00:38WireInterface #36

Check the multiplicity of rxLevelCurList[0..4] and receiveSignalIsDetectedList [0..11] 

Duplicate with #28 → closed

00:50MAC Example@Andreas Lattoch

Real world MAC example

From Andreas:

An additional status attribute from the MAC Bridging Table is needed:

The MAC-Addresses learned on a MAC-interface and managed in the switch MAC-Bridging table. The input- and output-mac-interface have the same bridge domain. The bridge domain could be a VLAN or other groupings.

The attached example show a filtered MAC Bridging Table with bridge domain filtered by VLAN on two switches that are connected via Air-Interface.


Option 1: (based on the description above)

LTP → MAC-PAC → Status → learned-mac-addresses

Note: LTP (MAC) has an association to a physical interface

This option could be associated with VLAN IDs based in server/client relations between the LTPs

MAC is server of VLAN - current modeling

MAC-IF → server → VLAN-IF (switch port) → part of many VLAN-FC (vlan-id)

Option 2: (based on implementations of some devices)

FC ->VLAN-FC-PAC (vlan-id) → Status →  learned-mac-addresses ( type: mac-address; physical-port-reference )[*]

Option 3: 

FC ->VLAN-FC-PAC (vlan-id) → VLAN-FC-PORT-PAC → Status →  learned-mac-addresses ( type: mac-address)[*]

The association to physically port goes via the reference from FC port to VLAN-IF. 

Option 4:

A table of learned-mac-address, vlan-id, physical-port-reference on MAC-FD level (like aging time).  

A central place for reducing requests by applications.

Note: due to its dynamic nature changes such changes must not be notified. 

End of the meeting


@Alexander Wenk


Current status:

  • UML-to-yang - synch_Pac - to generate a yang
  • create a workspace - with new - specify/augmentation to the core-model-1.4
  • there is a need to create a "new" UML-project

First try to generate yang model-

  • some manually modification
    • stereotype "experiment" - update of OpenModelProfile
    • then some issues found by pyang
      • duplicate of attributes - same attribute but different description
      • issue on a class which is not required - maybe we simply remove it from yang generation
      • feedback by Thorsten - UML/YANG header info missing

See feedback from Kam:

Info from 2021-07-06:

  • Alexander is going to create issues based on the feedback by vendors
00:00Mediator Instance Manager

Pre- Discussion happened yesterday 

  • info send by Thorsten on Monday 2021-05-17
  • in addition Thorsten will send the "background discussion slide"....

Mediator Instance Manager 

  • What is the protocol? NETCONF or REST or RESTCONF or ...
    • Working Assumption:  not decided
    • SIAE would like to decide based on efforts after analysis. 
    • UML include the "service" - but not the operational and maintenance layer
    • YAML (OpenAPI3) → UML (papyrus) → YANG → 


  • Any questions?
    • no questions


  • please see "App layer on top of the SDN controller" above.

Action items