You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is to inform the API Backlog Working Group about the scope change which we discussed and decided within QualityOnDemand sub project. The ask to the API Backlog group is to take notice and to communicate the change towards the Open Gateway Product team.
The change:
There was a statement within the scope "The scope of this API family should be limited (at least at a first stage) to 4G and 5G". We have removed this restriction based on the discussion in camaraproject/QualityOnDemand#238 and with the changes to the README.md in https://github.com/camaraproject/QualityOnDemand/pull/255/files. It now states that the service API provides customer the ability to "set quality for access network connections", instead of "set quality for a mobile connection".
The main arguments:
The API is already formulated in an access agnostic way
With v0.9.0 we introduced the concept of QoS Profiles which allow to define and use network specific profiles with the QoD API
The API was implemented by CableLabs in their lab across DOCSIS, PON and 5G networks from the same API endpoint.
The functional scope of CAMARA includes telco mobile networks and telco fixed line networks - we didn't want to exclude contributors from the sub project due to a scope limitation
Note 1: that the API can potentially be used also beyond mobile networks does not mean that any network operator is obliged to offer the service beyond their mobile network. Indeed, for networks, which don't have a shared medium and no other capacity bottlenecks the Service API might provide no benefit for customers.
Note 2: As QoD was one of the APIs already there before the API Backlog process was in place there is no API Proposal form which can be changed due to this issue.
The text was updated successfully, but these errors were encountered:
@hdamker thanks for adding this. This is an important addition to allow for intent based APIs to set QoD across all networks. We've made several changes to the API to accommodate wireline networks and enable operations to define available qos profiles.
This issue is to inform the API Backlog Working Group about the scope change which we discussed and decided within QualityOnDemand sub project. The ask to the API Backlog group is to take notice and to communicate the change towards the Open Gateway Product team.
The change:
There was a statement within the scope "The scope of this API family should be limited (at least at a first stage) to 4G and 5G". We have removed this restriction based on the discussion in camaraproject/QualityOnDemand#238 and with the changes to the README.md in https://github.com/camaraproject/QualityOnDemand/pull/255/files. It now states that the service API provides customer the ability to "set quality for access network connections", instead of "set quality for a mobile connection".
The main arguments:
Note 1: that the API can potentially be used also beyond mobile networks does not mean that any network operator is obliged to offer the service beyond their mobile network. Indeed, for networks, which don't have a shared medium and no other capacity bottlenecks the Service API might provide no benefit for customers.
Note 2: As QoD was one of the APIs already there before the API Backlog process was in place there is no API Proposal form which can be changed due to this issue.
The text was updated successfully, but these errors were encountered: