Skip to end of metadata
Go to start of metadata

Date

14 August 2018

Attendees

Goals

  • Administrative Updates
    • TAPI 2.1 Plan Update
  • Main Discussion Items
    • OTSi Media Model
      • Github UML/Yang Model Updates
      • Termination arrangement
      • Photonic Parameters
  • Other Github UML updates recap
    • TAPI OAM Model
      • OamProfile – PmThreshold & PmBin
    • TAPI Common/Topology/Connectivity Model
      • LayerProtocolQualifier
      • Aggregation/Assembly/Pooling association for Connection/CEP
      • Connection/Link association
      • Bidirectional Navigability for certain associations
      • Resilience Type/Constraints
        • GitHub Issue - #310
  • Other issues
    • RESTConf compliance of TAPI OpenAPI
    • TAPI Equipment/Inventory Model
    • ODU/DSR (L1) Model Enhancements
      • OTU Layer attributes for CEP & MEP
      • Representation of ODU channelization info in SIP/CSEP
    • Github Issues
      • ETH VLAN Config #313
    • Notification enhancements
      • Subscription to specific attribute changes
      • Representation of change-delta for deep/complex attribute data-types
    • Review of TAPI RI example(s) and desired enhancements
  • TAPI 2.0 Documentation and Use Cases
    • Termination Model (SIP, SEP, NEP, CEP)
    • Multi-layer, Multi-domain Connectivity
    • Resiliency, Protection & Restoration
    • OAM, Performance and Monitoring

Discussion Items

TimeItemWhoNotes
5 minsGeneral Administrative & StatusKarthik Sethuraman
  • Next TAPI call: Next Week
  • TAPI 2.1 Plan
    • Release has been delayed
    • Old target of 3Q-start 2018, new target 3Q-end 2018
      • First RC end of this month - draft on github
    • Key items
      • TAPI Photonic Media
        • target ODTN project
      • TAPI OAM (mostly ETH) Updates
        • target MEF NRM-OAM project
      • OpenAPI updates for Restconf Compliance
      • TAPI Equipment Inventory
        • Moved to TAPI 2.2 - mainly due to lack of time to discuss/review on TAPI calls
  • OIF TAPI Interop Status
  • ODTN phase 1.5
    • Control of Open Line System domain introduced
      • P2P ConnectivityService from ROADM Add-Drop Port to ROADM2 Add-Drop Port
      • Photonic MC (MediaChannel) Connectivity
      • Discussion ongoing whether to only use Generic TAPI Connectivity model or require Photonic Media model augment
    • Phase 1.0 controlled the transponder domain
      • P2P ConnectivityService from TPND1 Client Port to TPND2 Client Port
      • DSR layer Connectivity
      • Only Generic TAPI Connectivity model used
    • Activity will be mostly focused on mapping TAPI OLS photonic parameters to southbound
90 minsPhotonic Media & OTSiAndrea Mazzini

Nigel Davis

Stephane St-Laurent

Karthik Sethuraman

Action Items