Skip to end of metadata
Go to start of metadata

 | 2am PST | 5am EST | 09:00 UTC | 10:00 BST | 11:00 CEST | 12:00 EEST | 14:30 IST | 17:00 CST | 18:00 JST |

Web Conference: 


(please feel free to correct and update your names (wink) Thank you very much!!!) 

Discussion items

00:00Chair topic 
no update 



2022-05-04: Martin Skorupski

2022-05-11: Martin Skorupski

2022-05-18: Martin Skorupski

2022-05-25: Martin Skorupski

00:05EthernetContainer #50Roberto Servadio 

supported-affected-protocol-list capability is missing

  • approved as proposed

Adding new layer-protocol discussion

Current Assumption - not agreed - just for discussion purposes:

  1. a split between SyncE LTPs and PTP LTPs is useful
  2. a split between SyncE Clocks and PTP Clocks is useful
  3. There is a difference between Boundary Clocks and Transparent clocks and MasterClocks and Client Clocks?
  4. There is no need to address grand-master clocks in the 5G-xHaul model, because the addresses devices are not (and never will be Grand-Master Clocks)
  5. An FC for PTP is needed to express the status of the selected source
  6. An FC for SyncE is needed to express the status of the selected source and the configuration of possible sources


00:44EquipmentThorsten Heinze 

Idea: use augment for name/extension attributes - instead of documentation out side of UML and YANG

Addresses the limitations (rw/ro, units, ...)

00:00Backup and Restore@Sentival 

Requirements from TEF:

Comments could be addressed by adding issues in GitHub.

  • Backup and Restore Operations

    • backup configuration to FTP server
    • restore configuration from FTP server AND activate
    • abord operation individual for backup and restore
    • rollback to previous configuration stored in the device
    • applyRestoreOperation
  • Note: Mediator Instance Manager backup-and-restore functions are covered by app and cloud functions

  • status

    • backupOperationStatus
    • restoreOperationStatus

Action items