Skip to end of metadata
Go to start of metadata


07 August 2018



  • Administrative Updates
  • Main Discussion Items
    • OTSi Media Model
      • Base Termination Model recap
      • UML Model Updates
      • Photonic Parameters
  • Other issuesReview of TAPI RI example(s) and desired enhancements
    • TAPI OAM Model Updates (Karthik)
      • OamProfile – PmThreshold & PmBin
    • Resilience Type/Constraints (Andrea)
      • GitHub Issue - #310
    • 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
    • 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

5 minsGeneral Administrative & StatusKarthik Sethuraman
90 minsPhotonic Media & OTSiAndrea Mazzini

Nigel Davis

Stephane St-Laurent

Karthik Sethuraman

  • Photonic Media LTP Model Arrangements
    • Aligned labels/terminology to ITU-T G.MEDIA
    • Stephane questioned the need to model OtsiG-O
    • Agree to first focus on the Forwarding model ignoring OAM aspects
    • Do we really need to model Assembly CEPs if we do not model OAM ?
      • Can the "Assembly/Bundle" Connection be represented without "Assembly" CEPs?
    • Andrea presented various cases of SMC-NMC relationships below
    • Why should we qualify SMC and not just call it a media channel - we need to qualify different types of media channels for discussion purposes.
      • OTS, OMS, SMC & NMC are all media channels - lowerFreq, upperFreq
    • Still we need to define the characteristics/definition of the SMC
      • SMC = One or more NMCs + Guard bands
      • Construct used for representing paths in the ROADM networks
    • Clarified that the purpose of degree SMC above is to carry NMCs efficiently by applying guard-bands for some combined set of NMCs
    • The SMC switch XC above represents a combiner/splitter abstraction - irrespective of the implementation technology (passive v/s WSS based)
    • Both 1.3 & 1.4 are valid cases, but normally, in case 1.4, it may make more sense to model as 2 SMCAs
      • Also possible to scramble NMCs in the SMCs (e.g. SMC1–>NMC1+NMC3, SMC2–>NMC2, NMC4)
    • Update all the cases above to associate the SMC construction to the SMC XC rather than degree SMC CEP

Action Items