1. Pages
2. …
3. Open Transport Configuration and Control Home
4. 5G-xHaul
5. 5G-xHaul Call-in Details & Notes
6. 2022-11-09 5G-xHaul Meeting notes

Page History

00:01

2022-11-16: Thorsten Heinze / Alex Stancu (Martin ooo) 

2022-11-23: Martin Skorupski

2022-11-30: Martin Skorupski 

Issues to be approved: 

PolicyProfile #5

The existing formulation in paragraph LogicalTerminationPoint and LayerProtocol in Chapter 6 Instantiation of the Transmitter Equipment Specification is already covering the request for automatically creating the VlanInterfaces as soon as there is an entry into the expected equipment list. So, no change required.

Mapping of T-REC-G.8264 Figure A.1 to FC and LTPs?

- https://www.itu.int/rec/T-REC-G.8264-201708-I (Figure A.2)

- https://www.etsi.org/deliver/etsi_i_ets/300400_300499/3004170601/01_60/ets_3004170601e01p.pdf (Figure 6) - same as G.781 

• Discussion slides: https://wiki.opennetworking.org/download/attachments/265093121/itut-goes-onf.pptx?api=v2

AI Martin to upload new slide version - to be on the agenda fro next week with input from experts and App view.

VlanInterface and Profiles

Some findings:

1. From FD-Configuration point of view the “Provider Bridge” and “Provider Edge Bridge” cannot be distinguished – we would like to keep it this way.
2. The handling of VLAN-FD sub-layer-protocol-name is always clear.
1. SUB_LAYER_PROTOCOL_NAME_TYPE_C_VLAN_COMPONENT -> refers to “Customer Bridge” of page 2
2. SUB_LAYER_PROTOCOL_NAME_TYPE_S_VLAN_COMPONENT-> refers to “Provider Edge Bridge” of page 4 (and also to the “Provider Bridge” of page 3)
3. SUB_LAYER_PROTOCOL_NAME_TYPE_D_BRIDGE_COMPONENT -> our understanding is that in this case the VLAN function will be disabled the VLAN-FD – therefore all VLAN-Interfaces would be removed from the FD -> more discussion required e.g how would VLAN-IF added to another bridge? But this sounds also as a use case not related to Microwave.
4. SUB_LAYER_PROTOCOL_NAME_TYPE_EDGE_RELAY_COMPONENT -> not understood at all – maybe used for Routers?
3. The NETCONF edit-config RPC for creating an entry in forwardedCVlanListByDefaultSVlanId is basically the RPC needed to create VLAN objects of Option2 -> so we validate (again) that the functions of Option1 and Option2 are the same –Option1 simplifies the management.
4. Coming back to the original question of Equipment Issue #7 – It seams that VLAN interfaces are create always on the microwave devices by the devices and never by the controller.
5. Further discussions: what is the meaning of an empty forwardedCVlanListByDefaultSVlanId – there seam to be different implementations out.

Discussion slides: https://wiki.opennetworking.org/download/attachments/265093121/ProviderEdgeBridge%20Discussion.pptx?api=v2

EthernetContainer

Mapping of T-REC-G.8264 Figure A.1 to FC and LTPs?

- https://www.itu.int/rec/T-REC-G.8264-201708-I (Figure A.2)

- https://www.etsi.org/deliver/etsi_i_ets/300400_300499/3004170601/01_60/ets_3004170601e01p.pdf (Figure 6) - same as G.781 

Requirements from TEF:

https://github.com/openBackhaul/firmware/blob/tsp/BackUpAndRestore/BackUpAndRestoreRequirements.md

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