| 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 feel free to correct, update your names Thank you very much!!!)
Time | Item | Who | Notes |
---|---|---|---|
00:00 | chair topic | no update | |
00:00 | Admin | Next meetings 2020-05-06: Martin Skorupski 2020-05-13: Martin Skorupski 2020-05-20: Martin Skorupski 2020-05-27: Martin Skorupski | |
00:10 | Proposal to replace maxQueueDepth by availableQueueDepthList (follow link to see the email) For information only: Please see related issue. There is an action item to vendors to validate the proposed solution within the referenced email. | ||
00:1500 | Pawel Krecick | Proposal to align modeling of AirEquipment with WireEquipment (follow link to see the email) For information only: There is an ongoing action item to Martin and Pawel to develop the necessary explaining document for next week. Please feel free to review and contribute: https://github.com/openBackhaul/core/wiki/equipment-model-alingment Felix F. should be involved and will review. On the agenda for next Tuesday. | |
00:2500 | dropping-behavior-kind on device/switch level - link to issue AI: Danilo Pala, Michael Binder Daniela Spreafico: Please provide options how to solve the issue and a recommendation for discussion next week. We think there are more attributes. On the agenda for tomorrow. | ||
00:4500 | Thorsten Heinze | Default value for header-compression-name - link to issue Discussed and decided - please see link | |
00:00 | Roberto Servadio | radio-signal-id: proposal of simplification - link to issue Answer: ??? to be discussed | |
00:00 | Alex Stancu | pyang warning for must statement - link to issue Discussion: Decision: | |
01:11 | Validation | Thorsten Heinze | Info:
|
0min | UUID | Status: discussion on-hold core-model allows definition of both Logical Termination Points (interfaces), but also connections
core-model is also suitable for representing entire Networks, not only a Device this means that Universally Unique IDs are required Devices cannot get the UUIDs from outside, they need to be generated by the device, and cannot be overwritten from outside Devices are unaware by their surroundings (the network), so it cannot know if a UUID is already used by some other interface in other devices IETF defines how to create UUIDs, and the core-model references this RFC
Possible solutions:
Suggestions:
Out of time, we need to follow up: proposal, next week Tuesday 09:00 CET -- Notes from Discussion about UUID and Links/Asszosations/References between object classes ODL MountPoint is and association to a NetConf server - some NetConf servers representing some times the microwave model. |