Skip to end of metadata
Go to start of metadata

 | 3am PDT | 6am EDT | 9:00 UTC | 10:00 BST | 11:00 CEST | 12:00 EEST | 14:30 IST | 17:00 CST | 18:00 JST |

Web Conference:

Conference Call Link by Telefonica 


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

Discussion items

00:00Chair topic 
no update 



2023-04-05: Martin Skorupski

2023-04-12: Martin Skorupski

2023-04-19: Martin Skorupski

2023-04-26: Martin Skorupski


@Eduardo Yusta 
Roberto Servadio 

  • 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:
  • Intro by Eduardo
  • latest publication:
  • 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)


  • 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)


  • 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;




       "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;




       "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


  • Nader contacted IEEE chairs/representative - waiting for response


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

00:00EthernetContainerFD #2@all

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"

00:00EthernetContainerFD #4@all

Adding references to Policing and QoS Profile?

  • please provide comments (smile)

END of the meeting

00:00Modelling Roadmap

all, Nader Zein 

latest version in wiki:
Q: timeline?

Modelling Roadmap

update sequence to pre-MW-2.0-yangs

all currently implemented pre-TR532 2.0 -> PACs (existing today, including RMON, PM)

Sync and the updates of the CoreModel 1.4 yang (target to be available as YANG in 2022-10)

Centralized Alarm List (available now)

Mediator Instance Manager (available now) (REST for Mediators not for devices) (reusable component to be prepared)

based on the ApplicationPattern

proposed official ONF TR532 2.0

Sync and the updates of the CoreModel 1.4 yang

Centralized Alarm List - needs to be in 2.0 because it has impact on all PACs

Equipment Augment Module

all currently implemented pre-TR532 2.0 -> PACs

Mediator Instance Manager (REST)

proposed official ONF TR532 2.1

Backup and Restore

LLDP -> related automatic link discovery


proposed official ONF TR532 3.0

CoreModel 1.6

NMDA alternative

Target: start ONF review mid of November 2022 for TR532 2.0

zip file with folder structure

top-level document 




00:00Backup and Restore@Senthilvel 

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


Note: Mediator Instance Manager backup-and-restore functions are covered by app and cloud functions




Action items