Clarification on the control model needed by ITU-T Q14/15
- Clarification from the 2020.12.10 discussion on ExposureContext (EC), ConstriantDomain (CD), ControlConstruct (CC), ControlPort (CP)
- The relationship among EC, CP, and CD:
- The client talks to EC through CP about CD.
- EC: The "How". The gateway/agent for accessing. It defines the rule/requirement of accessing.
- CD: The "What". The thing to be viewed by the client in the CPI (control plane interface)
- CC/CP: The "Where". The interface port to access the CE.
- In the current v1.4 UML, the ControlConstructExposesExposureContext association should be ControlConstructAccessesExposureContext
- One Vmf can provide multiple views from the same set of resource.
- An ExposureContext can only expose one highest level (most outer) ConstraintDomain,
- Additional clarification on 2021.01.21

- The model allows access to multiple ExposureContext from a single ControlPort. For example, to support multiple users/applications at the same CPI (control plane interface) ControlPort.
- Consideration of multiple ControlPort vs multiple ExposureContext
- High-level security control and coarse grain operation control are set at the ControlPort.
- Additional ControlPort instances could be instantiated to meet different security requirements or operation previlage.
- Fine grain control (e.g., at object/attribute level) are set at the ExposureContext
- Additional clarification for TR-512.8 is needed.
- Lifecycle of EC and its dependency on CD
- Additional associations
- Multiplicity
- Start up bootstrap:
- CD representing the controller
- Then administrator create ....