2025-05-22 API backlog minutes
Attendees
Organization | Name |
Orange |
|
Charter Communications | @Christopher Aubut |
CableLabs |
|
Telefonica | @Alberto Ramos Monaga |
Vodafone | @Eric Murray @Surajj Jaggernath |
Ericsson | @Jan Friman |
AT&T | @Pierre Close |
T-Mobile US | @Murat Alrabasi |
KDDI | @Toshi Wakayama |
Slagen |
|
Nokia |
|
China Telecom |
|
ZTE |
|
KPN | @Appelboom, Huub |
GSMA |
|
Centilion |
|
Chunghwa Telecom |
|
Deutsche Telekom | @Noel Wirzius |
MTN |
|
China Mobile |
|
Verizon |
|
PlektonLabs |
|
TIM |
|
NTT |
|
China Unicom |
|
Infosys Ltd | @Abhisek Das @Hemanta Gogoi |
Spectrum | @Justin Pace |
Agenda Proposal
New APIs Proposals:
#35 (5G New Calling), #63 (IMEI Fraud), #17 (Consent and Measurement), #23 (Carrier Wholesale Pricing), #24 (Steering of Roaming Information), #115 (SIM Historical Information), #121 (User Account Spend Count), #122 (Number Of Cards Under User's ID), #160 (Voice Verification Code), #167 (IdentityAndConsentManagement), #205 (Multi Point VPN)
Out of Agenda:
#141 (Energy Footprint Notification), , #126 (Facial Recognition), #18 (Receive SMS), #89 (IP High-throughput Elastic Network), #41 (Telco Scoring), #83 #85 #86 #87 (Model as a Service), #20 (Best Interconnection), #68 (Consent URL), #91 (Fixed lines in Device Location APIs), #93 (Line Eligibility for Carrier Billing API), #50 (Device Management) #95 (IoT SIM Status Mgmt API), #96 (IoT SIM Fraud Prevention API), #109 (Support application resource requirements in application profiles), #163 (Dynamic Predictive Connectivity Data), #143 (IoT Network Optimization), #127 (Network Health Assessment), #128 (Network Traffic Analysis), #136 (eSIM Remote Management), #157 (Voice Notification)
Approval of minutes of last conf. call
Minutes of last API backlog WG call available here
DECISION: approved.
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.
|
 |
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 (9-10:30 UTC)
4th Thursday of the month (15-16:30 UTC)
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.
New API proposals are included in backlog table when template PR is created, linking to the pending PR
PR will be merged as soon as ready for TSC, and should be merged before TSC review
API enhancements requires existing group’s validation. TSC is informed accordingly to validate
Link and status in backlog table will be updated accordingly
Issue to track API onboarding will be opened once new API is confirmed in TSC.
Recent Updates & Recap
Last TSC meeting 2025-05-15:
No new API proposed for this session.
→ Open discussion on how to manage VPN related APIs, from current Site-to-Cloud-VPN to MultiPoint VPN proposal. Will update in TSC as soon as clarified.
Proposal how to manage stale API proposals and Sandbox API repositories in work
Standby/archived proposal will be included to manage those proposals and sandbox that are proposed but not “used”.
Other topics
New sandbox repo created: https://github.com/camaraproject/VoiceNotification.
We've carried out a cleanup of open issues in the API Backlog WG:
The API proposals for eSIM Remote Management, NetworkInsights, Telco Index, and IoT SIM Status Management have been closed, as they already have onboarding trackers and were no longer active.
We're now applying the same process to open pull requests to keep the backlog clean and up to date.
Draft frozen API proposal - information is shared with the backlog group, time is given for review and if the proposal is approved it is taken to the governance group https://github.com/camaraproject/APIBacklog/issues/212 .
Deadline to review: Next TSC meeting.
Proposal to Split KYC repo – https://github.com/camaraproject/APIBacklog/issues/213. There is a proposal under discussion within the KYC subproject community to split the current repository into three separate ones:
Decision: OK - AP: create onboarding trackers.
Repository incubation request:
Device swap: https://github.com/camaraproject/APIBacklog/issues/214.
Population Density Data: https://github.com/camaraproject/APIBacklog/issues/215 (subproject is created for this API)
Decision: OK - AP: the decision will be taken to the TSC Meeting.
Formalization of group name change from Number Verification to Number Insight: https://github.com/camaraproject/APIBacklog/issues/216.
Number verification accepts Device swap and Voice Verification Code (sent for approval to TSC) be part of the group.
Decision: OK
AP:
Voice Verification Code (sent for approval to TSC) and to be part of the group.
Device Swap move to NI
Create an issue in the Number Recycling group to be part of Number Verification sub project (proposed Number Insights) (@Toshi Wakayama & @Noel Wirzius to bring the discussion).
Discussion
Current Issues
Issue # | Company | Summary | Status Update |
Centillion | New Proposal for Authorization for Advertisements, Advertisements Consent, and Measurement The API template is available in PR#73. | INITIAL CONTEXT: 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. AP: provide required information and examples LAST UPDATES: No response since October 8, 2024. Feb 27, 2025: not treated Mar 13, 2025:not treated Mar 27, 2025: not treated Apr 10, 2025: not treated Apr 24, 2025: not treated May 8, 2025: not treated MEETING UPDATE: May 22, 2025: | |
TelecomsXChange | New Proposal: Carrier Wholesale Pricing The API template is available in PR#77 First YAML available here | INITIAL CONTEXT: 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 LAST UPDATES: No response for 6 months. Feb 27, 2025: not treated Mar 13, 2025: not treated Mar 27, 2025: not treated Apr 10, 2025: not treated Apr 24, 2025: not treated May 8, 2025: not treated MEETING UPDATE: May 22, 2025: | |
Netfocusin Technologies | New Proposal: Steering of Roaming Management The API template is available in PR#78 | INITIAL CONTEXT: 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) LAST UPDATES: No response since May 10, 2024. Feb 27, 2025: not treated Mar 13, 2025: not treated Mar 27, 2025: not treated Apr 10, 2025: not treated Apr 24, 2025: not treated May 8, 2025: not treated MEETING UPDATE: May 22, 2025: | |
China Mobile | 5G New Calling The API template is available PR#31 | INITIAL CONTEXT: 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. @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: ACTION: Operators open to comment/ask for clarification and support the API. @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 https://github.com/camaraproject/WebRTC/issues/52 to discuss in WebRTC about relationship new information to be uploaded and treated in next session Recommendation is that China Mobile join regular WebRTC call to discuss 5G New Calling proposal there. LAST UPDATES: No response since June 11, 2024. Feb 27, 2025: not treated Mar 13, 2025: not treated Mar 27, 2025: not treated Apr 10, 2025: not treated Apr 24, 2025: not treated May 8, 2025: not treated MEETING UPDATE: May 22, 2025: | |
MTN | New API proposal - IMEI Fraud The API template is available PR#64 | INITIAL CONTEXT: 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
@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. @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 LAST UPDATES: No response since September 6, 2024. Feb 27, 2025: no treated Mar 13, 2025: not treated Mar 27, 2025: not treated Apr 10, 2025: not treated Apr 24, 2025: not treated May 8, 2025: not treated MEETING UPDATE: May 22, 2025: | |
China Unicom | SIM Historical Information The API template is available in PR#114 | INITIAL CONTEXT: @Eric Murray comment: Sounds like a “historical SIM Swap” API. Discuss with SIM Swap sub-project. APs: China Unicom
LAST UPDATES: Feb 13, 2025: @Fan Yang to review issue offline and provide feedback and current status of the proposal. Feb 27, 2025: @Fan Yang no updates, will be reviewed in next meeting Mar 13, 2025: not treated Mar 27, 2025: not treated Apr 10, 2025: not treated Apr 24, 2025: not treated May 8, 2025: not treated MEETING UPDATE: May 22, 2025: | |
China Unicom | User Account Spend Count The API template is available in PR#120 | INITIAL CONTEXT: |
