1. Pages
2. …
3. Open Transport Configuration and Control Home
4. 5G-xHaul
5. 5G-xHaul Call-in Details & Notes

2023-03-15 5G-xHaul Meeting notes

00:01

Supporting EthernetContainerFc Creation with proper UUID

• for create no specific EthernetContainerFC attributes are needed.
• constrains about LTPs (# and layer-protocol) are in the comment/description. 

Before creating a proposal - a discussion is required.

Switched based configuration of queue depth, dropping behavior, wred profile and scheduler kind

• EthernetContainerFD Configuration 
  • profiles should be used instead of individual
  • currently only schedulerProfile
  • new issue created for wredProfile and policingProfile  (https://github.com/openBackhaul/ethernetContainerFd/issues/4)
    Please give feedback to Thorsten.

label was changed from "Decision made" to "Uml_to_be_changed" being consistent with the mechanise of "open issues" for 2.0.

EthernetContainerFD

General Discussion about the need and objectives of an EthernetContainerFD

• Does "no EthernetContainerFD" AND "no VLAN FCs" mean no forwarding at all?
  • device specific behaviour (BridgeMode?)
  • in some cases only VLANs are forwarded (all untagged traffic is tagged)
  • in other cases it is not possible to delete the "minimum default vlan"
  • in other cases the devices act as "shared Ethernet Bridge"
• What is the ETH-Topology if no VLANs are configured at the device (VLAN-IFs, VLAN-FCs)?
  • device specific 

MAC learning

• should happen by "default" on an initial EthernetContainerFC which includes all EthernetContainers if the device.
• in same cases MAC learning does not happen on WirelessTransport devices without a VLAN.

Functionality/operations?

• add/remove VLAN-IF from VLAN-FD
• add/remove EthernetContainer-IF from EthernetContainerFD
• VLAN-FD and also EthernetContainerFD exist based on hardware to express the capabilities of the device.

2023-01-31:

• How to show the ETH potential of a topology?

  • ETH forwarding is a valid concept within TEF. -> need to model an EthernetContainerFD
  • modelling for ETH frame transport independent form VLANs - e.g. for switches and routers
  • representing a transport topology based on ETH

• EthernetContainerFD

  • core-model:FD with LTP(LP=EthernetContainer)
  • augmentation for EthernetContainerFD should contain
    • capability -> L1-transport support
      • L1-transport-support = true allows remote operation for ETH-FC (create, delete, modify)
      • frame-forwarding-without-vlan
    • configuration
      • RPCs for operations of ETH-FC
        • create-l1-connection
          • input
            • references to 2 LTP(EthernetContainer)
          • output
            • success
              • FC:uuid
            • error
              • error-message
        • modify-l1-connection - not needed -> not modelled
        • delete-l1-connection
          • input
            • FC:uuid

• EthernetContainerFC

  • core-model:FC -> with number of FC-Ports equals to 2.
  • Is there a need for augmentation? no!

• Check also existing models for L1/L2

  • OpenConfig
  • MEF?
  • IETF?

2023-02-15:

Feedback from Andrea (TAPI)

3.2.2 TAPI representations of the ONF Core IM Forwarding Domain

The Forwarding-Domain described in the ONF Core IM [ONF TR-512], represents the opportunity to enable forwarding between its FdPorts. The Forwarding-Domain can hold zero or more instances of Forwarding Constructs (or Connections) and provides the context for requesting and instructing the formation, adjustment, and removal of Connections.

QoS Profile #10 | Wrong index in ingress-ip-dscp-to-per-hop-behavior-mapping-list

QoS Profile #13 | QOS profile configuration: ingress list key parameter

Policing Profile #5 | Request update from int16 to int32 for committed/excess/peak burst size

Supporting EthernetContainerFc Creation with proper UUID

Switched based configuration of queue depth, dropping behavior, wred profile and scheduler kind

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