Skip to end of metadata
Go to start of metadata




  • General update
  • Update on gNMI streaming and delta streaming
  • Continue the Path Computation UCs analysis
  • Continue the discussion of adding OMS CEP spec to version 2.1.3
    • Evaluate more in detail which part of 2.4.1 optical impairments model could be candidate for backporting in 2.1.4
  • Model of the internal connectivity matrix of a ROADM
  • AOB

Agreed Items & Priority

Discussion items

5 minsAdministrative


See TAPI Call-in Details and Notes for the RIA Review call coordinates.

Warning: in these weeks the RIA editors are changing or deleting some of these sessions.

TAPI weeky call

Preliminary agenda:

  • Progresses in gNMI streaming and delta streaming
  • Continue the Path Computation UCs analysis
  • Continue the discussion of adding OMS CEP spec to version 2.1.3
  • Model of the internal connectivity matrix of a ROADM
10 mins

Update on gNMI streaming and delta streaming

Nigel Davis 

Nigel Davis informs about progresses in the gNMI structure of PM data (both UML and YANG) and related Protobuf encoding data.

  • Next week will present some skeletons and pictures.

Regarding delta streaming, Nigel Davis recalls the challenge of mandatory properties which cannot be omitted even if not changed.

  • Andrea Mazzini what about the tree depth? If a parent level attribute changes, shall the whole subtree be streamed?
  • Answer is the same, if all the elements of the subtree are optional (in the UML/YANG), it is possible to condition them (e.g. in the RIA) according to the specific case, e.g.:
    • GET operation: in the reply always include all available parameters.
    • Streaming: in the stream include only the changed attributes.
    • Nigel Davis adds the consideration that a list shall be always streamed as a whole, in case one or more elements are added/removed/modified.
90 mins

Path Computation UCs


Andrea Mazzini shows slides 179-204 from updated otcc2022.AM.001_TAPI_RIASlides.pptx

Discussion items:

  • Jonathan Sadler mentions the result/state of Path Computation Service, e.g. optical metrics (available in calculated Paths).
    • Input: bounding
    • Output: actual values
  • Nigel Davis underlines that the Path object is currently modeled as a list of Links, hence there is no place e.g. for Node impairments.
  • Esther, the Path Computation Service constraints are essentially related to the topology and the 3R capability.
  • Gabriele Galimberti the including/excluding of 3R are constraints for optical feasibility, but by design, i.e. following the network planning previously performed.
    • Other optical parameters can be optionally specified as Path Computation Service constraints.
    • In general we need to be flexible, including full range of possible topological and optical constraints driving the computation.
  • Esther considers that the same model could be used for both planning and provisioning.
    • Ramon Casellas we already have the example of externalized Path computation (GNPy), anyway it would be recommendable to have same model for same entities but involved in different management steps.
    • Consider both Compute Path and Validate Path features.
  • Then long discussion on which are the essential differences between TAPI Connectivity Service and TAPI Path Computation Service.
    • Path is not reserving resources.
    • Could Path Computation Service constraints be exactly the same as Connectivity Service constraints?
    • Ramon Casellas Path shall include its partition, i.e. timeslot(s), wavelength(s).
      • A Path as a list of Links (OMS Sections) and wavelength slots valid for a given application

The conclusion is to continue exploring the real need of Path Computation Service and Path as distinct entities with respect to Connectivity Service and Connection-Route.

  • Investigate which enhancements to Connectivity Service may satisfy Path computation Use Cases.