| Time | Item | Who | Notes |
|---|
| 15 mins | General Administrative & Status | Karthik Sethuraman | - Next TAPI call: Skip next week Tuesday call to prepare for F2F? Use Thursday 5 AM PDT (OIMT+TAPI).
- OIMT/TAPI F2F - co-located with ONF Connect
- Dec 3-7, 2018 @ Infinera Sunnyvale, CA, USA
- TAPI on Tuesday afternoon & All day Thursday - Monday afternoon joint-ODTN
- Logistics & Agenda plan
- TAPI 2.1 Status
- Released on Oct 16, 2018
- Key items
- TAPI Photonic Media
- target ODTN project, phase 1.5
- TAPI OAM (mostly ETH) Updates
- target MEF NRM-OAM project
- Updated OpenAPI Specs (OAS) updates for Restconf Compliance
- Need to plan for next release
|
| 30 mins | TAPI Work Items and Next release plan | Karthik Sethuraman | - TAPI SDK release schedule (timefarme based)
- 2.0.0 - 2018 Jan-start
- 2.0.1 - 2018 Feb-mid
- 2.0.2 - 2018 Mar-end
- 2.1 - 2018 July-end
- OTSi Spec Model Updates to include OMS/OTS Media
- ETH Spec Model Updates to include OAM
- ODU Spec Model; Updates to include OTU
- DSR Spec Model
- OAM Model Updates to align with MEF NRM-OAM
- Notification Model Updates
- Equipment/Inventory Model (previously scheduled for 2.2)
- OpenAPI updates for RESTConf compliance
- 2.2/3.0
 - Timeline - 2019 Mar-end (Q1-end)
- SNAPSHOTS: Weekly starting DEC 2018 (TAGS)
- RC1: 2019 Jan-end (feature freeze)
- RC2: 2019 Feb-end
- RC3: 2019 Mar-mid
- Release: 2019 Mar-end
- Work Items
- Photonic Model updates
- OAM Model Updates
- Profiles & Templates
- OAM Profile - to support Ethernet PM, thresholds
- SLS Profile
- Routing Constraints
- Resilience Constraints
- Node Constraints
- Equipment Inventory
- ETH Model (non-OAM) Updates
- ODU Model Updates
- DSR Model Updates
- YANG conditional augments
- RESTConf/OAS Bugs/Enhancements
- Python-Flask Reference Implementation
- TAPI Requirements Updates (TR-527)
- TAPI Work Items (not release specific - checked means "being worked on")
- TAPI Model Refinement/Enhancement
- OAM model
- Virtual Network model
- Notification model
- Routing Constraints
- Resilience Constraints
- TAPI Documentation/Scenarios/Examples
- Termination Examples
- Multilayer Scenarios
- OAM Scenarios
- Node Constraints
- Technology Spec Model
- ODU/OTU
- OTSi Media
- DSR
- Ethernet
- Wireless
- TAPI Reference Implementation framework
- single layer use case
- multi-layer symmetric use case
- multi-layer asymmetric use case
- Equipment Inventory
- Equipment configuration
- Mgmt of Device Control interfaces
- Mgmt of Synchronization/Timing
- Mgmt of Software/Firmware download
- LTP Specification structure updates/enhancement
|
| 75 mins | | Andrea Mazzini | - https://github.com/OpenNetworkingFoundation/TAPI/pull/370
 - needed to avoid ambiguity in cases like periodEndTime < granularityPeriod
- need to change the label to periodStartTime in both History & Current Data classes
 - TAPI/ITU-T MEG maps to MAG+MA+MD
- MD properties is modeled just as an MEG property
- so MD properties will be duplicated across multiple MAs/MEGs in TAPI
- How to handle MIPs? IEEE MIP belongs to MD & not MA
- Separately IEEE MAG relationship to MA & MEP/MEPId-pointer seems wrong
|