1. Pages
2. …
3. Open Transport Configuration and Control Home
4. 5G-xHaul
5. 5G-xHaul Call-in Details & Notes
6. 2021-07-07 5G-xHaul Meeting notes

Page History

00:05

RMON - EthernetContainer #45

MacInterface #24

Are there RMON counters to be moved from MacInterface to EthernetContainer?

Editorial modification on the proposal - no change of objective or content.

Decision: proposal is approved.

Deleting MacInterfaceConfiguration::InterfaceIsOn

Decision: proposal is approved.

Deleting MacInterfaceConfiguration::performanceMonitoringIsOn

Decision: proposal is approved.

ObjectCreationNotification::_objectIdRef should be IsReadOnly==1

Decision: proposal is approved.

ObjectDeletionNotification::_objectIdRef should be IsReadOnly==1

Decision: proposal is approved.

Object References in CurrentPerformance to be deleted

Decision: proposal is approved.

Object References in CurrentPerformance to be deleted

Decision: proposal is approved.

maximum-frame-size might have discrete value ranges

kindly request to vendors,

• Is the maximum-frame-size attribute supported at all
  • Answer yes!
• with discrete values?
  • Answer yes! - but also as continuous range in other cases.
• for Tuesday June-29th 

Decision: proposal is approved.

link-loss-forwarding-delay might have discrete values

kindly request to vendors,

• Is the link-loss-forwarding-delay attribute supported at all
  • Answer yes (for some vendors)
• with discrete values?
• for Tuesday June-29th 

Decision: proposal is approved.

interfaceStatus, PowerIsUp, LinkIsUp, OperationalState and AdministrativeState at the LTP

Please have a look - this is the last open in AirInterface

radio-power-is-up: not supported by many of the vendors (as an operational attribute): AirInterface #52

interface-status: vendors need to double check if only enabled/disabled is supported, or the entire IETF operational status values; if only enabled/disabled is supported, the attribute could be deleted and operational-state of the LTP could be used instead

Discussion to be continued.

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

• https://github.com/openBackhaul/core/wiki/2021-06-22-Interface-call#synchronization-model

Info from 2021-07-06:

• Alexander is going to create issues based on the feedback by vendors

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.