Karthik Sethuraman
Karthik Sethuraman
I guess this relates to an class/grouping having attributes that are input only, output only and both input/output
Yes, that's correct - for TAPI 2.2, the attribute `tapi-topology:node/tapi-topology:aggregated-node-edge-point` will remain, but it is expected that it follows the intent of its parent UML association: _NodeAggregatesNEPExposedByEncapsulatedTopology_ as shown in...
All, Apologize for any misinformation from past discussions. The current implementation is consitent as per the containment hierarchy that was discussed/agreed by the TAPI design team during the TAPI IM...
Related Issue #132
This issue will be tracked as part of #151 discussion
It would be easier t understand/discuss your questions by drafting an RI network database for the scenario you are describing.
TAPI Call April 17, 2018 Notes: https://wiki.opennetworking.org/display/OTCC/2018-04-17+TAPI+Meeting+Notes ETHG (group of VLAN IDs) is used for OAM purposes where only a single VLAN is monitored https://wiki.opennetworking.org/download/attachments/317620231/image2018-4-17%2010%3A38%3A8.png?version=1&modificationDate=1523975890888&api=v2 All VLANs in ETHG has...
This issue will be tracked as part of #131 discussion
Related Issue #115
Let us keep this open until we resolve #115 . Either way, the behavior between RPC and SCRUD flavors of RESTConf mapping should be consistent.