Skip to end of metadata
Go to start of metadata

 | 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-11-03: Martin Skorupski

Note: time zone shift in Europe

| 3am PDT | 6am EDT | 10:00 UTC | 10:00 GMT | 11:00 CET | 12:00 EST | 15:30 IST | 18:00 CST | 19:00 JST |

2021-11-10: Martin Skorupski 

Note: time zone shift in North America

| 2am PST | 5am EST | 10:00 UTC | 10:00 GMT | 11:00 CET | 12:00 EST | 15:30 IST | 18:00 CST | 19:00 JST |

2021-11-17: Martin Skorupski 

2021-11-24: Martin Skorupski

00:05Summary from yesterdayThorsten Heinze Please see
00:05Marketing@Andreas Lattoch

Announcement of the activities

Brain storming

  • report to ONF about large scale of the model in production
  • testing
  • beyond PoC
  • TIP
  •  movement from PoC to Production

AI Martin: create a word doc and share with Senthilvel and Eduardo first before sharing with bigger group.


  • doc template is out but more test is required
  • AI Martin: ONF Activities -reach out to Lyndon

@Alexander Wenk


Some answer about modeling and mappings can be found here

Looks like there are different versions with similar but different content.

Q: Would it make sense to share the current generated yang already?

  • core-model-1-4.yang → still pending
  • sync-model-1-0.yang → could be generated


  • sync-model-1-0.yang
    • Clock/encapsulated-fc* [uuid] should be removed (from core-model-1-4.yang) 
  • core-model-1-4.yang
    • 11 findings were documented by Prathiba and needs to be addressed - work is ongoing

Centralized alarm list

(alarm definition, capability and notification)

Presentation from yesterday

AI Martin

check with TAPI and ONF

Contribution by Eduardo (see attachment)

MEG: Maintenance entity group

MEP: Maintenance end point

MIP: Maintenance intermediate point


ONF and TAPI are targeting, notification and streaming interface on service level. which is a bit different of device-model. However, it is possible to map from device- via network- into service-model.

00:59EthernetContainer #46

min-elements shall be removed from problem-kind-severity-list

  • details to be discussed in future meetings.



Relation between planning and actual data from the network

@Andreas Lattoch

Quick synch from last week

  • connector types to be standardized
  • work in progress - to be continued
  • Current work bases on the "EquipmentModel"

updated proposal

  • holders identified by a, c, ...
  • connectors identified by 0, 1, ...

See updated document:

00:00Mediator Instance Manager

Pre- Discussion happened yesterday 

  • info send by Thorsten on Monday 2021-05-177
  • 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