Scope
PS notes
Deployment phases:
Device/Service association
Device/Application association
Establishing session
Honestly, I'm getting the impression that it's a bit like the discussed network protocol analysis. It's being done behind the scenes by the Azure's black box. All we have is SDK which handles establishing the secure communication channel and then with the other thing we have which is either SAS/X.509 which provides:
- Identity of the device
- Authorization for specified resources
So unless there's a greater scheme behind these I missed it'd all be just "Establishing connection context". Unless you mean mixed flow of Azure configuration interweaved with actual device in runtime?
Establishing a semantic-context
We are not directly establishing semantic context, the message properties are mapped after they surface from IoT Hub to IoT Central (if such template is assigned) somewhere in the cloud. From the device perspective, its identity is the context. Also, it is under the "Establishing session" part but semantic context is defined before the session starts being established... assuming session means active connection here.
Security management - establishing security-context
Authentication
Aren't these the same thing in this IoT Hub's context?
Originally posted by @Drutol in #7 (comment)