Time | Item | Who | Notes |
---|
5mins | General Administrative | To-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
|
10mins | Eagle Uml2Yang Tool update- Enum/Literals/Constants mapping
- <ExtendedComposite> mapping
| To-be-removed Bernd Zeuner | |
30mins | Termination Model (SIP, SEP, NEP, CEP)- Multilayer switching
- Multi-stage multiplexing
- Fixed mapping case
- Inverse multiplexing case
- Asymmetric connectivity case
| To-be-removed | |
15mins | CEP-Has-Server-NEPs relationship & CEP containment | Nigel Davis | |
45mins | Multi-layer, Multi-domain Connectivity | Lyndon Ong | |