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 

Invited:

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

Discussion items

TimeItemWhoNotes
00:00Chair topic 
no update 

00:01

Admin

2023-05-17: Martin Skorupski

2023-05-24: Martin Skorupski

2023-05-31: Martin Skorupski

2023-06-07: Martin Skorupski

00:05Equipment #27@all

IpInterface Instantiation

  • approved as proposed
00:10LLDP 

@Eduardo Yusta 
Roberto Servadio 

Copyright/License

  • Nader contacted IEEE chairs/representative - waiting for response

Open issue: management-address-tx-port

YANG-tree

module: ieee802-dot1ab-lldp
  +--rw lldp
     +--rw message-fast-tx?              uint32
     +--rw message-tx-hold-multiplier?   uint32
     +--rw message-tx-interval?          uint32
     +--rw reinit-delay?                 uint32
     +--rw tx-credit-max?                uint32
     +--rw tx-fast-init?                 uint32
     +--rw notification-interval?        uint32
     +--ro remote-statistics
     |  +--ro last-change-time?   yang:timestamp
     |  +--ro remote-inserts?     yang:zero-based-counter32
     |  +--ro remote-deletes?     yang:zero-based-counter32
     |  +--ro remote-drops?       yang:zero-based-counter32
     |  +--ro remote-ageouts?     yang:zero-based-counter32
     +--ro local-system-data
     |  +--ro chassis-id-subtype?              ieee:chassis-id-subtype-type
     |  +--ro chassis-id?                      ieee:chassis-id-type
     |  +--ro system-name?                     string
     |  +--ro system-description?              string
     |  +--ro system-capabilities-supported?   lldp-types:system-capabilities-map
     |  +--ro system-capabilities-enabled?     lldp-types:system-capabilities-map
     +--rw port* [name dest-mac-address]
        +--rw name                          if:interface-ref
        +--rw dest-mac-address              ieee:mac-address
        +--rw admin-status?                 enumeration
        +--rw notification-enable?          boolean
        +--rw tlvs-tx-enable?               bits
        +--rw message-fast-tx?              uint32
        +--rw message-tx-hold-multiplier?   uint32
        +--rw message-tx-interval?          uint32
        +--rw reinit-delay?                 uint32
        +--rw tx-credit-max?                uint32
        +--rw tx-fast-init?                 uint32
        +--rw notification-interval?        uint32
        +--rw management-address-tx-port* [address-subtype man-address]
        |  +--rw address-subtype    identityref
        |  +--rw man-address        lldp-types:man-addr-type
        |  +--rw tx-enable?         boolean
        |  +--ro addr-len?          uint32
        |  +--ro if-subtype?        lldp-types:man-addr-if-subtype
        |  +--ro if-id?             uint32
        +--ro port-id-subtype?              ieee:port-id-subtype-type
        +--ro port-id?                      ieee:port-id-type
        +--ro port-desc?                    string
        +--ro tx-statistics
        |  +--ro total-frames?          yang:counter32
        |  +--ro total-length-errors?   yang:counter32
        +--ro rx-statistics
        |  +--ro total-ageouts?             yang:zero-based-counter32
        |  +--ro total-discarded-frames?    yang:counter32
        |  +--ro error-frames?              yang:counter32
        |  +--ro total-frames?              yang:counter32
        |  +--ro total-discarded-tlvs?      yang:counter32
        |  +--ro total-unrecognized-tlvs?   yang:counter32
        +--ro remote-systems-data* [time-mark remote-index]
           +--ro time-mark                        yang:timeticks
           +--ro remote-index                     uint32
           +--ro remote-too-many-neighbors?       boolean
           +--ro remote-changes?                  boolean
           +--ro chassis-id-subtype?              ieee:chassis-id-subtype-type
           +--ro chassis-id?                      ieee:chassis-id-type
           +--ro port-id-subtype?                 ieee:port-id-subtype-type
           +--ro port-id?                         ieee:port-id-type
           +--ro port-desc?                       string
           +--ro system-name?                     string
           +--ro system-description?              string
           +--ro system-capabilities-supported?   lldp-types:system-capabilities-map
           +--ro system-capabilities-enabled?     lldp-types:system-capabilities-map
           +--ro management-address* [address-subtype address]
           |  +--ro address-subtype    identityref
           |  +--ro address            lldp-types:man-addr-type
           |  +--ro if-subtype?        lldp-types:man-addr-if-subtype
           |  +--ro if-id?             uint32
           +--ro remote-unknown-tlv* [tlv-type]
           |  +--ro tlv-type    uint32
           |  +--ro tlv-info?   binary
           +--ro remote-org-defined-info* [info-identifier info-subtype info-index]
              +--ro info-identifier    uint32
              +--ro info-subtype       uint32
              +--ro info-index         uint32
              +--ro remote-info?       binary

  notifications:
    +---n remote-table-change
       +--ro remote-insert?    -> /lldp/remote-statistics/remote-inserts
       +--ro remote-delete?    -> /lldp/remote-statistics/remote-deletes
       +--ro remote-drops?     -> /lldp/remote-statistics/remote-drops
       +--ro remote-ageouts?   -> /lldp/remote-statistics/remote-ageouts

Info from Eduardo - thanks!

  • conclusion: We go with the current UML description

Next step

  • using UML naming convention
  • UML delivery Date may 26
00:25UML2YANG@Prathiba

 require-instance

  • Sync #16  | Method for managing require-instance statements to found
  • VLAN-IF #28 | require-instance==false at object-creation- and attribute-value-changed-notification manually corrected
  • VLAN-FD #19 | require-instance==false at object-creation- and attribute-value-changed-notification manually corrected
  • VLAN-FC #6 | require-instance==false at object-creation- and attribute-value-changed-notification manually corrected

The mechanism is required for AttributeValueChange Notification and ObjectCreate Notification but not for ObjectDeletion Notification

@Prathiba is going to check for other cases

Thorsten Heinze : Is an issues required for all UMLs?

00:55Mediator Instance Manager@Senthilvel

next to existing operation status and/or notification might be useful

  • on the agenda for Tuesday

END of the meeting

00:00Issues@allhttps://github.com/openBackhaul/core/wiki/priority-of-issues
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

SVLAN

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 

gendoc

uml

yang


00:00Backup and Restore@Senthilvel 

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

Action items