Versions Compared

Key

  • 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:

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:03

Admin

Next meetings

2021-10-06: Martin Skorupski

2021-10-13: Martin Skorupski

2021-10-20: Martin Skorupski

2021-10-27: Martin Skorupski

00:03issues labeled "yang to be provided"@PrathibaA list of related "issues" send by email to Martin → handled "offline" to be presented next week
00:05

VLAN-FD #12

Martin Skorupski 

priorityToTrafficClassMappingList to be added

Decision: approved as proposed

00:08

VLAN-FD #15

Martin Skorupski 

component-id lack a default value

Decision: approved as proposed

00:11MAC-FD #5 (learned MAC Addresses)Martin Skorupski 

Technology specific amendment to the ForwardingDomain class for documenting current forwarding according to IEEE 802.1 .

Decision: approved as proposed

00:15

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"
00:2045Synchronization

@Alexander Wenk

@Prathiba

Some answer about modeling and mappings can be found here

Working Assumption to be proven about figure 7-21 – UML model diagram – CdSpecificView

  • PtpDomainConstraint_Pac is a model OUTSIDE of the device (control-construct)
    • There is the first expectation that all attributes are laready in the LTP(Sync) and CLOCK object class.
  • NeSync_Pac
    • under the assupbtion that "Ne..." mean "NetworkElement..." the "NeSync_Pac" could be called "ControlConstructSync_Pac" and attached to the ControlConstruct itself

END OF THE MEETING

00:00Mediator Instance Manager

Pre- Discussion happened yesterday 

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