Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

 | 3am PST | 6am EST | 10:00 UTC | 10:00 GMT | 11:00 CET | 12:00 EET | 15:30 IST | 18:00 CST | 19: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

2022-11-23: Martin Skorupski

2022-11-30: Martin Skorupski 

2022-12-07: Martin Skorupski 

2022-12-14: Martin Skorupski 

00:02

VlanFd #21

@all

macAddress and macAddressCur attributes at both MacFD and VlanFD

approved as proposed

00:05VlanFd #22@all

Aspired coverage of the modelling

approved as proposed plus link to [VLAN interface #30](https://github.com/openBackhaul/vlanInterface/issues/30)

00:10SchedulerProfile@Senthilvel

Configuration expected on global level too

  • attribute: queueBehaviourList/weighting
    • could be also part of the EthernetContainer
  • all interfaces can have the same set of 'weighting' by pointing to a single profile
  • issue: profiles cannot be modified as explained by Thorsten - only delete and recreate with new  values


  • to Senthilvel: please change on the SchedulerProfile
00:40VLAN #30

Open questions

  • Description 'none': S-Vlan-Priority is set by the device (-> auto?)

    • one implementation of 'none' → maps to priority = 0 (same as 'fixed' and priority value = 0)
    • for now we continue with the current modelling approach
  • Handling of untagged frames on ingress?
  • How to describe the behaviour to VLAN headers on the egress?

END OF MEETING

00:05Frequency Synchronization Modelling (skipped)@all?

Mapping of T-REC-G.8264 Figure A.1 to FC and LTPs?

- https://www.itu.int/rec/T-REC-G.8264-201708-I (Figure A.2)

- https://www.etsi.org/deliver/etsi_i_ets/300400_300499/3004170601/01_60/ets_3004170601e01p.pdf (Figure 6) - same as G.781 

Discussion slides: https://wiki.opennetworking.org/download/attachments/265093121/itut-goes-onf.pptx?api=v2

AI Martin to upload new slide version - to be on the agenda fro next week with input from experts and App view.



Equipment #6 @allMacInterface and IpInterface Instantiation

Equipment #5@all

EthernetContainer


Equipment #4@allPureEthernetStructure

Equipment #3 @allAirEquipment

Equipment #2@allpartTypeIdentifier of non-pluggable connectors needs a rule to be filled

Equipment #1@allOUI needs a rule to translate it from hex to string
00:55Issues@alllooking to the next 10 issues for next week
https://github.com/openBackhaul/core/wiki/priority-of-issues
00:00Frequency Synchronization Modelling (skipped)@all?

Mapping of T-REC-G.8264 Figure A.1 to FC and LTPs?

- https://www.itu.int/rec/T-REC-G.8264-201708-I (Figure A.2)

- https://www.etsi.org/deliver/etsi_i_ets/300400_300499/3004170601/01_60/ets_3004170601e01p.pdf (Figure 6) - same as G.781 

00:05Modelling 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@Sentival 

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