Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

This call is being recorded

Date

06 February 2018

Attendees

Goals

Discuss OIF Interop activity as well as TAPI Termination Model and Multi-layer Examples. 

Agenda

Administrative

    • TAPI SDK 2.0.1 Release Plan
    • External TAPI-related activities: OIF 2018 TAPI Interop

TAPI 2.0 Documentation and Use Cases

    • Multi-layer, Multi-domain Connectivity
    • Termination Model (SIP, SEP, NEP, CEP)
    • Resiliency, Protection & Restoration
    • OAM, Performance and Monitoring

TAPI 2.0 SDK Items (contribution driven)

    • Github Issues

Discussion Items

TimeItemWhoNotes
5 mins

General Administrative

To-be-removed
  • Next week - Focus on OTSi and ODU Spec Models
5 mins

TAPI SDK 2.0.1 Release

To-be-removed
  • TAPI 2.0.0 released on snowmass github
    • Issues/comments on the RC3 version were posted on snowmass github
    • Issues were prioritized and some were addressed. Rest were deferred to 2.x.
  • TAPI 2.0.1 Items - target date mid-Feb
    • Yang modules meta data/information - Copyright, version, contact, etc (must have)
    • Working version of TAPI RI - current version in 2.0 does not work (SNAPSHOTS available from this week on snowmass git repository)
      • AI to To-be-removed
      • Compile tapi-connectivity.swagger using swagger-codegen tool
        • Use swagger-codegen to generate Python-flask server and Python client stubs
      • Returns responses from a predefined/static json file
    • Update to the .swagger files generated from yang using eagle tool (updates to the eagle Yang2OpenAPI tool)
      • AI to To-be-removed
      • '-' in REST input parameter names need to be replaced by '_' to confirm with python-flask/connexion convention
        • no change to class/attribute/enum names
    • Add additional rates to LayerProtocolName
    • Enhance Topology Pacs descriptions
    • CapacityPac attributes are always read-only in current version
      • This needs to be read/write when used in ConnectivityService request.
    • OAM Module Bugs (noticed by MEF)
    • Other Github Issues ?
30 mins

TAPI-related external activities:

  • OIF 2018 TAPI Interop
Lyndon Ong
  • Main focus is PRESTO/TAPI 2.0.x Testing
  • IA Spec development in progress currently
  • Actual testing in carrier labs in April/May
  • 4 Use cases
    • Multi-domain, Multi-layer Connectivity
      • Setup, Recovery, Re-optimization
      • Expect 10G-ETH and/or ODU2 interfaces
  • 7 Vendors, 4 Carriers
  • Questions
    • How to SIP attributes esp. specifying ODU trib/timeslot information
      • TAPI itself has not defined SIP attributes for any technology
      • Current MEF NRM/NRP spec/sdk defines SIP/CSEP/CS attributes for ETH (L2)
      • For ODU/L1, MEF has only TS (paper) for service definitions (no model/SDK)
        • We could either use the MEF L1 drafts to develop the SIP/CSEP/CS models as joint OIF/ONF/MEF activity with OIF Interop project
        • Or we could use an shortcut method to develop an "label" format to be passed as name attributes of SIP/CSEP/CS
    • Alignment of PRESTO and TAPI
      • expect it to be aligned, but this is more of an OIF discussion point as it involves bridging MEF and ONF
15 minsMulti-layer ExampleLyndon Ong

Documents

 

60 mins

Termination Model (SIP, SEP, NEP, CEP)
  • Fixed mapping case
  • Multilayer switching
  • Multi-stage multiplexing
  • Inverse multiplexing case
  • Asymmetric connectivity case

Andrea Mazzini

To-be-removed

Documents

TBDTAPI 2.0 Github Issues 

Not discussed due to lack of contributions

Action Items / Task Assignments

Github Issues

General Areas to be worked on (target at least 1 item per week for discussion in TAPI call - a brief contribution should be provided)

  •  UML Lifecycle sterotypes - capture maturity of TAPI classes/attributes explicitly - no stereotype means "not determined"
  •  Entity Lifecycle - (Lifecycle/Operation/Administrative state enumerations): need more explanation, documentation and inter-state-dependency diagrams
    • Some state diagrams are available in Core IM 1.3 Foundation module (512.3 figures 3-4, 3-5, 3-6 & table 16)
  •  Topology pacs: need develop descriptions/examples how that can be used
  •  "key" attributes should be extensible enumerations instead of string type (e.g. address-type, cost-name)
  •  Termination pac (State/Direction) - needs discussion on usage or even if we need them
  •  Generalized Capacity data structure
  •  OTIM- OCH & OTSi usage clarification from ITU-T SG15
  •  Extensible Enumerations - should all TAPI enumerations be extensible by default ?
    • Semantic v/s vendor/interface/run-time extensible
  •  Backward compatibility
  •  NMDA compatibility
  •  Multi-vendor Inter-operability gaps
    • Can it be addressed by development guide/guidelines?

2018 TAPI Features

General Areas to be worked on (a brief contribution should be provided)

  •  TAPI SDK release schedule (timefarme based)
    •  2.0.1 - Feb-mid?
    •  2.1 - July 2018?
    •  2.2 - Jan 2019?
  •  TAPI Reference Implementation framework
    •  single layer use case
    •  multi-layer symmetric use case
    •  multi-layer asymmetric use case
  •  TAPI SDK/Model Refinement/Enhancement
    •  OAM model
    •  Virtual Network model
  •  TAPI examples and documentation
    •  Termination
    •  Multilayer
    •  OAM
    •  Node Constraints
  •  Technology Spec Model
    •  ODU
    •  OTSi/OCh
    •  Media (photonics)
    •  Ethernet
    •  Wireless
  •  ? Device/Equipment configuration interfaces
  •  ? Physical Inventory
  •  ? Mgmt of Device Control interfaces
  •  ? Mgmt of Synchronization/Timing
  •  ? Profiles & Templates