Skip to end of metadata
Go to start of metadata

Date

17 July 2018

Attendees

Goals

  • Administrative Updates
    • 2.1 Plan update
  • 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
    • Resilience Type/Constraints (Andrea)
    • TAPI OAM Model Updates (Karthik)
      • OamProfile – PmThreshold & PmBin
    • 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

TimeItemWhoNotes
10 minsGeneral Administrative & StatusKarthik Sethuraman
  • Next TAPI call: Skip next week due to MEF
  • OIF TAPI Interop Status
  • TAPI 2.1 Plan
    • Release has been delayed
    • Old target of 3Q-start 2018, new target 3Q-end 2018?
      • First RC mid of next month
    • Key items
      • TAPI Photonic Media
        • target ODTN project
      • TAPI OAM (mostly ETH) Updates
        • target MEF NRM-OAM project
      • TAPI Equipment Inventory
      • OpenAPI updates for Restconf Compliance
90 MinsPhotonic Media & OTSi

Andrea Mazzini

Nigel Davis

Stephane St-Laurent

Karthik Sethuraman

Adriana Veronica Errigo

  • Base Termination Model
  • UML Model Updates
    • https://github.com/OpenNetworkingFoundation/TAPI/tree/develop/UML
    • LayerProtocolName updates - move existing sub-LayerProtocolNames out into LayerProtocolQualifier
      • OTSiA, OCH, OTU & ETY will be moved
      • LayerProtocolQualifier enumeration is used to qualify the sub-layers (if applicable) for a specific LayerProtocol.
        This extensible enumeration is intentionally empty in the common module and will be augmented with layer-specific values in the respective technology-specific modules.
        Examples:
        - LayerProtocolName := OPTICAL_DATA_UNIT
        LayerProtocolQualifier := "ODU_FLEX", "ODU_0", "ODU_1", "ODU_2", "ODU_2E", "ODU_3", "ODU_4"", "ODU_CBR"", "ODU_GFP"", "ODU_GFP_HAO", etc
        - LayerProtocolName := DIGITAL_SIGNAL_RATE
        LayerProtocolQualifier := "GBE", "10_GBE_WAN", "10_GBE_LAN", "100_GBE", "FC_100", "FC_200", "FC_400", "FC_800", "FC_1200", "FC_1600", "FC_3200", "STM_1", "STM_4", "STM_16", "STM_64", "STM_256", "OC_3", "OC_12", "OC_48", "OC_192", "OC_768", "OTU_1", "OTU_2", "OTU_2E", "OTU_3", "OTU_4", "GPON", "XGPON", "IB_SDR", "IB_DDR", "IB_QDR", "SBCON_ESCON", "DVB_ASI", "SDI", "SDI_1G5", "SDI_3G", etc
        - LayerProtocolName := PHOTONIC_MEDIA
        LayerProtocolQualifier := OCH, OTSi, OTSiA, NMC, NMCA, SMC, SMCA, OMS, OTS

    • Rename the existing TAPI OTSiA module to PhotonicMedia
    • Need to review the Photonic parameters spreadsheet (link below) and merge relevant attributes into the TAPI Photonic Media UML.
  • Photonic Parameters - summary provided

Action Items