Open Transport Configuration & Control
Space shortcuts
Expand all   Collapse all
Child pages
  • 2018-01-23 TAPI Meeting Notes
Skip to end of metadata
Go to start of metadata

This call is being recorded

Date

23 January 2018

Attendees

Goals

Discuss TAPI Termination Model and Multi-layer Examples. 

Agenda

Administrative

    • TAPI SDK 2.0.1 Release Plan
    • External TAPI-related activities

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

TAPI 2.0 SDK Items

    • Github Issues

Discussion Items

TimeItemWhoNotes
5 mins

General Administrative

To-be-removed
  • Skip Next week call due to MEF, ITU-T meetings
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
    • OAM Module Bugs (noticed by MEF)
    • Other Github Issues ?
5 minsTAPI-related external activitiesLyndon Ong

From OTCC 2018-01-22 OTCC TST Meeting Notes

 

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

  • Document on OTCC Wiki:
  • Discussed Andrea's contribution
    • Base case is 10G/40G DSR over flexible-switched 10G/40G ODU over fixed-mapped 100G ODU
    • Second case is 10G/40G DSR over flexible-mapped 10G/40G ODU over switched 100G ODU
  • Question - does instance of TranstiionalLink and corresponding the CEPs (TTP/CTP)s exist at the same time?
    • Yes:
      • TransitionalLink represents capabilities/possibilities as topological information
      • CEP/Connections represents provisioned connectivity information
    • As in "normal" Links, the CapacityPac attributes of TransitionalLink are used to represent used/available capacity
  • CSEP probably most better places to store the remote termination information (such as intermediate-sub-layer ODU timeslots) in case of multi-layer asymmetric cases
  • For Option B, the TransitionalLink is probably not needed and can be replaced by a single multi-layer SIP or 2 single-layer SIPs each of which would contain some matching label/information (PLUG ID, TRI, etc)
  • Need to update the slides with proper/missing legends
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