Skip to end of metadata
Go to start of metadata

Date

Attendees

Goals

  • Admin
  • The model of 3R
  • Continue the discussion on potential CTPs/CEPs model (transmission capability)

Agreed Items & Priority

Discussion items

10 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.

Easter 2022: Nigel is ooo the first week of April, Ramon the second week. We will anyway proceed with the RIA review.

Only for this week agreed to have two additional calls:

  • Wed 13, 12:00-2:00pm and Thu 14, 10:00-12:00 CEsT

Asked to ONF to extend the additional, official, dedicated TAPI calls till July 2022.


TAPI weeky call canceled

TAPI weeky call

Preliminary agenda:

  • Continue the development of Optical Impairment UML model
  • Capability model
5 mins

pull request #519

Karthik Sethuraman 

Karthik Sethuraman is reviewing the changes.


50 mins

The model of 3R

All

Andrea Mazzini shows this slide on the subject.


  • Nigel Davis indicates that the color of OTSi is locked by the spare route which does not include any regeneration.
    • In general the recoloring is avoided
    • OTSiMC is a four ended Connection, the OTSiMC ConnectivityService is always point to point, transponder to transponder.
  • Broadcast between degrees, agreed to not represent the default connectivity, but only the MC CEP and XCs which actually support a ConnectivityService.

Discussion on SIP:

  • A SIP shall not refer to NEPs, one or more NEPs may refer to a SIP.
  • A SIP shall be associated to one or more AccessPorts, e.g. all the AccessPorts of a building.
    • Karthik Sethuraman we may move the AccessPort to TapiCommon to avoid to force the support of Equipment model.
    • Nigel Davis alternatively the SIP can include - in case the Equipment model is not supported - some loose attributes indicating the position in the physical network, similarly to the INVENTORY_ID.
    • Karthik Sethuraman SIP can be everywhere, Nigel Davis so far we positioned the SIP only where a ConnectivityService can be provisioned.