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

2023-03-29 5G-xHaul Meeting notes

00:01

• focus of a subset LLDP for topo discovery
• base is IEEE 802.1
  • in control-construct as lldp-container? (vs. function split across several objects
  • pointers to LTP (EthernetContainer) or (physical) port
• pre-work already done (openConfig vs ieee - proposal: go with ieee)
• repo: https://github.com/openBackhaul/lldp
• Intro by Eduardo
  • Please see "material" folder: https://github.com/openBackhaul/lldp/tree/tsi/materials
  • main use case: topology recovery
• latest publication: https://ieeexplore.ieee.org/document/9756407
• implementation/adoption option
  • parameter per parameter - where to augment TR532
  • single container on CC - with basically a copy of IEEE.
  • ieee lldp yang as is with augmented references to LTP(ETHContainer)

Discussion

• one container for the entire function vs. port details in LTPs
  • Working assumption: go with one container for the entire LLDP Functions with referenced to LTPs
• min implementation vs complete function
  • Working assumption: Let's go with the entire LLDP management function as described by IEEE 802.1ABcu Dec 2021 (yang)

Comments

• control-construct // how to inject the lldp-container into the control-construct
  • profile-collection
    • ...
  • forwarding-domains 
    • ...
  • logical-termination-points
    • ...
  • protocols (or use of an existing onf object 
    • lldp
      • ...
    • <further-processes />
• How to structure the lldp?
  • using onf naming-conventions with verbal referencing - using yang-'reference' statements
  • seams to be possible from UML and UML2YANG 

Option1 for the yang output

augment "...."

 if-feature "lldp-support"; 

 container link-layer-discovery-protocol

   use link-layer-discovery-protocol-g;

   description

     "bla";

   reference

       "ieee 802.1ABcu Dec 2021: lldp";

Option2 for the yang output (reuse IEEE parameter names)

augment "...."

 if-feature "lldp-support"; 

 container lldp

   use link-layer-discovery-protocol-g;

   description

     "bla";

   reference

       "ieee 802.1ABcu Dec 2021: lldp";

Preference is on option2 - reuse the IEEE parameter names.

Next Steps:

• Create UML and then use UML2YANG tool to generate an augmentation yang to core-model-1-4:control-construct.
  • takes time ....
  • sources for the document are existing

Copyright/License

• Nader contacted IEEE chairs/representative - waiting for response

UML2YANG tool

• Function to be checked for the reference statement and its translation

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.

introduction of the "potential proposal"

Adding references to Policing and QoS Profile?

• please provide comments

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