2024-01-25 API backlog minutes
- Jose Ordonez-Lucena
Attendees
Organization | Delegates |
|---|---|
AT&T | Pierre Close |
CableLabs | Randy Levensalor |
Charter Communications | Chris Aubut, Justin Pace, Jason Page |
Deutsche Telekom | Noel Wirzius |
Ericsson | Jan Friman |
Infosys | Chintan Lodariya |
Huawei | Zhang Kai |
Nokia | Tanja De Groot |
Telecom Italia | Fabrizio Moggio |
Telefónica | Jose Ordonez-Lucena, Jorge García Hospital |
Vodafone | Eric Murray, Kevin Smith |
Agenda Proposal
Approval of minutes of last conf. call
Recent Updates & Recap
Review of Action Points
Discussion
OGW Drop 3 APIs: 336, 359, 375, 376
Other APIs: 351, 372, 378
Governance: 367
Action Points
AOB
Q&A
Antitrust Policy
The project's Antitrust Policy, which you can find linked from the LF and project websites. The policy is important where multiple companies, including potential industry competitors, are participating in meetings. Please review and if you have any questions, please contact your company legal counsel. Members of the LF may contact Andrew Updegrove at the firm Gesmer Updegrove LLP, which provides legal counsel to the LF. |
 |
New Procedures in API Backlog WG meetings
A number of improvements are under discussion with leadership team of OGW project (Henry), CAMARA Project (Markus), Product Definition WS (Helene) and TSC (Herbert). As of today, the WG adopted agreements are three:
To close the agenda SEVEN DAYS BEFORE the conf. call.
In case a WG participant wants to include a point in the agenda (e.g., present a new API proposal), this participant shall ensure the corresponding issue is opened in Github by then.
Exceptional situations will be treated separately.
New schedule of conf. calls
2nd Thursday of the month (10-11 CET)
4th Thursday of the month (15-16 CET)
Send agenda to TSC mail list, to encourage more TSC member companies to join the call and provide comments when they identify APIs which are of interest for them.
Meeting Minutes within Wiki instead of Github
CAMARA community agreed that meeting minutes would only be recorded in the wiki
Approval of minutes of last conf. call
Minutes of last API backlog WG call available here
DECISION: The minutes are approved.
Recent Updates & Recap
Technical Steering Committee (TSC)
Last TSC call held on Jan 18th. Minutes available here.
"Device Location retrieval API proposal" was approved
ongoing in Device Location repo → issue 343 is closed
"Network Slicing API proposal" was approved
TSC noted that the proposed sub-project name "on-demand network slicing" was not appropriate. They asked backlog WG to decide on a new sub-project name.
Two options for the sub-project name: 1) Network Slicing Booking; 2) Network Slicing Reservation.
Huawei has commented their preference to option 1.
Backlog table
Table updated in PR#382
Review of Action Points
AP | Owner | Description | Issue | Due Date | Status |
|---|---|---|---|---|---|
20240111-04 | Telefónica | Open a new PR to update governing document for API submission pipeline | 2024/02/15 | Open | |
20240111-03 | WG operators | Post position on what the scope (mobile-only or mobile+fixed) of "Call Forwarding" API should be | 2024/01/24 | Not pursued | |
20240111-02 | China Unicom, Orange | Submit PRs for their companies to become supporters of the Call Forwarding API | 2024/01/24 | Closed | |
20240111-01 | China Unicom | Update the API template on Network Slicing, clarifying the issues covered in the deck and questions covered in the call. | 2024/01/12 | Closed |
Discussion
Current Issues
Issue | Owner | Description | Discussion |
|---|---|---|---|
China Unicom | New Proposal: Network Slicing API
|
DECISION: "Network Slice Booking" is the sub-project name. ACTION: WG chair to inform TSC on the decision, so that CAMARA admin can proceed with the repo creation. The issue is not eligible to be closed yet. | |
China Unicom | New API proposal: Device Visit Location | The issue was not treated in this conf. call. The issue is not eligible to be closed yet. | |
Telefónica | New API proposal: OGW Home Location Verification |
The issue is not eligible to be closed yet. | |
Centillion | New Proposal for Authorization for Advertisements, Advertisements Consent, and Measurement | No delegate from Centillion attended. The issue was not treated in this conf. call. The issue is not eligible to be closed yet. | |
Telecom Italia | New API proposal: Call Forwarding Signal |
DECISION: API proposal is WG endorsed. The proposed Sub-Project name is Call Forwarding Signal. ACTION: to send out information to TSC, asking for API approval. ACTION: to seek codeowners/maintainers from Orange and China Unicom. The issue is not eligible to be closed yet. | |
Governance | Adapt Project StructuresAndRoles.MD to changes in API backlog table (reduction of comments) | The issue was not treated in this conference call. No progress. The issue is not eligible to be closed yet. | |
| New Proposal: Receive SMS | The issue was not treated in this conference call.
The issue is not eligible to be closed yet. |
Closed Issues
New Issues
Issue | Owner | Description | Discussion |
|---|---|---|---|
Deutsche Telekom | Device Quality Indicator |
ACTION: to improve and clarify the API proposal, based on discussion during the call. The issue is not eligible to be closed yet. | |
Deutsche Telekom | Best Interconnection |
ACTION: to improve and clarify the API proposal, based on discussion during the call. The issue is not eligible to be closed yet. | |
Charter Communications | CPE management | Charter Communications presented a slide deck to elaborate on API proposal. There was no time to really discuss the topic, since we ran out of time . We will resume the discussion next call. ACTION: to submit the deck here, and link it to the issue. The issue is not eligible to be closed yet. |
Action Points
AP | Owner | Description | Issue | Due Date | Status |
|---|---|---|---|---|---|
20230125-06 | Charter Communications | o submit the deck here, and link it to the issue. | 2024/02/01 | Open | |
20230125-05 | Deutsche Telekom | to improve and clarify the API proposal, based on discussion during the call. | 2024/02/01 | Open | |
20230125-04 | Deutsche Telekom | to improve and clarify the API proposal, based on discussion during the call. | 2024/02/01 | Open | |
20230125-03 | Telecom Italia | to seek codeowners/maintainers from Orange and China Unicom. | 2024/02/07 | Open | |
20230125-02 | Telefónica | To send out information to TSC, asking for API approval. | 2024/01/25 | Open | |
20230125-01 | Telefónica | To inform TSC on the decision of Sub-Project name, so that CAMARA admin can proceed with the repo creation | 2024/01/25 | Open |
Decision Points
AoB
Next conf. call: 8th February, 10-11 CET.
Q&A
How does CAMARA API pipeline work?
The pipeline consists of FOUR stages:
A. Submission of the API proposal.
B. Evaluation of the API proposal.
C. API proposal voting & decision.
D. Sub-Project setup.
The following clauses provides details on individual stages.
Stage A: Submission of the API proposal
Participants: API owner.
Description: The proccess is detailed here. To proceed with the submission, the API owner shall follow these steps:
Fill in the template available here and save it with the following name: "APIproposal_<APIname>_<owner>. md" locally.
Create a new issue in the API Backlog Working Group repository, labeled with "API Backlog".
Upload the filled-in template to GitHub repository folder for API proposals via Pull Request. This Pull Request shall be associated to the issue created in the previous step.
Stage B: Evaluation of the API proposal
Participants: API owner, API backlog WG.
Description: The proccess is detailed here. Upon submission, the API owner will present the proposal in the next API backlog WG meeting, to socialize it with the rest of partners. In paralell..
The WG chair checks that the template is duly filled in. Otherwise, the API owner is requested to provide missing information.
After this sanity check, each WG participant declares their support. If a company wants to become supporter of an API, then a delegate of this company needs to add the company's name in the 'supporters' column in the API backlog table. The more support an API proposal gets, the better (it may get more traction).
When the API owner considers the API proposal is in good shape to go for approval, it informs the WG chair accordingly.
Upon receiving this information, the WG chair merges the Pull Request into the main branch, and sends the API proposal to the Technical Steering Committee (TSC) of CAMARA. This action shall be completed at least one week prior to the TSC meeting where the API proposal will be voted upon.
The whole procedure (steps 1-4) should be done within 2 regular meetings of the API Backlog WG. Nonetheless, it is up to the API owner to decide if it wants to shorten or extend this time period.
Stage C: API proposal & voting decision
Participants: TSC.
Description: The proccess is detailed here. Upon receiving the API proposal and notification from the API backlog WG chair, the TSC studies the proosal and votes it at the next TSC meeting.
NOTE 1: Possible decisions outcomes:
Not Accepted: The API proposal is rejected, and thus will not be included in any API Sub-Project. The TSC will need to inform the API backlog WG of this decision, and clarify next steps: either (1) remove this API proposal from backlog, with objecting companies providing justifications why; or (2) ask for changes (e.g., clarifications, corrections, gaps to be addressed) required in order for the API to be re-submitted by the API supporters.
Accepted: In this case, the TSC shall specify whether the API proposal is to be hosted by a new or existing Sub Project.
NOTE 2: The TSC may also propose changes to an API proposal and take the decision considering these changes. The TSC documents the decision in the CAMARA API overview list (fills in columns TSC date and TSC decision / Sub Project; in case of a No-Go "Rejected" is documented there).
Stage D: Sub-Project setup
Participants: API backlog WG, TSC, CAMARA admin team
Description: If an API proposal is accepted and there is a neeed to open a new Sub-Project, the following steps are needed:
Supporting companies propose their initial maintainers to be added for the Sub-Project. The API backlog WG chair centralizes this information, and sends it to the TSC.
The TSC will use this input to oficially nominate the initial maintainers by next TSC meeting.
The CAMARA admin team creates the Sub-Project repository.
NOTE: After the initial maintainers are nominated, the criteria for further maintainers would be three months of active contribution to the sub project. Code owners are to be decided by the maintainers within the subproject.