Skip to end of metadata
Go to start of metadata

Date

26 June 2018

Attendees

Goals

  • Administrative Updates
  • Main Discussion Items
    • OTSi Media Model
      • Dis-aggregation Use Case (ODTN)
      • Multi-vendor OMS Use Case (Martin)
      • UML Model
      • OTSi OAM in MEP/MIP style
  • Other issuesReview of TAPI RI example(s) and desired enhancements
    • 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
      • Multi-layer NEP #309
    • Migration to Papyrus Oxygen
    • Migration to latest OpenModelProfile
    • RESTConf compliance of TAPI OpenAPI
    • Notification enhancements
      • Subscription to specific attribute changes
      • Representation of change-delta for deep/complex attribute data-types
  • 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 - Nigel to host (karthik unable to attend)
  • OIF Interop Status
    • Testing official completed last week, but participants have agreed to continue testing for couple of weeks more
    • First public readout at NGON this week
    • TAPI 2.0.x being tested
60 minsOTSi Model

Karthik Sethuraman

Nigel Davis

Stephane St-Laurent

Andrea Mazzini

  • TAPI OTSi Overview


  • Transponder-Roadm interface
  • is OTSiA-Otsi relationship an assembly or an inverse multiplex? Agree that it is inverse multiplex, although it is actually OtsiG adaptation that is inverse multiplex. TAPI will name the Pac classes appropriately.

Action Items

  •