Due to a ransomware attack, the wiki was reverted to a July 2022 version. . We apologize for the lack of a more recent valid backup.
Open Transport Configuration & Control

Space shortcuts

Expand all   Collapse all
Child pages
  • 2022-05-17 TAPI Meeting Notes

Date

Attendees

Goals

  • Admin
  • Brief review of pull request #519
  • Continue Optical Impairments review
  • DSR UNI Model and asymmetric Connectivity Service

Agreed Items & Priority

Discussion items

20 minsAdministrative

All



TAPI RIA 2.0:

  • Scheduled two additional, dedicated TAPI calls:
    • Mon 14-16 and Wed 13-15 CEsT

Asked to ONF to extend the additional, official, dedicated TAPI calls till end of year.

This week the next call is on Wed 18, 12-15 CEsT

Next week: Thu 26, 10-12 and Fri 27, 11-13 CEsT

  • Andrea Mazzini will send the invitation to anyone who wants to participate.


TAPI weeky call

Preliminary agenda:

  • DSR UNI Model and asymmetric Connectivity Service
5 mins

Brief review of pull request #519

Karthik Sethuraman 

Karthik Sethuraman will take some time to review.

5 minsTAPI 2.4 and RIA 2.0 plan

Ramon Casellas Nigel Davis Andrea Mazzini

Agreed that we need another full month for the delivery.

  • UML side, all modules are mature but TapiPhotonicMedia, where are likely necessary some adjustments to:
    • OTSi / OTSiMC / MC structures - to reflect the recent agreements regarding layering and connectivity provisioning.
    • Optical Impairments structures - where some further review is necessary to double check the alignment to IETF.
  • RIA side, we made progresses in many subjects, several technical issues are now solved. Next main steps:
    • Complete the review of Connectivity UCs
    • Complete the inventory UCs with the Optical Impairments specific structures
    • Introduce the OAM UCs
    • Check the Path Computation UCs
90 mins

Optical Impairments review

All

Andrea Mazzini shows the updated diagrams regarding ROADM Path impairments.

  • Below the simplest scenario, where the Node Rule Group indicates full mesh connectivity between all add/drop and degree ports, and the related impairment profiles as applicable to all possible connectivities:

  • Below the diagram built during the discussion, where add/drop NEPs and degree NEPs are grouped by distinct Node Rule Groups and the impairments profiles are referred by the Inter Rule Group object:


  • The figure above is an example of the agreed the solution where:
    1. one or more Node Rule Group instances aggregate only the add/drop MC NEPs,
    2. one or more Node Rule Group instances aggregate only the degree MC NEPs, and refer to the express-path profiles,
    3. one or more Inter Rule Group instances associates the above 1. and 2. Node Rule Group instances, to identify one or more add/drop to degree path impairments.

Below the UML model of Node Rule Group and Inter Rule Group:


  • After some discussion agreed to make bidirectional the association between NEP and Node Rule Group classes.
    • This shall allow both:
      • GET on Node Rule Group instance including all the references to the NEP instances associated by the Node Rule Group Rule(s),
      • GET on NEP instance including all the references to the Node Rule Group instances involving the NEP.
  • We briefly review the other Optical Impairments data structures and agreed the current state of the definitions.
  • Ramon Casellas regarding the RIA, we may introduce the Optical Impairments as "sub use cases" of the inventory ones. In other words, starting from the inventory of technology agnostic topology and connectivity objects, add the description of technology specific augments.