Versions Compared

Key

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

 | 2am PST | 5am EST | 09: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

2022-09-28: Martin Skorupski (Thorsten ooo)

2022-10-05: Martin Skorupski (Daniela, Michael ooo)

2022-10-12: Martin Skorupski (Daniela, Michael ooo) 

2022-10-17: Martin Skorupski

2022-10-24: Martin Skorupski 


Approval session

00:05

Sync #42 

@all

ptpSourceDataset isSf parameter

approved as proposed

00:08Core #10@all

LogicalTerminationPoint::_(!)physicalPortReference String -> leafref

approved as proposed

00:12

Core #12

@all

manufacture-date is not date and time

A new proposal is made for Oct12.

00:15

Core #24

@all

Centralize storing of the timestamp of the latest attributeValueChangedNotification
approved as proposed plus a reference will be added in the EquipmentAugment

00:18

Core #25

@all

New core module name?

closed as proposed

00:21

Core #29

@all

Delete attributes related to configuration-and-switch-control
approved as proposed

00:25

Core #21

@all

Changes to other attributes datatype after including C&SC grouping






END OF THE MEETING


Working session

00:30Frequency Synchronization Modelling @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:45Equipment #11@allExpansion towards a general Equipment specification
00:50Equipment #10@allEmpty occupying-fru - WireEquipment

Equipment #9@allUUID

Equipment #8@allRoot instantiation

Equipment #7@allVlanInterface and Profiles

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
01:05Feedback from Event last weekThorsten Heinze 

Focus on Implementation

  • Thursday call to be cancelled 

END OF THE MEETING

Equipment #12

Name of the Vendor | | Create a proposal and go for it - see also comment

Equipment #11

Expansion towards a general Equipment specification | Create a proposal and go for it.

Equipment #10

Empty occupying-fru - WireEquipment | bug -> Prathiba should have a look, if the situation can be solved by UML2YANG.

Equipment #9 

UUID | see comments

Equipment #8

Root instantiation | go with the proposal

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