Proposal - Runtime Restrictions API

[gmuratk]

Problem description
There is currently no mechanism for API Producers (e.g. Operator) to communicate which optional capabilities/features/parameters are supported and enabled to API Consumers!

Possible evolution
A programmatic approach that is generic enough to describe Runtime restrictions imposed by an API Producer and exchange capabilities enabled based on end-user, network location/status, etc.

Alternative solution
There has been discussion around use of well-known URL.

Additional context
Some of the recorded (open and closed) Issues that will potentially benefit from such a solution:
camaraproject/Governance#141
camaraproject/IdentityAndConsentManagement#57
camaraproject/DeviceStatus#46
camaraproject/SimSwap#58
camaraproject/QualityOnDemand#173

[gmuratk]

Just to add a note, I realize this is a proposal for an API, and there will be a separate submission to API Backlog WG. However, I think it is a fairly general topic that will benefit the project/community at large so Commonalities group should review and comment.

[nickvenezia]

This would be in addition to ad tech Propsal submission. I believe QOD refers to it also.

[rartych]

The slide deck was uploaded CAMARA Wiki.
I propose to convert this issue to discussion.