| 6am PST | 6am EST | 10:00 UTC | 11:00 CET | 12:00 EET | 15:30 IST | 18:00 CST | 19:00 JST |
https://thorsten-heinze-telefonica-de.webex.com/join/andreas.lattoch.external
(please feel free to correct and update your names Thank you very much!!!)
Time | Item | Who | Notes |
---|---|---|---|
00:00 | chair topic | no update | |
00:00 | Admin | Next meetings 2020-11-18: Martin Skorupski 2020-11-25: Martin Skorupski 2020-12-02: ??? 2020-12-19: Martin Skorupski | |
00:05 | Issues in General | INFO: https://github.com/openBackhaul/core/wiki/summary-of-issues | |
0:15 | Firmware | @Eduardo Yusta | Use case discussion challenging the model proposal: Please see updated slides (thanks Eduardo). Feedback from vendors:
Firmware inventory
Firmware operations
|
00:45 | Reboot | As a result of the discussion about Firmware, their might be a need for a "restart" trigger. The "software activation trigger" usually also leads to a "restart" but with new software, which a "restart" reboots using the currently running software. Other terms for the same? or similar? function:
Questions:
General reboot
| |
@Eduardo Yusta | License Management | Questions:
First proposal:
2020-11-18
| |
End of the meeting Backlog | |||
PureEthernetStructure, HybridMwStructure | Daniela Spreafico | Please see email_ Please see related issues:
Please confirm by email to Martin Skorupski by end of this week (Nov6) that keeping FM and PM for xyzStructure is ok? Status: positive feedback to keep it as it is: Decision: we keep xyzStructure as they are and close the issues above. | |
Roberto Servadio | RMON counter
Update: Support is welcome to consolidate with respect to RMON | ||
@Eduardo Yusta | License Management | Questions:
First proposal:
| |
00:00 | Layering discussion (FCs, FDs etc.) | Thorsten Heinze |
Agenda: 2020-09-30 Discussion and agreement about the following proposal: Discussion The following aspects are proposed to be decided by the 5G-xhaul subproject. - The ForwardingDomain shall be interpreted as a Potential for Forwarding (e.g. SDH Matrix). [sko] Potential: something which allows the creation of “forwarding” based in the FD:LTP - The ForwardingConstruct shall be interpreted as an Actual Forwarding (e.g. Connection between two VC-12 endpoints at the SDH Matrix). [sko] Actual: configured Forwarding – check operational states and traffic flow - There might be 0 .. * ForwardingConstructs inside a ForwardingDomain. [sko] ok Discussion on dependencies between LTPs, FD, FC and between the layers will continue... Agenda: 2020-10-07
|