| 2am PDT | 5am EDT | 9:00 UTC | 11:00 CEST | 12:00 EEST | 14:30 IST | 17:00 CST | 18:00 JST |
https://onf.zoom.us/j/853336915 -Zoom is blocked by more and more ITs. Please use the following link: https://thorsten-heinze-telefonica-de.webex.com/join/andreas.lattoch.external
ONLY TODAY: https://thorsten-heinze-telefonica-de.webex.com/thorsten-heinze-telefonica-de/j.php?MTID=mb1d17556e17e436261d7c34bbdfe685d
(please feel free to correct and update your names Thank you very much!!!)
|00:00||chair topic||no update|
2020-08-26: Martin Skorupski
2020-09-02: Martin Skorupski
2020-09-09: Martin Skorupski
2020-09-16: Martin Skorupski
|00:05||VLAN IF and Connection|
UML Model based on ONF CoreModel 1.4
Questions/Suggestions by Danilo Pala
VLAN UML2YANG is progressing
report by Thorsten
Result: 4 connection related PACs
yangs will be available in openbackhaul - an email will indicate availability
table and presentation - will be send around by email - please provide feedback about 2 weeks after the email was received (proposal)
VLAN Model with reduced scope.
review period for documents from August 2019 will end 2020-06-09
for 2nd September 2020 - list issues to be decided
Related Contribution in Email from 2020-04-30
Latest discussions revealed the following documented issues:
→ all for issues on the agenda for decision next week 2020-07-29 - Please send comments to be addressed until 2020-07-27 - Thanks!
rxCollisions attributes to be added to WireInterfaceStatus and WireInterfacePerformanceType
Proposal of removal of "unused"/"unsupported" counters.
Please check the proposals:
Latest testing showed that none of the devices under test is supporting alarms in the PureEthernetStructure and the HybridMwStructure.
Vendors not participating in the tests also confirmed that their devices don't implement alarms on these interfaces.
It should be considered to remove all attributes, data types and classes related to alarming from the PureEthernetStructure and the HybridMwStructure modelings.
Thorsten Heinze created the following two issues on the openBackhaul Github for being discussed and decided before the next update of the respective modelings:
|00:??||Identification of Object instances||@all|
How to align between Controller/Apps/Mediator/Devices?
Please see related email: https://groups.google.com/a/opennetworking.org/forum/#!topic/wireless-transport/daCPBnPKJzo
Feedback from vendors available => Vendors confirmed to be able to store an external equipment label and an external interface label on the device.
The following text has been added to the TransmitterEquipment document:
ControlConstruct and LogicalTerminationPoint
dropping-behavior-kind on device/switch level - link to issue
AI: Danilo Pala, Michael BinderDaniela Spreafico: Please provide options how to solve the issue and a recommendation for discussion next week.
AI: Martin SkorupskiWork out a proposal to be discussed next week.
based on the proposal made in the issue:
further details should be agreed.
Conclusion during the discussion:
Switching the port by management interface → CoreModel solution is ForwardingConstruct with FC-Switch.
AI: Martin SkorupskiShow how this works with CoreModel 1.4