Skip to end of metadata
Go to start of metadata

 | 2am PST | 5am EST | 10:00 UTC | 10:00 GMT | 11:00 CET | 12:00 EET | 15:30 IST | 18:00 CST | 19: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:01

Admin

2022-02-02: Martin Skorupski

2022-02-09: Martin Skorupski

2022-02-16: Martin Skorupski

2022-02-23: Martin Skorupski

00:05CoreModel #23Daniela Spreafico 

Identities for 'switch-selection-reason' are missing

  • Please see the proposal made for 2022-01-26
00:10Equipment #16@Andreas Lattoch

Identifier at the original management interface to be mapped

  • Please see the proposal made for 2022-01-26
00:15Text for ONF @Andreas Lattoch

Info: proposed text send to Denise Barton <denise@opennetworking.org> ...

00:16

CoreModel #22
SyncModel #7
SyncModel #8

@Prathiba Jeevan

Removing embedded clock attribute from logical termination point

  • Please see the proposal made for 2022-01-26 (modified on 2022-01-18)
  • Please see proposals:
00:30

Centralized alarm list

(alarm definition, capability and notification)

Continue UML Modeling

  • Alarm History
    • notification log like (feedback from yesterdays discussion)



END OF THE MEETING

00:00Relation between planning and actual data from the network

Please see the latest version of the proposal: 
https://wiki.opennetworking.org/download/attachments/265093121/proposal-sequence-id.0.2.docx?api=v2

00:35Mediator 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 → 

2021-05-25

  • Any questions?
    • no questions

2021-06-16

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

2021-11-24

  • Introduction to the topic 
  • functional requirements
  • how to address security constrains and its key management
  • impact on MediatorInstanceManager
    • including logging mechanism
  •  option to reuse code provided by TEF

2021-12-01

  • Create Mediator Instance
    • Q: Is device-port missing?
    • A: no - because this is knowledge of the Mediator-Instance
    • (Management) Protocol and protocol version and other protocol configuration parameters : depend on 'device-kind-name'.
    • Further Configuration comes as general configuration with the "LoadFile" (e.g. NETCONF port range, SNMP version, SNMP TRAP port)

    • Q: Release version for in device parameters?
    • A: also here the mediator implementation knows what to do. 

    • Q: device-kind-name: enum vs. string
    • A: type sting → ok but known values must be agreed between vendor and operator OPEN...... to be continued tomorrow.

2021-12-15

  • some "security" findings by TEF IT - to be addressed - some repos changed to "private" - access by git invitations - please send github accounts to Thorsten. 


Action items