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:

https://thorsten-heinze-telefonica-de.webex.com/thorsten-heinze-telefonica-de/j.php?MTID=m849236edb092dffd10071725f5b8839f 

Invited:

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

Discussion items

TimeItemWhoNotes
00:00chair topic 
no update 

00:05

Admin

Next meetings

2021-08-04: Martin Skorupski

2021-08-11: Martin Skorupski

2021-08-19: Martin Skorupski

2021-08-29: Martin Skorupski

00:06Hybrid MW Structure #23

supportedAlarmList to get DefaultValue and *

Decision: approved as proposed

00:07Pure Ethernet Structure #20

supportedAlarmList to get DefaultValue and *

Decision: approved as proposed

00:08TDM Container #14

supportedAlarmList to get DefaultValue and *

same subject as Hybrid MW Structure #23 → same solution, but min element 2 → multiplicity goes to *

Decision: approved as proposed

00:09WireInterface #33

supportedAlarmList to get DefaultValue and *

same subject as Hybrid MW Structure #23 → same solution

Decision: approved as proposed

00:10Pure Ethernet Structure #14

All Attributes at all Notifications should be IsReadOnly==1

Decision: approved as proposed - closed!

00:11Pure Ethernet Structure #15

objectClass of CurrentPerformace and HistoricalPerformance data type is not needed

Decision: approved as proposed - closed!

00:34Pure Ethernet Structure #16

Object References in CurrentPerformance to be deleted

Decision: approved as proposed - closed!

00:12Pure Ethernet Structure #17

Administrative and Operational State at CurrentPerformance

Decision: approved as proposed - closed!

00:13TDM Container #9

Object References in CurrentPerformance to be deleted

Decision: approved as proposed - closed!

00:14TDM Container #10

Administrative and Operational State at CurrentPerformance

Decision: approved as proposed - closed!

00:14TDM Container #12

number-of-historical-performance-sets and time-of-latest-change is present in yang file but not in UML for historical-performance

Decision: approved as proposed - closed!

00:15WireInterface #20

All Attributes at all Notifications should be IsReadOnly==1

Decision: approved as proposed - closed!

00:16WireInterface #21

objectClass of CurrentPerformace and HistoricalPerformance data type is not needed

Decision: approved as proposed - closed!

00:17WireInterface #22

Object References in CurrentPerformance to be deleted

Decision: approved as proposed - closed!

00:18WireInterface #23

Administrative and Operational State at CurrentPerformance

Decision: approved as proposed - closed!

00:20WireInterface #24

wireInterfaceStatus::receive-signal-is-detected should be receive-signal-is-detected-list
Decision: approved as proposed - closed!

00:22WireInterface #25

Default value for rx-level-cur

Decision: approved as proposed - closed!

00:25WireInterface #26

time-of-latest-change: wrong type

Decision: approved as proposed - closed!





00:26WireInterface #32

autoNegotiationPmdList cannot be addressed

Proposal made - however, quick follow up about the NETCONF/RESTCONF capability of config for leaf-lists.

Thorsten is going to check if the description in the proposal needs to be changed or not ...

00:37WireInterface #35

Replacing restart-pmd-negotiation-is-on by RPC

>> Proposal made for 18th August

00:50MAC Example@Andreas Lattoch

Real world example

issue should be created in MAC Interface


End of the meeting





00:15Synchronization

@Alexander Wenk

@Prathiba

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 → 

2021-05-25

  • Any questions?
    • no questions

2021-06-16

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

Action items