/
2026-02-12 API Backlog Minutes

2026-02-12 API Backlog Minutes

 

Attendees

Organization

Name

Orange

 @Gilles Renoux

Charter Communications

CableLabs

 

Telefonica

@Alberto Ramos Monaga

Vodafone

@Eric Murray

Ericsson

@Jan Friman

AT&T

@Pierre Close

T-Mobile US

KDDI

 

Slagen

 

Nokia

 

China Telecom

 

ZTE

 

KPN

 

GSMA

@Reg Cox

Centilion

 

Deutsche Telekom

 

MTN

 

China Mobile

 

Verizon

 

PlektonLabs

 

TIM

 

NTT

 

China Unicom

 

Infosys Ltd

@linda juffermans

Spectrum

 

Chunghwa Telecom

 

Telecom Argentina

 

Huawei

 

xFlow Research

 

NCSRD

@panagiotis pavlidis @harilaos koumaras

Infolysis

@Pantelis Papachronis @Vaios Koumaras

Agenda Proposal

Approval of minutes of last conf. call

  • Minutes of last API backlog WG call available here

    • DECISION: OK

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:

  1. 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.

  2. 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)

  3.  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. 

  4. New API proposals are included in backlog table when template PR is created, linking to the pending PR

  5. PR will be merged as soon as ready for TSC, and should be merged before TSC review

  6. API enhancements requires existing group’s validation. TSC is informed accordingly to validate

  7. Link and status in backlog table will be updated accordingly

  8. Issue to track API onboarding will be opened once new API is confirmed in TSC.

  9. New proposal Lifecycle for frozen APIs.

Recent Updates & Recap

Last TSC meeting 2026-02-05 (summary):

Governance:

  • MCP Whitepaper: several articles, e.g. here and here, worth to read: a longer review by Dean Bubley and work in progress of MCP Enablement Program #210.

API Backlog:

  • Name change proposal: Device Quality Indicator —> Device Media Streaming Rate #296. API family owner, API family supporters remains as before.

    • Decision: Approved, issue #296 will be used to manage the change

Commonalities:

Identity & Consent Management:

  • Spring26 meta-release status:

    • The Spring26 Release Candidate (r4.1) PR is available for review #344.

    • The following issues were dropped from the scope of the meta-release (more details on the reasoning behind these decisions can be found here):

      • #288 (the WG has decided to remove the OAuth 2.1 adaptations from the scope of Spring26 and move them to a future release, with a tentative target of Spring27), #312 (the WG noted insufficient business justification and no participant ownership for continuing RAR support).

  • Consent Info API: The repository is preparing for the v0.2.0 release candidate #46. The v0.2.0‑rc.1 pre‑release PR has passed all checks and received approvals; only Release Management review is pending.

  • Consent Management API - Controlled Consent Capture Delegation: Initial API draft is under review; Open questions from previous sessions have been addressed; Further review to continue as needed; No open blocking issues.

Release Management:

Other topics

(Information) CAMARA APIs - Functional Differences (Use-Case & Data Semantics Edition: A white paper has been produced for publication on the CAMARA website to explain in detail what problem each API solves, what data it delivers, how to interpret it, and how to combine them in risk and error-prevention policies (Audience: Non-telco experts) APIs covered: SIM Swap · Device Swap · Tenure · Number Recycling - (link)

(Information) Define standard README warning and topics for archived API repositories #297: Define a standard warning/note block to be added at the top of the README of any API repository that is archived

(Review PR) Update the backlog table with the changes as of December #280

(Scope enhancement) Enhancement of Dedicated Networks API #295: Dedicated Networks proposes an optional “Areas API” (Issue #86 / PR #87) to help consumers find/select eligible areas. Early signals suggest the same concept may also be needed in QoS Booking, so we risk duplicating / diverging semantics across CQM APIs. The group needs guidance on whether this should be treated as:

  • DN-only optional API enhancement (new API within the Dedicated Networks family), or

  • a shared CQM cross-API building block that can be reused by multiple CQM APIs (at minimum DN + QoS Booking), to prevent duplication.

    • Decision: The decision must be agreed upon by the group before being added to the backlog - (no new updates)

Discussion

Current Issues 

Issue #

Company

Summary

Status Update

#259

Heksagon

Voice One Time Password Call

The API template is available at #263

INITIAL CONTEXT:

The “Voice One Time Password Call” API is used to send short-lived one time passwords (OTP) to a phone number via voice call and validate it afterwards, in order to provide a proof of possession of the phone number.

AP1: Update the PR by creating a new entry under documentation/API-proposals instead of modifying documentation/API-proposal-template.md.

AP2: Create an issue with the API proposal label and link it to this PR.

AP3: Resolve the easyCLA error by clicking the provided link and signing the authorization

Sep 25, 2025: Not treated

Relation with Voice Verification Code (#233) - Herbert suggest if we can merge this with this issue.

Heksagon: Regarding your suggestion to merge our issue proposal with #233, we have checked and it looks like that their use case works only for "IMS based audio codes" as explained in their API description which is not the case for our API. So we don't think that merging the two issues would be a good idea. If there is any further discussion needed on that, we can have a call to evaluate it.

Oct 10, 2025, Oct 23, 2025, Nov 13, 2025,Nov 27, 2025, Jan 8, 2026: Not treated

Dec 11, 2025: Resolve the PR comments and upload the PowerPoint presentation - Not treated

Jan 22, 2026: Not treated

MEETING UPDATE:

Feb 12, 2026: Not treated

#288

T-Mobile US

Group Management API

The API template is available at #289

INITIAL CONTEXT:

The Group Management API enables API Consumers to create and manage named groups of pre-defined entities (e.g. devices or areas). It supports batch membership operations and event-driven notifications, making it ideal for Service APIs (e.g., Geofencing) that need to manage and track sets of entities, and be informed about changes to group member states.

Related Issue: Standardize Group Management for CAMARA Sub-Projects

Jan 8, 2026: Not treated

Jan 22, 2026: @Murat Karabulut Will be discussed in commonalities first.

MEETING UPDATE:

Feb 12, 2026: Not treated

#293

NCSRD
& Infolysis

Trust Worthiness Intent API

The API template is available at #294

INITIAL CONTEXT:

TWIA is an intent-based API that lets an app submit high-level trust requirements (Security, Privacy, Reliability, Resilience, Safety) in natural language and get back per-category scores plus an overall trustworthiness level, without dealing with low-level configuration.

Jan 8, 2026, Jan 22, 2026: Not treated

MEETING UPDATE:

Feb 12, 2026: The owner presented the API. Discussion:

  • @Eric Murray: Whether “assurance tiers” (higher reliability/security/privacy) are just a pricing negotiation, and asks what concrete input from the API consumer would make the provider actually change how the service is delivered (e.g., infrastructure/operations) to meet that higher tier.

    • Harilaos: the current “trustworthiness” score is effectively tied to specific user profiling; it’s not priced that way yet, but profiling could drive tiered pricing (validated commercially with a Greek mobile operator), potentially requiring API extensions to support negotiation of different profiling/charging levels.

  • @Jan Friman: Ask for a concrete example of a service that would use this kind of profiling (e.g., connectivity or positioning), and whether it’s meant to apply to any service or only to specific service categories.

    • Harilaos: like VR/XR as the concrete example: a “highly trustworthy” XR app would justify different operational treatment (e.g., stricter service provisioning controls, core-network prioritization, and differentiated access/assurance mechanisms), etc.

AP1: Refine the PR:

  • 1) Make the proposal more telco operator capability to differentiate it from AI-trust scoring, which does not require the telco.

  • 2) Standardize the normative definition of 0-1 score to make multi-operator interoperability more realistic.

  • 3) Focus only on POST/intents for now, and leave the subscriptions part for a future version.

  • 4) Given the risk involved in entering free text (personally identifiable information/confidential data), apply protective measures in the proposal.

#298

Infosys

Enterprise Connectivity Governance API - ConnectivityGovernance

The API template is not available yet

INITIAL CONTEXT:

The proposed Enterprise Connectivity Governance API enables telcos to enforce enterprise network policies at the operator network level (e.g., gateway/edge/core) across MPLS, SD-WAN and mobile networks, so enterprises can centrally control or restrict access to services/app categories (e.g., streaming sites) and optimize usage for compliance scenarios (including BYOD) without installing software on end-user devices.

MEETING UPDATE:

Feb 12, 2026: Not treated

Out Of Agenda

N/A

Closing Issues

Issue #

Company

Summary

Status Update

18

Totogi

New Proposal: Receive SMS

 

The API template is available in PR#75

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

→ Follow-up on API onboarding tracker: Pending.

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.