Simple Forwarding

[openBackhaul]

As a part of the harmonization of an Ethernet based connection between IDU and ODU, a simplified modelling of Forwarding shall be documented in the ONF TR-532 document (respectively its future version in the LinuxFoundation).

Decision at the LF ONMI x-haul call on 16th of October 2024:

• A new chapter 6.9 Simple Forwarding shall be added to the existing chapter 6 Special elements of the ONF TR-532 document.
• The following text shall be added to chapter 6.9 Simple Forwarding:
  "In general, it is expected that forwarding is expressed based on ForwardingDomains, ForwardingConstructs and ForwardingConstructPorts.
  In case of very simple kinds of forwarding, the LogicalTerminationPoint::connectedLtp attribute might be used instead.
  The following criteria are defining a very simple kind of forwarding:
  ~ The forwarding happens between exactly two LogicalTerminationPoints with identical values in their LayerProtocol::layerProtocolName attribute.
  ~ The forwarding is bidirectional (the LogicalTerminationPoint::connectedLtp attributes have to be filled at both involved LogicalTerminationPoints).
  ~ The forwarding is inherent to the device’s hardware structure; it is permanently active and cannot be switched off.
  ~ The forwarding cannot be changed in its path or any other characteristic; it does not provide any status, alarm or performance information.
  
  Figure 8: Simple Frame Forwarding
  As the Simple Forwarding is a matter of the device’s hardware structure, all involved LogicalTerminationPoints (including their bidirectional references in the connectedLtp attributes) shall be automatically instantiated while the underlying hardware gets either plugged or chosen for being expected."