Skip to end of metadata
Go to start of metadata




  • Admin
    • Any update on liaison between TIP and ONF?
  • Review of last updates for version 2.3 delivery
    • “undefined” type for object creation notification contents?
  • Delivering RIA 1.1 (ONF TAPI RIA)
    • Outcomes from the dedicated review calls 
    • Selection of UCs which review is necessary for RIA 1.1 delivery, e.g.
      • 0d – clarification on SAPI/DAPI vs. TxTI/ExT
      • 3d - Constrained Provisioning diversity based on SRG / Diverse Routing in SRG failure
      • 5d - Asymmetric service provisioning with 1+1 Protection with Diverse Service Provisioning (eSNCP)
      • ASON related UCs
      • 12a: Pre-calculation of the optimum path
      • 12b: Simultaneous pre-calculation of two disjoint paths
  • Server constraints vs. multiple augment of (distinct) technology specific packages

Agreed Items & Priority

  • Below the list of the agreed items and related priority.
  • An item is blocking when its resolution is necessary precondition for the delivery.

TAPI 2.1.3 and RIA 1.1

  1. OTU(+ODUCn) CEP/CSEP as single point for OTU/OTSiA ConnectivityService provisioning (solved)
  2. ENNI/INNI Asymmetric service provisioning for multi-domain scenarios, agree UCs (solved)
  3. Alarm / TCA notification (solved - work ongoing on probable cause list)
    1. Subscription
    2. Notification contents
      • Probable Causes / Elementary alarms (e.g. ITU-T cZZZ fault causes), including TCA PM Parameters
  4. OTS and OMS model (solved)
  5. Path Computation Use Cases (blocking)

TAPI 2.3/2.4 and RIA 1.2

  1. MEP/MIP model vs. direct inclusion of OAM parameters in the CEP (solved)
    1. ODU OAM
    2. Photonic OAM
    3. TCA provisioning
  2. Physical impairments (not blocking)
    • OFC is augmenting TAPI Link, others the AbstractStrand.
    • Type of amplifier, fibre attenuation, etc.
  3. Photonic model capability (not blocking)
  4. Lifecycle management of ConnectivityService at every layer, necessary to identify UCs (not blocking)
    • Lifecycle management of single ConnectivityService, necessary to identify UCs
  5. 3R (not blocking)
  6. UNI Client interfaces modelling. DSR/ODU multiplexing over ODU (not blocking)
  7. RESTCONF Response codes for use cases (not blocking)
  8. TAPI OAS, action points to be assigned (not blocking)
  9. Routing Constraints (not blocking)
  10. Physical Route (not blocking)

Discussion items

5 minsAdministrative


Review of TR-547 1.1: Scheduled 2 hours calls for Aug 5, 6, 9, 10, 12, 13.

  • Invited Ramon, Nigel, Ronald, Pedro, Arturo. Please others interested to contact Andrea.

TAPI weeky call - canceled

TAPI weeky call - canceled (Andrea is not available)

 TAPI weeky call - canceled (Andrea is not available)

 TAPI weeky call

5 minsTIP MUSTNigel Davis

 Nigel Davis informs that TIP MUST should have become accessible also to vendors.

60 mins

Review of last updates for version 2.3 delivery

  • “undefined” type for object creation notification contents?

Andrea Mazzini presents the last updates to the UML model candidate for 2.3 release.

  • TapiOdu and TapiPhotonic, the comments on the diagrams have been copied (and when necessary restructured) to the comments of relevant object classes, hence making them available also in generated Yang modules.
  • TapiOam, added to OamJob a reference to ConnectivityService, in case the OamJob instance is not related to any OamService/Point but created together with ConnectivityService through ConnectivityOamJob augment.
  • “undefined” type for object creation notification contents, agreed to define in TapiCommon a new primitive type AnyType to be used as the generic type for the content of object creation notification.
    • Check how uml2yang tool manages this new primitive.