Versions Compared

Key

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

Date

14 November 2017

Attendees

Goals

  • Administrative
    • Review agenda and next call plan
    • CORD-Build/ONF Interim Meeting Update
    • Liaisons
  • MEF Feedback on TAPI
    • Bidirectional navigability for associations
    • Topology-Node encapsulation, Link containment & NEP containment/aggregation?
  • TAPI 2.0 SDK Model
    • LayerProtocol Refactoring & Spec pattern
      • Merging of LayerProtocol attributes into NEP, CEP, CSEP & SIP
      • Constraining of Layer multiplicity to 1 for NEP, CEP, CSEP
      • Spec pattern usage & Spec Constraints
    • CEP-Has-Server-NEPs relationship & CEP containment
    • Eagle Uml2Yang Tool update on Literals/Constants naming
  • Tapi 2.0 SDK Technology Model
    • ETH Spec Model
    • OTSi Spec Model
    • ODU Spec Model
  • TAPI 2.0 Documentation & Use Cases
    • Multi-layer, Multi-domain Connectivity
    • Resiliency, Protection & Restoration
    • OAM, Performance and Monitoring
    • Termination Model (SIP, SEP, NEP, CEP)

Discussion Items

TimeItemWhoNotes
5minsGeneral AdministrativeTo-be-removed
  • This call is being recorded
  • Next TAPI call: Next week, Nov 21, 2017
30mins

CORD-Build/ONF Interim Meeting Update

Lyndon Ong
30mins

MEF Feedback on TAPI

  • Bidirectional navigable associations
  • Others

Andrea Mazzini,

Nigel Davis

  • Andrea to followup with MEF on the status of the official liaison
  • in general objections from almost all TAPI participants to incorporating bidirectional navigability for all associations in an "interface" oriented model
  • Recommendation to escalate bidirectional navigability issue to OTCC TST
15mins

LayerProtocol Refactoring & Spec pattern

  • Merging of LayerProtocol attributes into NEP, CEP, CSEP & SIP
  • Constraining of Layer multiplicity to 1 for NEP, CEP, CSEP
  • Spec pattern usage & Spec Constraints
To-be-removed
  • Agreed to merge LayerProtocol attributes into NEP/CEP/CSEP/SIP - this results in elimination of LayerProtocol class in TAPI
  • Agreed to Constrain Layer multiplicity to 1 for NEP, CEP
  • Agreed that introducing constraints that limits the application of <Specify> (augment) relationship is good practice
  • Rod Lu: CSEP should be multi-layer to allow for specifying/configuring lower (transport/tunnel/internal) layer adaptation properties while creating a upper layer connectivity. Example to be provided in next TAPI call
10minsEagle Uml2Yang Tool update on Literals/Constants namingBernd ZeunerAgreed to update TAPI SDK with the output of the latest Eagle Uml2Yang tool
15mins

CEP-Has-Server-NEPs relationship & CEP containment

Nigel Davis 

Old Action Items

  •  All: Consider what needs to be covered in the TAPI portion of the interim face to face meeting
  •  All: Propose approach to demonstrating TAPI at CORD Build event
  •  Nigel Davis: Validate with David that we do have two booths at the CORD Build Science Fair 
  •  All: Review the FRD by 24 Oct 2017
  •  Karthik Sethuraman: add slot to TAPI calls to cover FRD.
  •  All: location to post recording that is accessible to China - maybe mirror
  •  Karthik, Lyndon: update draft FRD example for Friday liaison to OIF
  •  Lyndon: check with Guru on availability for TAPI review
  •  Lyndon: Get David to change agenda title for morning CORD session
  •  All: continue to review FRD
  •  Nigel, Karthik, Lyndon and anyone else interested: continue to work on CORD Build slide pack and Science Fair
  •  Nigel: host meeting next week (Karthik may be on plane, Lyndon in Shanghai)

New Action Items

  •  Andrea & Nigel to work on response to MEF Liaison
  •  Rod to present an example for multi-layer CSEP
  •  Karthik to update the TAPI SDK using the latest version of the Uml2Yang tool