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

Page History

00:05

txEthernetBytesMaxM is not supported by hardware implementations

Decision: proposal is approved.

Performance Counters to be complemented

Decision: proposal is approved.

Naming of Performance Counters to be harmonized

Decision: proposal is approved.

Deleting unsupported performance attributes

Decision: proposal is approved.

00:15

oversizedFramesIngress to be made available as status value (statistics), too
Already Decided! 

undersizedFramesIngress to be made available as status value (statistics), too

Already Decided! 

jabberFramesIngress to be made available as status value (statistics), too

Already Decided! 

fragmentedFramesIngress to be made available as status value (statistics), too

Already Decided! 

Adding PerformanceValue for Frames containing unknown Protocol

Already Decided! 

Frame counters in the MacInterface Performance->Statistics

Already Decided! 

Deleting unsupported performance attributes

Already Decided! 

rxCollisions attributes to be added to WireInterfaceStatus and WireInterfacePerformanceType

Already Decided! - label to be changed to "UML_to_be_changed"

RMON - MacInterface #24

Performance Counters to be complemented 

Decision: proposal is approved.

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

Correction made on approved decision as there was bug in the approved list.

Please see comment in

https://github.com/openBackhaul/macInterface/issues/33

Here a copy of this comment_

Correction of the approved list above:
MacInterfaceStatus::framesOf64Byte was missing
We consider it as a bug of the approval and continue with the following list:

The following statistic values shall be created in the MacInterface model:
MacInterfaceStatus::framesOf64Byte
MacInterfaceStatus::framesOf65To127Byte : INT64 = -1
MacInterfaceStatus::framesOf128To255Byte : INT64 = -1
MacInterfaceStatus::framesOf256To511Byte : INT64 = -1
MacInterfaceStatus::framesOf512To1023Byte : INT64 = -1
MacInterfaceStatus::framesOf1024To1518Byte : INT64 = -1

queue-depth on device/switch level

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 

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 

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

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

Deleting MacInterfaceConfiguration::InterfaceIsOn

Proposal made - on the agenda for July 7th

Deleting MacInterfaceConfiguration::performanceMonitoringIsOn

Proposal made - on the agenda for July 7th

@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

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.