Skip to end of metadata
Go to start of metadata

Date

Attendees

Goals

  • Admin
    • Plan for dedicated RIA 1.2 / 2.0 review calls (ONF TAPI RIA)
  • Continue the development of Optical Impairment UML model
  • Updates on OAM model

Agreed Items & Priority

Discussion items

5 minsAdministrative

All



TAPI RIA 1.2/2.0:

  • Scheduled two additional, official, dedicated TAPI calls:
  • Added a third non-official call on Thu 10:00-12:00 CET
    • Andrea Mazzini will send the invitation to anyone who wants to participate.

For the two weeks where US and EU are not aligned on daylight saving time, Andrea Mazzini sends separate invitations to maintain the european time slots:

  • For Wed. 16, 23 and Fri. 18, 25.
  • Do not connect to official ONF TAPI calls in these days!


TAPI weeky call

Preliminary agenda:

  • Continue the development of Optical Impairment UML model
15 mins

Plan for dedicated RIA 1.2 / 2.0 review calls (ONF TAPI RIA)

Ramon Casellas indicates the key features which are expected for TAPI 2.4 / RIA 2.0:

  • OAM Use Cases for Digital OTN
    • we are in solid track, should complete in two week or less
  • Physical Route Inventory
    • model is already defined, it should not take much time
  • Optical Impairments Inventory
    • model is under consolidation

Ramon Casellas recalls that the RIA 2.0 delivery also includes the review of all Connectivity UCs in the light of new layering agreements.

  • In addition, in April there is the Easter break

All of the above is leading to a shift of the delivery at the end of April.

40 minsReview of OAM  modelAll

Andrea Mazzini shows the OamJob model:

  • Some comments for clarification have been added to the diagram.
  • Some considerations regarding the streaming of CurrentData, which state changes can be not meaningful in some cases.
    • E.g. is useless to stream the evolution of elapsedTime or of any PM Metric, as sampling is currently defined only when
      • the granularity period ends,
      • a GET operation is performed on CurrentData.
  • Ronald, very short granularity periods may be applicable for telemetry/spotlight applications where a frequent sampling of a specific metric is required (e.g. power , FEC).
    • In this case the creation of HistoryData instances may not useful/convenient, rather an immediate notification/streaming is preferable.
    • To be considered in the RIA Use Cases.
60 minsDraft of Optical Impairment UML modelAll

Andrea Mazzini shows the updated draft model.

Below the draft of Transceiver Profiles:


Below the draft of ROADM Path Profiles:


Below the draft of Amplification Profile, the Amplification state (associated to the OMS CEP) and the OMS/OTS impairments:


Discussion on the PowerParams, which CCAMP includes both in grouping amplifier-params and in grouping oms-general-optical-params.

  • To be clarified whether are parameters for configuration, state and maybe profile.
  • Huy Tran indicates that these parameters are configured on ROADM degree ports, but further analysis is necessary, e.g. whether they are correlated to any booster function or not.
    • GNPy does not define any impairment parameter on the OMS section (TAPI MC Link, the ROADM to ROADM Link).

Discussion on OAM for Photonic.

  • Ramon Casellas the transceiver CEP shall include power measurements both on signal (OTSi) and on spectrum (OTSiMC) base.
  • Andrea Mazzini we shall review all existing metrics and evaluate how to include any OAM Use Case in the RIA.

Discussion on the model of the OTS Impairments, which is composed by an ordered sequence of either a fiber span or a concentrated loss (see diagram above).

  • Andrea Mazzini ideally the UML constraint shall define the XOR between the two associations, but it is unclear if the UML to YANG tool supports the translation to the choice statement.
  • Ramon Casellas we shall introduce also the when statement, to better specify the constraints.
  • Karthik Sethuraman to fully leverage the YANG language we should have YANG as master, with UML only for documentation.
  • Andrea Mazzini Currently the YANG modules are already the main references:
    • To deliver a new version n, the n-1 YANG modules are matched against the YANG automatically generated from UML version n.
    • In other words, the automatically generated modules are used to manually update the existing YANG modules.
    • Hence we can introduce YANG statements even if not automatically derived from UML, as already done for augments.
      • Key aspect is the proper documentation in IISOMI Guidelines.