Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New API Proposal - QoS Booking #155

Merged
merged 14 commits into from
Jan 16, 2025
Merged
Prev Previous commit
Next Next commit
Revert "Update APIproposal_QoS_Booking_KDDI. md"
This reverts commit fdd8fcb.
Masa8106 committed Dec 4, 2024
commit 9c7af0ba374969074c2626b98c8d3a90c3b53555
14 changes: 7 additions & 7 deletions documentation/API proposals/APIproposal_QoS_Booking_KDDI. md
Original file line number Diff line number Diff line change
@@ -1,12 +1,12 @@
| **Field** | Description |
| ---- | ----- |
| API family name | QoS Booking |
| API family owner | KDDI |
| API family name | Name of the API or API family |
| API family owner | Company submitting the API proposal. |
| API summary | High level description / scope of the API or API family, and two/three examples of in-scope business cases. |
| Technical viability | Identify the underlying network/cloud capabilities which are needed for the support of this API or API family, relating these capabilities them to standards maturity. <br><em>Example: this API requires the availability of NEF with this Rel-15 "X"feature</em>.
| Commercial viability | Specify the availability of commercial or (industrialized) open-source solutions for the identified network/cloud capabilities. <br><em> NOTE: If open-source, provide a publicly available reference/link to the actual solution, and specify the version under consideration.</em>|
| YAML code available? | YES |
| Validated in lab/productive environments? | NO |
| Validated with real customers? | NO |
| Validated with operators? | NO |
| Supporters in API Backlog Working Group | List of supporters. <br><em> NOTE: That shall be added by the Working Group.</em> |
| YAML code available? | YES / NO. |
| Validated in lab/productive environments? | YES / NO. <br>If YES, specify if it was lab network or productive network. |
| Validated with real customers? | YES / NO. <br>If YES, specify how many customers participated in the evaluation, and what their use cases were. <br><em>NOTE: It is not mandatory (though recommendable) to specify the name of the customers. </em> |
| Validated with operators? | YES / NO. <br> If YES, specify how many operators participated in the evaluation. <br><em>NOTE: It is not mandatory (though recommendable) to specify the name of the operators. </em> |
| Supporters in API Backlog Working Group | List of supporters. <br><em> NOTE: That shall be added by the Working Group. Supporting an API proposal means that the supporting company must provide at least 1 (one) Maintainer at the time of the Sub Project creation.</em> |