2024‐06‐11 TAPI Meeting Minutes

Date

• 11 June 2024

Disclaimer: ONF is disbanding and merging into Linux Foundation. Until is not fully clarified and agreed under which entity this project will land, no final decisions will be taken by the TAPI team for the TAPI next versions. TAPI team will at most agree recommendations, with final agreement postponed.

Attendees

• Andrea Mazzini
• Nigel Davis
• Pedro Amaral
• Brian Johnson
• Roshan Joyce
• Kam Lam

Tentative agenda:

• General update
  • Update on Linux Foundation
  • New TAPI wiki and discussion pages
• Considering to leverage the conditionality statements of RIA-TAPI 2.4/2.5 for RIA-TAPI 2.1.3
  • Coverage of missing/underspecified/unclear/erroneous old statements
• Photonic Model: continue the fix/update of the transceiver provisioning model
  • Check transceiver profile and transceiver parameters
  • GOSNR (Generalized OSNR) approach and possible enhancements to the explicit profile
• Manual editing to improve autogenerated .yaml modules (see here and here)
• UC 11a: “Modification of service path” and UML/YANG comments
  • Review of UML/RIA related updates
• UC 11b: “Modification of service nominal route to secondary (protection) route for maintenance operations”
  • Unidirectional switching of bidirectional service/connection
• Continue the discussion on digital payload of photonic media
• Model for Multi-technology Network Interface

Next Call, June 18

Andrea not available, Nigel to lead or postpone to June 25

• General update
  • Update on Linux Foundation
  • New TAPI wiki and discussion pages
• Photonic Model: continue the fix/update of the transceiver provisioning model
  • consolidate transceiver profile and transceiver parameters model
  • GOSNR (Generalized OSNR) approach and possible enhancements to the explicit profile
• Manual editing to improve autogenerated .yaml modules
• Node - Device linkage
  • Review of UML/RIA related updates
• UC 11a: “Modification of service path” and UML/YANG comments
  • Review of UML/RIA related updates
• UC 11b: “Modification of service nominal route to secondary (protection) route for maintenance operations”
  • Unidirectional switching of bidirectional service/connection
• Continue the discussion on digital payload of photonic media
• Model for Multi-technology Network Interface

---

Discussion item 1

General update

40 mins

1. Move to LF

   • This is the first TAPI call with the new LF zoom
   • No other news with respect to last week

2. New TAPI wiki pages

• Andrea shows two new TAPI repositories:
  • TAPI-Documentation
    • to safely store all the TAPI documentation (RIAs, etc.), leaving in the TAPI only the code (UML, YANG, OAS modules)
    • Note that a TAPI-documentation _release _has been created per each relevant TAPI SDK release:
      • TAPI-documentation Release 2.1.3
      • TAPI-documentation Release 2.4.0
      • TAPI-documentation Release 2.4.1
      • TAPI-documentation Release 2.5.0
  • TAPI-Activities
    • to safely store all the TAPI documentation not candidate for a TAPI delivery:
      • Contributions for discussions, plans, backup of TAPI wiki
• Regarding meeting minutes and dicussions, Andrea has centralized both in the TAPI wiki
  • Because the Github wiki is easily clonable, while Github discussions seems not

• Roshan suggests this link for the migration of TAPI wiki to TAPI-Activities wiki

---

Discussion item 2

Leverage the conditionality statements of RIA-TAPI 2.4/2.5 for RIA-TAPI 2.1.3

• Coverage of missing/underspecified/unclear/erroneous old statements

20 mins

Nigel proposes to use recent RIA versions as reference for missing/underspecified/unclear/erroneous statements of older RIA versions (mainly RIA 1.1 of TAPI 2.1.3)

• For example, the mandatory statement regarding equipment temperature
  • which can be fulfilled only if the detector is available, hence it is not mandatory but conditional
• Agreed to create a new RIA ancillary document where to track these findings and related agreed solution
  • E.g. "old statement" is replaced by "new statement" according to RIA version x.y
  • Nigel will provide a first draft

---

Discussion item 3

Discussion ‐ Transceiver Model

30 mins

---