Skip to end of metadata
Go to start of metadata




  • Admin
    • Plan next TAPI virtual meeting
    • Streaming RIA follow up
  • Review the updated TR-547-TAPI Reference Implementation Agreement_v1.1.docx
    • New use cases: 0d, 1g, 1h, 2a, 2b, 2c, 3d, 3e, 3f, 5d, 11a, 11b, 13b, 13c, 16a, 16b.
      • NEP/SIP Capability model
      • Link model, agree a general rule
  • Updated Alarm Tables
  • Clean up of “Experimental” stereotypes

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 (blocking, 1)
    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 (blocking, 2)
  5. Path Computation Use Cases (blocking, 3)

TAPI 2.3 and RIA 1.2

  1. MEP/MIP model vs. direct inclusion of OAM parameters in the CEP (blocking, 1)
    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

60 minsAdministrative


Next TAPI virtual meeting. candidate week is

  • 12-23 April - consider 2+1 days/5 hours - focus on limited number of items.

Review of Agreed Items & Priority, see above.

Nigel Davis will set up a separate call for clarification regarding TR-548 scope.

  • Karthik Sethuraman suggests to involve Jack Pugaczewski, who is active in MEF and TMF on streaming subject.

Ramon Casellas plans to provide an updated RIA 1.1 draft by the virtual meeting.

 TAPI Call: 2 hours

Review the updated TR-547-TAPI Reference Implementation Agreement_v1.1.docx

  • New use cases: 0d, 1g, 1h, 2a, 2b, 2c, 3d, 3e, 3f, 5d, 11a, 11b, 13b, 13c, 16a, 16b.
  • Link model, agree a general rule.

45 mins

Review the updated TR-547-TAPI Reference Implementation Agreement_v1.1.docx

  • NEP/SIP Capability model

Continued the discussion on this picture:

  • Nigel Davis points out that it may be unnecessary that SIP shall include all supported clients, as they may be several and a reasonable assumption is that any client layer protocol can be supported. Also noted that if new clients become supported (network improvements), then all SIPs shall be accordingly updated, notifications sent etc.
  • Karthik Sethuraman suggests to add the relationship between ENNI OTN SIP and the DSR NEP ending the (not shown) DSR Link.
  • Discussion on the need of Layer Protocol Name and Qualifier in Connectivity Services and Connections. Agreed that is fundamentally redundant, because the layering information is available on end points (CSEP/CEP). Anyway considered useful for query purposes, e.g. GET all Connectivity Services at a given layer.
    • Andrea Mazziniadd the Layer Protocol Name and Qualifier to the Connectivity Service (version 2.3)
  • Agreed that the ODU2 CEP "floating point" shall have its server OTN NEP.
  • To be discussed the distinction between ENNI and INNI SIPs. Actually the INNI SIPs are the entry points for the provisioning of infrastructure ConnectivityServices, which build the Links of client virtual topology.
  • Karthik Sethuraman regarding NEP capability, we should reconsider the Node to show capabilities.
15 mins

Updated Alarm Tables

Andrea Mazzini

Andrea Mazzini presents TR-547-TAPI RIA V1.1 Alarms.xlsx , which is a copy of the spreadsheet included in TR-547-TAPI Reference Implementation Agreement_v1.1.docx with some additional columns mapping the proposed alarm probable causes with ITU-T G.798, G.806, G.7041.