Versions Compared

Key

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

Date

21 November 2017

Attendees

Goals

    • Administrative
    • TAPI 2.0 SDK Review
      • LayerProtocol Refactoring
        • Constraining of Layer multiplicity to 1 for NEP, CEP, CSEP
      • Eagle Uml2Yang Tool update
        • Enum/Literals/Constants mapping
        • <ExtendedComposite> mapping
      • ODU Spec Model
        • Channelization info in connectivity request
      • ETH Spec Model
      • OTSi Spec Model
    • TAPI 2.0 Documentation
      • Termination Model (SIP, SEP, NEP, CEP)
        • Multilayer switching
        • Multi-stage multiplexing
        • Fixed mapping case
        • Inverse multiplexing case
        • Asymmetric connectivity case
      • Multi-layer, Multi-domain Connectivity
      • Resiliency, Protection & Restoration
      • OAM, Performance and Monitoring

Discussion Items

TimeItemWhoNotes
5minsGeneral AdministrativeTo-be-removed
  • This call is being recorded
  • Next TAPI call: Next week, Nov 28, 2017
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
Rod LU
  • 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
  • Enum/Literals/Constants mapping
  • <ExtendedComposite> mapping
To-be-removed Bernd Zeuner 
30minsTermination Model (SIP, SEP, NEP, CEP)
  • Multilayer switching
  • Multi-stage multiplexing
  • Fixed mapping case
  • Inverse multiplexing case
  • Asymmetric connectivity case
To-be-removed 
15minsCEP-Has-Server-NEPs relationship & CEP containmentNigel Davis 
45mins

Multi-layer, Multi-domain Connectivity

Lyndon Ong 

Old 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

New Action Items

  •