Skip to end of metadata
Go to start of metadata

Date

Attendees

Goals

  • Proceed on 2.1.3 version freeze, tentative target March end: review of modifications and open issues
    • Any issue on Github side
    • Eqp model, slot/sub-slot
    • ODU Attributes (payload type, tributary slot list)
    • Multi-layer model / capabilities: at least in the scope of TR-5XX.1-TAPI v2.1.2 Reference Implementation
    • Bulk retrieval
  • OTSiMCA/MCA CSEP attributes
  • Preparation of May virtual meeting agenda

Discussion items

5 minsAdministrative
  • Next F2F TAPI meeting, Virtual Meeting:
    • -  
  • Call slot assignment: last week we were preempted by another ONF meeting overlapping last scheduled hour
    • ONF TAPI Call is scheduled by ONF admin from 3pm to 5pm CET
    • easonably we can ask to extend to four hours - with option for two additional hours "on demand".
    • Issue is temporary solved by ODTN project moving its call to Monday

  • TAPI Call: 3 hours, note that both Europe and US are in daylight saving time, call will start at 3pm CET 
    • 2.1.3 version freeze
    • ODU Attributes (payload type, tributary slot list)
    • Continue preparation of May Virtual Meeting agenda
30 mins

Github issues, Equipment Model UML

Arturo Mayoral and Nigel Davis clarify that the tool does not work correctly for a specific case, see https://github.com/OpenNetworkingFoundation/TAPI/pull/463 for details.

Agreed to perform a simple manual fix as identified in the comments.

Nigel Davis asks whether it is possible to avoid the stacking of changes in a single pull request. Karthik Sethuraman explains how to manage it.

Currently the 2.1 stream includes only YANG Equipment model.

  • Nigel Daviswill replicate in 2.1 the UML model from TAPI edge.
50 minsEquipment Model, Slot and Sub-Slot model

Summary of agreements:

  • No changes to current Equipment model, no hiearchy of slot and sub-slots, only one level of Holder.
  • Add clarifications in Reference Implementation regarding conventions on sub-slot numbering.
  • Nigel Davis, these detailed cases shall be described by the equipment specification object.
50 minsODU Attributes

Andrea Mazzini presents otcc2020.AM.002_TAPI_2.1.3_Enhancements.pptx

  • Summary of agreements (see the presentation for further details):
    1. Add OduConnectivityServiceEndPointSpec to 2.1.3 delivery
    2. Add oduRate to OduConnectivityServiceEndPointSpec
    3. Change all OduConnectivityServiceEndPointSpec attributes to read/write
    4. Remove/deprecate oduRateTolerance from OduCommonPac
    5. In OduConnectivityServiceEndPointSpec class, replace attribute label from acceptedPayloadType to configuredPayloadType
    6. Not necessary/urgent to compact oduType and oduRate in a single attribute (G.875 compacts oduType/Rate/RateTolerance)
  • For further evaluation:
    1. In OduTerminationAndClientAdaptationPac class, there is acceptedPayloadType attribute, which is meaningful for sink termination point, verify how to correctly map the ITU-T G.875 client type configuration applicable to source termination point.
  • Hing-Kam Lam will check ODU TTP G.875 definitions (G.875 v4.07 which is in AAP Last Call for approval as v5)
30 minsBulk RetrievalAndrea Mazzini

Andrea Mazzini presents otcc2020.AM.002_TAPI_2.1.3_Enhancements.pptx  (last slide) with a proposal to add a set of operations for the creation of inventory files, to be transferred by FTP, considered more efficient wrt REST / RESTCONF / HTTP.

Proposal is rejected, because the issue is not related to TAPI, the solution is too much protocol dependent.

Arturo Mayoral, we could find a proper protocol extension to solve the problem.

Karthik Sethuraman states that REST is widely implemented, the issue should have already been considered.

Also considered that Streaming should provide the best solution.

15 mins

Preparation of May virtual meeting agenda

All

Precondition for discussion are use cases, specially for the more advanced features.

  • 2.1.4 – ODU OAM
  • Multi-Layer Capabilities / Node Rule Group
  • TAPI Release Plan, alignment with Core IM Release Plan (e.g. IETF alignment for topology)
  • Candidate features:
    • Connectivity Service Computation Services, reuse orphan connection etc.
    • Build the Contexts
      • Maybe based on same “resources”
      • Slicing features
      • Recursive
    • Control Model
    • Spec Model