Attendees & Representation
...
Representative | Organization | Role | |
---|---|---|---|
Herbert Damker | Deutsche Telekom AG | TSC Chair, Active Maintainer | x |
Shilpa Padgaonkar | Deutsche Telekom AG | Active Maintainer | X |
Jan Friman | Ericsson | Active Maintainer | X |
Toshi (Toshiyasu) Wakayama | KDDI | Active Maintainer | X |
Ludovic Robert | Orange | TSC Deputy Chair, Active Maintainer | X |
Adnan Saleem | Radisys | EUC Representative | x |
Doug Makishima | Summit Tech | EUC Representative | X |
Diego González Martínez | Telefonica | Active Maintainer | X |
Jose Luis Urien | Telefónica | Active Maintainer | X |
Mahesh Chapalamadugu | Verizon | EUC Representative | X |
Eric Murray | Vodafone | TSC Deputy Chair | x |
Kevin Smith | Vodafone | Active Maintainer | x |
Chris Howell | Vonage | Active Maintainer | |
George Glass | TM Forum | TM Form Representative | |
Henry Calvert | GSMA | GSMA Representative | x |
...
- API proposal "Device Location Retrieval" - see message https://lists.camaraproject.org/g/tsc/message/105
- Initial version of the YAML already available within the sub project "Device Location"
- Hence just a formal approval required
- #Approved
- API proposal "Network Slicing" - see message https://lists.camaraproject.org/g/tsc/message/104
- Application proposal: APIproposal_NetworkSlicing_ChinaUnicom.md
- Discussion within related issue: https://github.com/camaraproject/WorkingGroups/issues/317
- Supporting presentation in PPT
- Endorsed by API Backlog WG Jan 11th, see meeting minutes
- Jan raised a question about the name of the API as it more about ordering/reservation than Network Slicing itself.
- Discussion about use of "on-demand" label - rationale for this?
- Kai Zhang: on-Demand because the customer will dynamically reserve the slice
- The API could have the reservation name (and it will be decided by the project later) but what's about the project name? Herbert: what about Network Slicing ... on-Demand ? Booking ? Reservation?
- Discussion about project granularity: Reservation but then does device attachment should be managed in same project? Herbert explained that we targeted 'small' project in term of APIs managed (to be flexible for CAMARA meta release management) - It is possible to have several APIs but must be very close and released together.
- Ms. De Groot From a developer perspective, what do they want to call the sub-project? On Demand, or Network Slicing - The API needs to be explicit in the name
- Mr. Damker gave the final answer to end the discussion for now, the option for the team to come back at a later time to decide upon a name, or they can make the decision during the meeting (TSC 1/18) -
- Discussion about use of "on-demand" label - rationale for this?
- Approved
- Application proposal: APIproposal_NetworkSlicing_ChinaUnicom.md
Commonalities
- Initial input info by Shilpa
- Target date for release 0.3.0 is to be ready for approval on 05.02.2024
- Linting ruleset and guidelines PRs are currently under review. We need to close this review soon.
- API Testing guideline doc has 1 open point left. After this discussion is resolved, PR can be merged.
- Security-scheme and scope update in design guidelines document and reference to document in ICM are also currently in review.
- Other release 0.3.0 specific PRs are minor documentation changes.
- Mr. Damker asked when the team is planning on a certain release?
- ACTION: Former user (Deleted) will get a more defined date for the next release
- Mr. Damker asked when the team is planning on a certain release?
...