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

2021-05-05 5G-xHaul Meeting notes

00:05

Feedback 

• implementation from PoC#4 seams to be outdated
• ietf-ptp (https://datatracker.ietf.org/doc/rfc8575/ - IEEE1588) or itu-t (https://www.itu.int/rec/T-REC-G.8275.1/en) is now the table
• AI: Thorsten: Experts should check the options.
• GenDoc from 7721 under analysis
• proponed for tomorrow 

AirInterface feedback from vendors

• feedback from 5 vendors received - thanks!!! 
• first result - many attributes are supported by some vendor 
  • 3 attributes are not supported by any of the vendors platform
    • alic-is-on: was known that it is supported only by one vendor, when the attribute was introduced
      • should be kept, due to the benefit of the feature
    • alic-is up:
      • same as above
    • auto-freq-select.is-up
      • should be kept due to the benefit of the underlaying feature
  • attributes to be discussed
    • receiver-is-on
      • needed for diversity → in case of 1 transmitter and 2 receiver
    • clearing-threshold-cross-alarm-is-on
      • needs to be kept for vendor not supporting auto clearing
      • could be an rpc - but no benefit in changing it now → so attribute is kept. 
    • signal-noise-...-average 

Summary

• yes in specific implementations a lot of attributes are not supported
• but overall there are good reasons of not removing 

Further "findings"

• introduction of more capabilities attributes: receiverIsOn, alicIsOn
• Thorsten is adding an issue for the "receiverIsOn" case.

overlap of status attributes

LTP:operationalStatus :== AirInterface:status

Conclusion: should be discussed in conjunction with "NMDA alternatve"

air-interface-2-0:air-interface-capability::transmission-mode-list::transmission-mode-label

• comment by Daniela

Link: https://github.com/openBackhaul/ethernetContainer/issues

Allowed queue depth values to be declared as capability

dropping-behavior-kind on device/switch level

Bundling attributes for Ethernet ports

• on radio side all good
• LAG is different? - yes and is independent of the "bundling" attributes.
• When combing with NMDA alternative and when EthernetContainer is associated to WireInterface
  • capabilities: bundling-is-avail==false
  • bundling-is-on = false in status
  • no representation in configuration object
• LAG example
  • idea: LAG → combination of EthernetContainers ?!?!? - maybe grouped by MacInterface
  • What are the necessary parameters for LAG? 
• Is there a "need of change"?
  • if no → to be closed
  • if yes → to be discussed.

Multiplicity of _supportedHeaderCompressionKindList = 1, but headerCompressionName undefined

Issue #29 is the final solution for this issue.

However, the comment made in UML according the initial proposal should be reverted. 

To be decided on 2021-05-12

(Not-)Support of queue utilization performance values to be clearly indicated

• next step: start review period now and decide on 2021-05-12 if issue can be closed.