Connectivity enhancements to support requesting a bundled intent of multiple outcomes (Connections) in case of declarative model of operations (where TAPI client performs path computation and resource allocation)
Andrea Mazzini : Is it correct to say that ConnectivityServices are MC Assembly level and not at the MC component level?
CSEPs already support hierarchy/recursive associations
Karthik Sethuraman : Would it be conceptually backward compatible if we call the Yellow boxes "ConnectivityService" and the orange box as "ConnectivityServiceEnvelope" ?
Andrea Mazzini : We don't create ConnectivityService for individual MCs and only use ConectivityService to ask for MCAs.
Stephane St-Laurent : TAPI does explicitly restrict this approach - could use CS for requesting either MC or MCA
Nigel Davis : Approach seems reasonable as this can be applied recursively across controller hierarchies
Arturo Mayoral : We should avoid substantial deviation from the previous Connectivity models
Hing-Kam Lam Will need to study the use cases to evaluate the need for additional CS "envelope"