Attendees

Organization	Name
Orange
Charter Communications	@Christopher Aubut
CableLabs
Telefonica
Vodafone	@Kevin Smith @Eric Murray
Ericsson	@Jan Friman
AT&T	@Pierre Close
T-Mobile US
KDDI	@yusuke nakano
Slagen
Nokia
China Telecom
ZTE
KPN
GSMA	@Mark Cornall @reg cox
Centilion
Chunghwa Telecom
Deutsche Telekom
MTN
China Mobile	@Haojie Li @zhangruqian
Verizon

Agenda Proposal

Antitrust Policy
Approval of minutes of last conf. call
Recent Updates & Recap
Review of Action Points
Discussion
- OGW Drop #4 APIs: #35 (5G New Calling), #50 (Device Management), #63 (IMEI Fraud), #83 #85 #86 #87 (Model as a Service), #91 (Fixed lines in Device Location APIs), #93 (Line Eligibility for Carrier Billing API)
- Other APIs: #17 (Consent and Measurement), #23 (Carrier Wholesale Pricing), #24 (Steering of Roaming Information), #89 (IP High-throughput Elastic Network)
- Governance: #4 (Structures and roles, RACI, Maintainers initiative)
Closing Issues
- #20 (Best Interconnection), #22 (Capability and Runtime Restrictions), #18 (Receive SMS), #54 (Number Recycling), #70 (Quality by Design), #34 (Shutdown Service Status), #41 (Telco Scoring), #60 (Dedicated Networks), #66 (network Info), #68 (Consent URL)
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 LinusFoundation.

Antitrust Policy

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 **The meetings are to be held by Linux Foundation (Links available at GitHub and Confluence Backlog front pages)
- 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: Approve

Recent Updates & Recap

TSC meeting 03rd October:

Repository for DedicatedNetwork created (as decided last meeting), TelcoIndex naming still under discussion along supporters.
New API proposals brought to TSC (2):
- See informative message https://lists.camaraproject.org/g/tsc/message/230
- Scope Enhancement for Network info:
  - Supported by Vodafone and DT. Filled template: link. Original issue: 66.
  - Meant for including more information on current Device Status API, including Network Type (e.g.2/34G, 5GNSA/SA, non-3GPP..)
  - Decision: Not for decision, only informative as already agreed in both backlog and subproject. Already included into Device Status group scope, as agreed in issue 143 and PR 8.
- Consent URL API:
  - Supported by Telefonica and KPN. Filled template: link. Original issue: 68. Additional material: link
  - Meant for providing an out-of-band consent gathering mechanism that can be triggered in a separated moment (apart from API authentication phase) and in an arbitrary device (not only the API-targeted device), enhancing current mechanisms tied to Authcode or CIBA token flows.
    - Discussed with ICM work Group in particular to define the relationship between this API & ICM
  - Decision: (not to be treated as no all the affected participants can attend today)

Other topics

GSMA informed CAMARA Backlog that Open Gateway is considering certain Drop2/3/4 APIs that have been stuck in Backlog, “at risk”, due to lack of support. What this means is that GSMA is pushing our MNOs to actively reconsider within the next 2 weeks if they can support them. By raising it in the Backlog meeting we increase the chance to find enough support to “reactivate” progress.
- Best Interconnect

For clarity if any API is not a priority for OGW anymore at this point in time, we still expect they can progress independently in CAMARA.

(new) Sandbox proposal from TSC to speed-up the inclusion of new APIs into CAMARA, fostering the development of new APIs and the finalization of API scope definition.

https://github.com/camaraproject/Governance/pull/161

Backlog table

Table updated in PR#79 (unmerged) New backlog table with reduction of columns → All reviews are welcomed

Discussion

Current Issues

Issue #	Company	Summary	Status Update
17	Centillion	New Proposal for Authorization for Advertisements, Advertisements Consent, and Measurement The API template is available in PR#73.	Published new standards, Next meeting (this time) Nick will bring all the documentation and present everything putted together The issue is not eligible to be closed yet. Pending to provide a concrete API description into the API proposal template Action: Clarifying with interested parties whether this may be a possible API or a Framework etc. MEETING UPDATE: Not treated
4	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.	PR is uploaded: New APIbacklog.md by TEF-RicardoSerr · Pull Request #80 · camaraproject/APIBacklog (github.com) PR to be checked and confirmed before issue can be closed Action: Partners to review and validate MEETING UPDATE:
23	TelecomsXChange	New Proposal: Carrier Wholesale Pricing The API template is available in PR#77 First YAML available here	The issue was not treated in this conference call The issue is not eligible to be closed yet. ACTION: Backlog Governance to reach up TelecomXchange to see if the could connect next meetings MEETING UPDATE: Not treated
24	Netfocusin Technologies	New Proposal: Steering of Roaming Management The API template is available in PR#78	Does not seem to be in the Scope of Camara. Not an east-west (not between telcos) Already included in 3GPP as technical viable (provided in comment) The issue is not eligible to be closed yet. ACTION: Check for support/commitment from the partners (technical implementation approach important) Meeting Update: Not treated
35	China Mobile	5G New Calling The API template is available PR#31	Telefonica and Vodafone willing to see the presentation to check whether there is support for this To be treated in next session (still pending for providing extra info) Presentation of current proposal was shared in the meeting. Slides to be included in PR#31. @G. Murat Karabulut asked about the proposal been part of WebRTC enhancement or new API → new API. @Eric Murray asked about examples of 3rd parties in this API flow → app invoquing API to request or activate features, which can be enabled or not by the telco. @Mark Cornall raised the existance of a 5G New Calling project in GSMA: https://www.gsma.com/get-involved/gsma-foundry/5g-new-calling/ & 5GNCTF Meeting#1 ACTION: Operators open to comment/ask for clarification and support the API. MEETING UPDATE: @Eric Murray asks for user stories that can explain the behaviour of the proposed API, as not clear how this interacts with the proper 5G New Calling standard and how it solves the features that are proposed. AP for @Haojie Li
50	Verizon	Device Management The API template is available PR#30	The issue was not treated in this conference call The issue is not eligible to be closed yet. Action to contact Verizon to ensure participation in next backlog meeting API proposal presented by @Mahesh Chapalamadugu , clarified this proposal is targeted for IoT device management to activate/deactivate/manage the connection of those devices. ACTION:@Mahesh Chapalamadugu to upload current yaml for clarification in PR#30, and present again in next meeting. MEETING UPDATE: @Mahesh Chapalamadugu AP to upload documentation
63	MTN	New API proposal - IMEI Fraud The API template is available PR#64	This API was presented already and included in an existing group but no work was done so discontinued. Now Rebecca is presenting the proposal seeking for support DeviceCheck GSMA proposal overlaps this IMEI Fraud will offer more information to developers than GSMA Device Check service. MTN and other supporters should meet with GSMA to discuss if proceeding with this API within CAMARA still makes sense. Request for meeting already sent by GSMA to MTN Outcome of meeting awaited before deciding if this API proposal should proceed in CAMARA Pending to be confirmed by MTN, AP to be raised. @Eric Murray : (IMEI status) service related, but GSMA is ok for this proposal. ACTION: Pending from MTN for moving on with this API. Maybe to be included in the Device Identifier family. MEETING UPDATE: @reg no further information from MTN, consider to de-prioritize, pending to further update Any other operator open to take the lead of this API is welcomed
20	Deutsche Telekom	Best Interconnection The API template is available in PR#88 Input from OGW Drop 3	Seek for support ACTION: See if there is any overlap within EdgeCloud ACTION: Nick (centillion) to review with Noel (DT) about the match of use cases and consider support. DECISION API to be de-prioritised following de-prioritisation by OGW, but to remain in backlog. Issue to remain open. MEETING UPDATE: Not treated
83	China Mobile	Model As A Service Family The API template is available in PR#84 - MaaS (Model As A Service) Family	China Mobile presented the API ACTION: To include support from ZTE and Huawei. Proposals in good shape for been moved to TSC approval, @Haojie Li asked for one additional round for more clarifications and comments. MEETING UPDATE: @Haojie Li proposes to move to next TSC for approval → Agreed
85	China Mobile	Knowledge Base - Manage The API template is available in PR#84 - Knowledge Base - Manage	As per 83
86	China Mobile	Q&A Assistant - Manage The API template is available in PR#84 - Q&A Assistant - Manage	As per 83
87	China Mobile	Q&A Assistant - Service The API template is available in PR#84 - Q&A Assistant - Service	As per 83
89	China Mobile	IP High-throughput Elastic Network The API template is available in PR#90	Supporting document (presented) https://github.com/camaraproject/APIBacklog/raw/0a447dd4c53d0c675f8d72fc5622ff65eb48f7e3/documentation/SupportingDocuments/APIproposal_IP-high-throughput-elastic-network_ChinaMobile.pptx METING UPDATE: @Jan Friman asked about the relation of this proposal with current CAMARA’s APis dedicated to network config (QoD, slice booking…). @qiuhai explained that this proposal is focused on enabling new network technologies like Srv6 @Mark Cornall shared comments about the technology dependence on QoD solutions @Kevin Smith & @Jorge Garcia Hospital asked for more details on the difference with current proposals
91	Telefonica	Fixed Lines in Location The API template is available in PR#92	METING UPDATE: to be open in location group (no comments received)
93	Telefonica	Line Eligibility for Carrier Billing API The API template is available in PR#94	METING UPDATE: not treated

Closing Issues

Issue #	Company	Summary	Status Update
22	T-Mobile US	Capability and Runtime Restrictions The API template is available in PR#74	It was accepted by the TSC to treat this as a new API Initial YAML files to be included in the API TEMPLATE MEETING UPDATE: Clarifications will be provided by Murat. Intended to cover these slides but time ran out: and request ‘sandbox creation’. Will update the Issue #22 accordingly. To be reviewed in TSC on 17th
18	Totogi	New Proposal: Receive SMS The API template is available in PR#75	20240327-02 was completed. Herbert responded but not the subgroup owners, no activity seems to had happened for a month: Issue #9 · camaraproject/ShortMessageService Seems to fit in the SMS as a new scope enhancement The issue is not eligible to be closed yet. ACTION: Ricardo to formally proceed with the scope enhancement os the SMS group MEETING UPDATE: Reminder sent
34	China Unicom	New API Proposal: Shutdown ServiceStatus (SubscriptionStatus) The API template is available in PR#32	DECISION Separate Repos should be created but same family (KYC) in order to have coordination meeting Pending to confirm codeowner/maintainers for repo creation, email sent Included in today's TSC approval. Issue #34 can be closed and PR #32 merged ACTION Pending to validate remaining codeOwner MEETING UPDATE:
54	KDDI	Number Recycling The API template is available 55	NumberRecycling Pending Codeowners and maintainers (requested in comment) MEETING UPDATE: Group created and participants included, issue to be deleted. → PR merged
70	Cablelabs	New API proposal - Quality by Design The API template is available #71 Slides available here: here YAML available here: here	Proposal is that QbD be a scope enhancement to Connectivity Insights Will likely require new API, hence new repository required QdD supporters will attend Connectivity Insights meeting next week to finalise proposal Awaiting outcome of Connectivity Insights meeting before finalising if new repository required New repo to be created (new separated API) but included into the existing Connectivity insights family. To be confirmed base on the last meeting minutes. As soon as clarified, it will be included in next TSC DECISION : @Herbert Damker creates the repo QualityByDesign @Ben Hepworth provides user story/ies, → AP (Project team) Discuss the concept & propose rename → AP (TSC) Adjust the name MEETING UPDATE: Group created and participants included, issue to be deleted. → PR to be merged
41	Telefonica	New API Proposal: Telco Scoring The API template is available PR#42 Input from OGW Drop 4	Presented slides: API-Overview-TelcoScore.pptx The API seems to not fit within KYC and new sg should be created. Support is required, feel free Scoring can be calculated both with any user registered in the telco. Less information means less scoring, Algorithm may be different for each of the implementators (MNO) ACTION: Toshi validate if This API may fit within KYC API family → The issue was raised but still under discussion →(Toshi's proposal 20240627) In API Backlog 20240613 meeting, Jorge TEF and Toshi KDDI agreed that the API does not fit within the existing KYC-SP. Then, in KYC-SP 20240625 meeting, that was shared within KYC-SP and there was no objection. Closed. Pending meeting with DT to seek for support. ACTION Noel to come back to TEF Telefonica manage to find the support of VDF (Kevin confirmed in the chat also) and DT if no objections. The name should be readressed, Jorge was prposing Telco Index to avoid using legal restrictions for using words "Credit" and "Scoring". Nick propose Telco Trust → Discussing this in the issue ofline. Tanja (note in chat on behalf of Release Mgmt): Reminder to not use Telco specific terms in API names. To avoid: Telco, operator, CSP, subscriber, customer, EMEI, UE, etc. Pending: API approved, repo will be created after final name is proposed by the group (email sent) Pending to confirm codeowner/maintainers for repo creation, email sent and issue in discussion MEETING UPDATE: Pending to merge PR
60	Ericsson	New API proposal-Dedicated Networks The API template is available PR#59	Thorsten presented the proposal: Material here There have been a similar work in a TMF API. Pierre offered himself to Thorsten to reach up DECISION New repo/subproject to be created and a family that groups both NSB and DN ACTION Telefonica providing comments this afternoon and moving to TSC → Action complete Comments from TEF addressed in Issue PR#60 ACTION: Eric to check with Miranda in Issue PR#60 if her preference is for separate sub-projects, or for DN to join NSB sub-project No response regarding this, pending to response MEETING UPDATE: Discussion regarding separate or not separate repos. Telefonica supports having separate repos but having the conversation in the same forum as part of a unified family DECISION: Move to tsc taking care of this comment and expecting the administrative work to be clarified there. Someone for NSB group (Huawei, China etc.) should be connecting tsc that day at least to be aware of this ACTION: Thorsten to reach up NSB group by it mailing list proposing to join the TSC meeting. Next TSC meetings: 19/09/24 at 16:00 CEST / 14:00 UTC / 07:00 PST Meeting Registration / Join 03/10/24 at 10:00 CEST / 08:00 UTC / 01:00 PST Meeting Registration / Join Pending: Codeowners and Maintainers to be included MEETING UPDATE: Group created and participants included, issue to be deleted. → PR to be merged
61 66	Vodafone	Scope Enhancement for Network info The API template is available PR#72	To clarify if new API is proposed in the Device Status Family or it's an enhancement over an existing API. To clarify its relationship with Open Gateway Telco Finder API → Kevin opened PR#72 to complement Issue PR#66. Both still open. Noel commented that this is likely to be accepted New repository is likely to be required Comments have been provided in the issue Device Status group to confirm, TSC will review the match or alignment with Telco finder (GSMA) Device status WG, as part of Device status reachability, considered this enhancement. Device Status Issue143 Pending: Enhancement proposal to be updated by @Kevin Smith according to final scope agreed in Device Status group, TSC to be informed about final decision. MEETING UPDATE: As all solved, issue to be deleted → PR to be merged
68	Telefonica	New API proposal - Consent URL The API template is available PR#67	The API proposal was presented, including additional slide info Discussion to follow offline in the issue/PR. To hold a separated ad-hoc meeting to clarify the scope and need of the API (conclusions to be shared with backlog before any further decision) @Huub Appelboom supports API proposal @G. Murat Karabulut previously raised some concerns but seem clarified with last documentation. (uploaded in API PR#67 and also direct link) Pending: Proposal to be brought to TSC if no other concern is raised before end of week. MEETING UPDATE:

Review of Action Points

AP #	AP Owner	AP description	Related issue	Status
20240523-01	API Backlog Governance	Backlog Governance to reach up TelecomXchange & Netfocusin to see if the could connect next meetings	23 24	Open
20240711-04	MTN/Chenosis	IMEI Fraud: Check the material shared by Eric/GSMA regarding DeviceCheck, and validate the inclusion of the API in the Device Identifier group IMEI Fraud will offer more information than GSMA Device Check service. MTN and other supporters should meet with GSMA to discuss if proceeding with this API within CAMARA still makes sense. Request for meeting already sent by GSMA. Action to remain open until after meeting with GSMA is held Meeting Update: Waiting for more updates, any other operator open to join	63	Open
20240801-04	Vodafone	Scope Enhancement for Network info: To clarify if new API is proposed in the Device Status Family or it's an enhancement over an existing API. To clarify it's relationship with Open Gateway Telco Finder API. Kevin opened PR #72 to complement Issue #66. Both still open. Noel commented that this is likely to be accepted New repository is likely to be required Action to stay open until PR#72 is decided Meeting Update: Closed as per issue update	61	Closed
20240808-01	Ericsson	Dedicated Networks: Eric to check with Miranda in Issue #60 if her preference is for separate sub-projects, or for DN to join NSB sub-project No response yet Meeting Update: Closed as per issue update	60	Closed
20240822-01	Telefonica	Consent URL API: Discussion to follow offline in the issue/PR around Consent URL API use cases/user stories To hold a separated ad-hoc meeting to clarify the scope and need of the API (conclusions to be shared with backlog before any further decision) Meeting Update: Closed as per issue update	68	Closed
20240822-02	Vodafone	Scope Enhancement for Network info: Kevin opened PR#72 to complement Issue 66. Both still open about destination of API Device Status group to confirm, TSC will review the match or alignment with Telco finder (GSMA) Meeting Update: Closed as per issue update	66	Closed
20240912-01	Cablelabs	QualityByDesign: List of maintainer/codeowner https://github.com/camaraproject/APIBacklog/issues/70 User stories for the project, as first deliverable of the group Discuss the concept & propose rename (TSC) Adjust the name	70	Open
20240926-01	Telefonica	Telco Scoring Decide final name proposal for repo creation → Closed Pending to confirm codeowner/maintainers, email sent and issue in discussion	41	Open
20240926-02	Ericsson	Dedicated Networks Pending to confirm codeowner/maintainers, email sent and issue in discussion → closed	60	Closed
20240926-03	China Mobile	5G New Calling China mobile to further present the API proposal and include material in API PR#31. Partners to comment and further discuss the proposal.	35	Open
20240926-04	Verizon	Device Management Verizon to upload current yaml for clarification in PR#30, and present again in next meeting.	50	Open
20240926-05	Vodafone	Scope Enhancement for Network info Enhancement proposal to be updated by @Kevin Smith according to final scope agreed in Device Status group, TSC to be informed about final decision. → Closed	66	Open
20241010-01	China Mobile	IP High-throughput Elastic Network Provide more information on the technology dependancy, and the differences to current proposals Slice bookking QoD Dedicat	89	Open
20241010-02	ALL	IMEI Fraud Provide support from any company to take this API.	63	Open

Decision Points

DP #	DP description	Status
1	Increase backlog meeting duration from 1 to 1:30: 2nd Thursday of the month (10-11:30 CET) 4th Thursday of the month (15-16:30 CET)	Agreed

AoB

Proposal to extend meeting half hour (1:30 total) to accomodate all new APIs and also the track of existing.

Agreed

Next Backlog conf. call: 24th October, 15-16 CET/UTC+2.

Next TSC conf. call: 17th October, 16-17:30 CET/UTC+2

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 process 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 process 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 parallel..

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 process is detailed here. Upon receiving the API proposal and notification from the API backlog WG chair, the TSC studies the proposal 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 need 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 officially 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.

2024-10-10 API backlog minutes