Open Transport Configuration & Control
Space shortcuts
Expand all   Collapse all
Child pages
  • 2018-05-08 TAPI Meeting Notes

Versions Compared

Old Version 12

changes.mady.by.user Karthik Sethuraman

Saved on

compared with

New Version Current

changes.mady.by.user Karthik Sethuraman

Saved on

Key

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

Date

08 May 2018

Attendees

Goals

  • Administrative Updates
    • Eclipse Oxygen Migration
    • TAPI Wiki Structure
  • Main Discussion Items
    • OTSi Media Model
      • Generic Model - Relationship of OMS-OTS to OTSi
      • OTSi OAM in MEP/MIP style
    • TAPI OAM Model
      • Updates to JobControl and JobConstraints
    • ODU Spec Model Review
      • Refactor spec models based on directionality
    • Github Issues
      • ETH VLAN Config #313
      • Multi-layer NEP #309
  • Other issuesReview of TAPI RI example(s) and desired enhancements
    • TAPI Equipment/Inventory Model
    • RESTConf compliance of TAPI OpenAPI
    • Representation of ODU channelization info in SIP/CSEP
    • 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
45 minsGeneral Administrative & StatusKarthik Sethuraman
  • Next TAPI call: Next Tuesday on May 15
  • Migration of TAPI UML to Eclipse Oxygen
    • Target is Eclipse-Papyrus 3.3.0
    • Importing a model created in Eclipse Mars mangles the end-roles of some associations
    • Nigel Davis has discovered a pattern to this behavior and the fix needs to be coded (todo: Karthik Sethuraman)
    • Expecting to write the script and perform this migration this week or next.
  • TAPI Wiki updated to include TAPI Documentation section
    • Idea is to put useful information on TAPI concepts and usage here
    • The pages will be tagged as a draft until is is approved by the OTCC TST
60minsOTSi Model

Nigel Davis

  • Media Channel in TAPI is modeled as an OTSiG Connection (bundle of OTSi media channels)
  • Media Channels in ITU-T - Constraining, concatenating and filtering the signal spectrum (ignores that OTSi requires DSP to resolve the spectrum)
    Disaggregated Node with Overheads and no amplifiers
  • Schematic with amplifier put back in the picture
  • Relationship of OMS-OTS to OTSi
    • Functional Flow and connectivity

  • Encapsulated into LTPs, FCs, FCs are at same layer, are connected/concatenated

0 minsGithub IssuesAndrea Mazzini
  • Not discussed due to lack of time - Notes from previous TAPI call below
  • ETH VLAN Config - Issue #313
    • ETHG (group of VLAN IDs) is used for OAM purposes where only a single VLAN is monitored

    • All VLANs in ETHG has to be co-routed, but beyond the scope of the OAM ME/MA, each of these VLANs may have separate route. Thus ETHG is not necessarily E2E.
    • But from an UNI-N side, all these VLANs are/should be bundled. So effectively they are a single connection

    • Is the below valid to model or monitor as a bundled-connection even if they belong to different services and if they are co-routed in the transit domain. No if needs to be done, OVC (S-Tags) has to be used.

  • Multi-layer NEP - Issue #309

Action Items