2024-01-11 API Backlog minutes

Attendees

Organization	Delegates

Organization	Delegates
China Unicom	Yan Fang
China Telecom	Dan Xu
Deutsche Telekom	Noel Wirzius
Ericsson	Jan Friman
GSMA	Mark Cornall
Huawei	Zhang Kai, Shuting Qing
Infosys	Chintan Lodariya
KDDI	Toshi Wakayama
Orange	Ludovic Robert
Telecom Italia	Fabrizio Moggio
Telefónica	Jose Ordonez-Lucena, Jorge García Hospital
Vodafone	Eric Murray, Kevin Smith

Agenda Proposal

Antitrust Policy
Recent Updates & Recap
Review of Action Points
Discussion
- OGW Drop 3 APIs: 336, 343, 359
- Other APIs: 317, 351
- 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

Recent Updates & Recap

Minutes of last API backlog WG call available here
Last TSC call held on Dec 21st. Minutes available here. Key takeaways:
- Population Density Data (replaces "Dynamic People Density Information") API proposal was approved, after backlog WG took required action.
- Short Message Service (replaces "Send SMS") API proposal was approved, after backlog WG took required action.
- Decision about names & maintainer lists for already approved sub projects will be taken in lazy consensus if there there are no objections or additional nominations on the TSC mailing list within 48 hours.
New repos:
- RegionUserCount Sub-Project is up and running → issue 328 is closed
- PopulationDensityData Sub-Project is up and running → issue 334 is closed
- ShortMessageService Sub-Project is up and running -> issue 352 is closed

Review of Action Points

AP	Owner	Description	Issue	Due Date	Status

AP

Owner

Description

Issue

Due Date

Status

20231214-01

Orange

Address received comments on Device Location Retrieval in in PR#366

343

2024/01/10

Closed

Discussion

Current Issues

Issue	Owner	Description	Discussion

Issue	Owner	Description	Discussion
317	China Unicom	New Proposal: Network Slicing API The API template is available in PR#333	Progress offline in the PR thread since last conf. call. Huawei presented a deck (c.f. slides 11-14) shedding light on the open questions raised by delegates with regards to: API definition (input/output params) differences with other existing APIs (QoD and SiteToCloudVPN) naming and other issues raised by Ericsson and Vodafone Further questions were raised calling for clarifications on how API logic on other scenarios (access control, user provisioning and resource guarantees). Huawei clarified them. No further concerns from audience. API owner asked the WG to endorse the API proposal. No objections were raised, but API owner was asked to update the API template before sending it out to the TSC. GSMA (Mark Cornall) also noted that the API definition should align with current GSMA OPG/OPAG activities. ACTION: China Unicom to update the API template, clarifying the issues covered in the deck and questions covered in the call. DECISION: The WG endorses the API proposal. It will be taken for approval to next TSC meeting (18th January). The issue is not eligible to be closed yet.
330	China Unicom	New API proposal: Device Visit Location The API template is available in PR#329	The issue was not treated in this conf. call. Awaiting for GSMA-TSC mails, with global privacy group of Open Gateway involved as well. For further details in background and next steps see issue thread. The issue is not eligible to be closed yet.
336	Telefónica	New API proposal: OGW Home Location Verification The API template is available in PR#337. Input from OGW Drop 3	No progress since last conf. call. Telefónica has not yet taken action. For further details in next steps, see issue thread. The issue is not eligible to be closed yet.
343	Orange	New API proposal: Device Location Retrieval The API template is available in PR#3 66. Input from OGW Drop 3	Orange updated the API template, according to the comments received in last conf. call. Further clarity on the new feature proposed for inclusion in the Device Location family. AP 20231214-01 is closed. Ludovic asked the WG to endorse the API proposal. No objections were raised. DECISION: The WG endorses the API proposal. It will be taken for agreement to next TSC meeting (18th January). The issue is eligible to be closed.
351	Centillion	New Proposal for Authorization for Advertisements, Advertisements Consent, and Measurement The API template is available in PR#350.	No delegate from Centillion attended. The issue was not treated in this conf. call.
359	Telecom Italia	New API proposal: Call Forwarding Signal The API template is available in PR#361. Input from OGW Drop 3	Progress offline in the PR thread since last conf. call. API supporters: the API needs a supporting company other than TIM (owner). China Mobile has confirmed its willingness to become supporter, but they are still pending to officialise it. To that end, a delegate from China Mobile should submit a PR against the backlog table, by adding the company name in the column "Supporters in API Backlog Working Group" for this API. Ludovic noted that Orange would officialise support next week. ACTION: China Mobile and Orange to submit PRs for their companies to become supporters of the API. API scope: The scope (mobile-only or mobile+fixed) needs to be agreed for this API. While we have quorum on the need for mobile domain to be included in the scope of the original API, there is no consensus on the fixed domain. WG chairman recommendation is to follow a pragmatic way, starting with a very concrete market-empowered use case (and thus a narrower scope), and grow from that point over time. API owner agreed. Fabrizio suggested focusing on the expected biggest market opportunity around mobile lines, leaving landlines for a second version of the API. The rest of operator companies did not express their positions. KPN, who reported in the issue thread that the API should cover both mobile and fixed domains, could not attend the conf. call, so the scope cannot be closed yet. ACTION: Operator companies are invited to post their position, to reach offline consensus on API scope. The API proposal is not ready for WG endorsement. The issue is not eligible to be closed yet.

Closed Issues

Issue	Owner	Description	Discussion

Issue	Owner	Description	Discussion
328	China Unicom	New Proposal: Region User Count The API template is merged, available here Input from OGW Drop 3	Sub-Project is up and running
334	China Unicom	New API proposal: Device Visit Location The API template is merged, available here Input from OGW Drop 3	Sub-Project is up and running
352	Telefónica	New API proposal: OGW Home Location Verification The API template is merged, available here Input from OGW Drop 3	Sub-Project is up and running

New Issues

Issue	Owner	Description	Discussion

Issue

Owner

Description

Discussion

367

Governance

Adapt Project StructuresAndRoles.MD to changes in API backlog table (reduction of comments)
The aim is to update the governing document to reflect on the updated changes on API submission pipeline, according to the new structure of the API backlog table.

The issue was not treated in this conference call.

ACTION: Jose (Telefónica) to open a new PR to address this issue.

372

New Proposal: Receive SMS
No PR available.

The issue was not treated in this conference call.

Action Points

AP	Owner	Description	Issue	Due Date	Status

AP	Owner	Description	Issue	Due Date	Status
20240111-04	Telefónica	Open a new PR to update governing document for API submission pipeline	367	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	359	2024/01/24	Open
20240111-02	China Unicom, Orange	Submit PRs for their companies to become supporters of the Call Forwarding API	359	2024/01/24	Open
20240111-01	China Unicom	Update the API template on Network Slicing, clarifying the issues covered in the deck and questions covered in the call.	3 17	2024/01/12	Open

AoB

Next conf. call: 25th January, 15-16 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.