onvif
Updated entry point for device service over Uplink
Ref: https://github.com/onvif/wg_profile_cloud/issues/9
Entry point for device service needs to have HTTPS url scheme to access device over Uplink and the PR updates core spec to clarify such requirement.
Note
- Since Core spec never refers to other service specs, Uplink spec reference is NOT included in list of references
Should we use a different term for Uplink but convey same meaning like 'access device over reverse tunnel'? Suggestions welcome.
only local paths are used
Not sure if I get your comment fully, as I understand the scheme + "onvif/device_service" is what's standardized while the "onvif_host" in the entry point syntax is left to implementation? so in that sense mentioning about local paths could be hard to harmonise?
only local paths are used
Not sure if I get your comment fully, as I understand the scheme + "onvif/device_service" is what's standardized while the "onvif_host" in the entry point syntax is left to implementation? so in that sense mentioning about local paths could be hard to harmonise?
I agree with @HansBusch. Since it’s HTTP/2, the full URL with http or https is not relevant. Only the path “/onvif/device_service” is important.
only local paths are used
Not sure if I get your comment fully, as I understand the scheme + "onvif/device_service" is what's standardized while the "onvif_host" in the entry point syntax is left to implementation? so in that sense mentioning about local paths could be hard to harmonise?
I agree with @HansBusch. Since it’s HTTP/2, the full URL with http or https is not relevant. Only the path “/onvif/device_service” is important.
I think there is a conceptual mistake here. While it is true that with uplink we must use encryption, the URI used to connect to the cloud is not the entry point of of any service. It's just one end of a reverse proxy. Eventually the tunnel is reverted and commands are sent towards the other direction.
Therefore, for me this PR should be rejected.
10/24 VEWG Telco
- Agreed to remove the transport + "onvif_host" for defining onvif entry point
@HansBusch You have a change requested for this PR. Is it still required?
