Skip to end of metadata
Go to start of metadata




  • Admin
    • Plan for dedicated RIA 1.2 / 2.0 review calls (ONF TAPI RIA)
  • Continue the development of Optical Impairment UML model (depending on audience)
  • Updates on Connectivity model – the LayerProtocolConstraint object
  • Updates on OAM model
  • Physical Route

Agreed Items & Priority

Discussion items

10 minsAdministrative


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:

  • Physical Route
  • Continue the development of Optical Impairment UML model
  • Capability model
80 minsDraft of Optical Impairment UML modelAll

Andrea Mazzini shows the updated draft model. Added almost all the data types and comments.

Below the draft of Transceiver Profiles:

  • Esther Le Rouzic clarifies that the frequency granularity and grid type are necessary parameters in ROADM Degrees (filter constraints), not in the transceiver.
  • Esther Le Rouzic confirms that CommonOrganizExplicit tx/rx channel power min/max are suitable parameters for a transceiver profile.
    • Also added the rxTotalPowerMax (max optical power for all the received channels) to the OtsiConfig (configuration of maximum allowed level) and to the OtsiTerminationPac (measurement).
    • Discussion ongoing on TIP MUST and OpenROADM on the relationship between received power and OSNR. These aspects need stabilization.
      • IETF and OpenConfig will align.
  • Esther Le Rouzic clarifies that maximum differential group delay is measured in picoseconds.
    • Other clarifications on units of measure. Use THz for frequency.
  • Future developments: configuration of the amplification function, added target in/out VOA and the PowerParams.

Below the other profiles and states:

30 mins

Updates on Connectivity model – the LayerProtocolConstraint object


Andrea Mazzini shows the LayerProtocolConstraint object of ConnectivityServiceEndPoint:

  • An example of Service provisioning with LayerProtocolConstraint instances (LPConstr):

  • Nigel Davis highlights that the scenario is applicable only in case of a single ODU4 server trail.

Discussion on SIP layer.

  • Ramon Casellas asks for a criteria to associate the SIP to the NEP.
    • Karthik Sethuraman clarifies that the idea is that the SIP is associated to the NEP
      • of the highest layer,
      • made available at time zero, i.e. defining the base topology.
  • Brief discussion on potential CTPs, a possible model to represent payload capability is to introduce the disabled CEP. For further analysis.