1. Pages
2. …
3. Open Transport Configuration and Control Home
4. OTCC
5. OTCC Meeting Notes

2020-05-26 TAPI Meeting notes

Andrea Mazzini

• Next F2F TAPI meeting: Virtual Meeting to be planned
  

• 02 Jun 2020 TAPI Call: 3 hours Andrea Mazzini not available - Nigel Davis agrees to manage the call to progress on:
  
  • Streaming documentation
    • oimt.2019.ND.017.00-TapiStreaming.mht (as well as oimt.2019.ND.016.00-StreamingDiscussion.pptx, oimt.2019.ND.018.00-StreamingSummary.pptx and oimt2020.ND.005-Streaming.pptx)

Arturo Mayoral

Arturo Mayoral reviews the updates on TR-5XX.1-TAPI v2.1.3 Reference Implementation_v0.10.docx (Reference Implementation Agreement, RIA):

1. Transitional Link: agreement on proposed updated text
   • Reflecting the agreement of 2020-05-12 TAPI Meeting notes, items 4 and 5.
     
2. qianjia asks clarification on MC Link scenario:
   1. Confirmed the optionality of all Links, exceptions being:
      1. the PHOTONIC_MEDIA Links (necessary to describe the topology at "day zero"),
      2. the Transitional Links (necessary to join electrical and optical Nodes at "day zero", when applicable).
   2. Agreed that the Link is essentially an abstraction of information already provided by its server Connection/CEP/NEP.
      • Arturo Mayoral we may reconsider this assumption in future evolutions of the RIA.
3. Arturo Mayoral UNI modelling simplification, agreed the proposed text, integrated with some further clarifications.
   1. Reflecting the agreements of 2020-05-19 TAPI Meeting notes, item 8.
4. Agreed to remove the following Use Case, as we have not reviewed it with the necessary level of detail:
   
   • UC1e - Example 8: OTSiA multi-wavelength over two OTSi/OTSiMC over a single physical (PHOTONIC-MEDIA_OMS) port through a single MC.
5. Confirmed to keep only the requirement for "_selectedConnectionEndPoint" attribute of Switch class
   • Reflecting the agreements of 2020-05-19 TAPI Meeting notes, item 4.

• Andrea Mazzinito update TAPI 2.1.3 RC2 with the agreed modifications on 2020-05-04 / 08 TAPI Virtual Meeting Agenda and Notes, Wed 6/P3.
  • Agreed to NOT modify TAPI 2.1.3 RC1.

Arturo Mayoral uploaded the TR-5XX.1-TAPI v2.1.3 Reference Implementation_v0.11.docx version candidate for official delivery:

• We need to check the ONF process for TR delivery
• Karthik Sethuraman Post meeting note: we need to engage at the ONF board level as TAPI and OTCC TST would prefer to assign it a TR number.
  • Lyndon Ong Karthik Sethuraman Andrea Mazzinito follow up on this.
    

Andrea Mazzini

Andrea Mazzini briefly recaps TAPI available model for ODU OAM

• Necessary to review some attributes: Hing-Kam Lam provides link to the latest draft text of G.875, currently under Additional Review (AR) of the approval process.

Andrea Mazzini

Andrea Mazzini presents otcc2020.AM.002-Transmission_Capability.pptx

• General agreement on the approach, with the following notes:
  • Malcolm Betts the ODU Flex payload can be organized in complex ways, more details may be necessary to describe capability
  • Nigel Davis the invariant parts shall be centralized in appropriate spec/rule descriptions
  • Andrea Mazzini capability on UNI side need refinements