-
Notifications
You must be signed in to change notification settings - Fork 0
2024‐10‐29 TAPI Meeting Minutes
Date
- 29 October 2024
Attendees
- Dacian Demeter
- Roshan Joyce
- Gabriele Galimberti
- Kishore Kumar Kowthalam Gajula
- Esther Le Rouzic
- Brian Johnson
Restart of the TAPI Subproject. New leaders have limited experience. Patience in sorting out direction and procedures is appreciated.
Actions
- Brian: setup meeting with TIP for roadmap discussion
Brief review of activities and discussions prior to the break. TAPI 2.6.0 Includes addition of OTSiMC and OTSiMCA Reviewed Roshan's [extensive] comments for TAPI 2.6.0 (Version 3.2) - Andrea resolved all comments
The TAPI 2.6.0 plan as of June 13th was: https://github.com/Open-Network-Models-and-Interfaces-ONMI/TAPI-Activities/wiki/TAPI-Plan
Digital payload of photonic media (OTSIMCA) - Complete
○ The management of inverse multiplexing can be attached to the OTU/ODU or OTSiMCA CEP instance, unique client of the NEP which represents the digital payload supported by one or more optical carriers
○ Simplified the DSR over OTSiMC model, by skipping OTSiMCA layer in case there is no multiplexing at L1, i.e. only one DSR CEP client of DSR NEP client of OTSiMC CEP(s).
Transceiver Profile (capabilities) - Reached general consensus , but not complete? ○ Need for capability model for provisioning (query device?) and for planning (no network) ○ Explicit vs standard vs organizational - is there enough information to determine compatibility (of transmission capabilities)? ○ Need to define a structure to the profile to prevent repetition ○ (IETF models don't scale due to repetition) ○ https://github.com/Open-Network-Models-and-Interfaces-ONMI/TAPI-Activities/wiki/Discussion-%E2%80%90-Transceiver-Model
Photonic Model (Status unknown) ○ GOSNR (Generalized OSNR) approach and possible enhancements to the explicit profile
Node - Device linkage (Status unknown) ○ Review of UML/RIA related updates
Model for Multi-technology Network Interface (Status unknown)
Recent Contributions ○ UC 11b: “Modification of service nominal route to secondary (protection) route for maintenance operations” ○ Unidirectional switching of bidirectional service/connection – see contribution CS and Top Connection Directionality.pptx § Presentation on forward and backward A-Z peer references
Other Topics ○ Manual editing to improve autogenerated .yaml modules • The YANG specifications are generated from the corresponding UML model in the SDK release using the ONF EAGLE UML2YANG mapping tool and further edited manually to comply with the ONF IISOMI UML2YANG mapping guidelines.
Reviewed https://github.com/Open-Network-Models-and-Interfaces-ONMI/TAPI-Activities/wiki/TAPI-Plan
- status of most items is uncertain. This needs review prior to setting priorities moving forward
- Notes:
- Topology Management item (DSR/OTN --> PHOTONIC_MEDIA or (new) ELECTRICAL_MEDIA) seems to be completed
- Digital payload of photonic media (OTSIMC/OTSIMCA) completed.
- RIA restructuring not completed
- All other items need assessment
- Note this iETF draft: Data Modelling and Gap Analysis of Optical Pluggables in Packet Over Optical Network (https://datatracker.ietf.org/doc/draft-rokui-ccamp-actn-wdm-pluggable-modelling/)
Roadmap (TBD) Link to TAPI Activities: Candidate+Features+for+Future+Releases+of+TAPI+SDK+and+RIA.doc (https://github.com/Open-Network-Models-and-Interfaces-ONMI/TAPI/blob/tapi-team-activities/TAPI-TEAM-ACTIVITIES/Plan/Candidate%2BFeatures%2Bfor%2BFuture%2BReleases%2Bof%2BTAPI%2BSDK%2Band%2BRIA.doc)