Open Transport Configuration & Control
Space shortcuts
Expand all   Collapse all
Child pages
  • 2021-11-03 5G-xHaul Meeting notes

Versions Compared

Old Version 2

changes.mady.by.user Martin Skorupski

Saved on

compared with

New Version Current

changes.mady.by.user Martin Skorupski

Saved on

Key

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

 | 3am PDT | 6am EDT | 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!!!) 

Info to: 

Goals

  • going forward


Mailings

Discussion items

TimeItemWhoNotes
00:00Chair topic 
no update 

00:05

Admin

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

2021-12-01: Martin Skorupski

00:0504Marketing@Andreas Lattoch

Announcement of the activities

  • report creation ongoing
00:1505Synchronization

@Alexander Wenk

@Prathiba

Some answer about modeling and mappings can be found here

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

YANG generation process:

  • core-model-1-4.yang → pending (5/11 issues are done)
  • sync-model-1-0.yang → generated but requires core-model updates
00:1006

Centralized alarm list

(alarm definition, capability and notification)

Thorsten Heinze Alex Stancu 

Info by Alfredo

  • TAPI updates for current and historical alarms list in the pipe

How to continue?

Agreements

  • alarm handling should be centralized from modeling point of view
  • separation function between current alarm list and history alarm lists 
    • consequence: remove all the alarm list from PAC
  • Expanding for alarm fields
    • what fields are missing?
    • AI Eduardo: to validate the expected functions against IETF-ALARMS
  • Idea: IETF-Alarm functions under core-model 

END OF THE MEETING

00:

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:

https://wiki.opennetworking.org/download/attachments/265093121/proposal-sequence-id.docx?api=v2

00:00Mediator Instance Manager

Thorsten Heinze

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.

Action items