2024-10-10 API backlog minutes
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
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
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.
|
 |
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.
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 |
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 | |
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:
| |
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 | |
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 | |
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. @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 | |
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 | |
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
@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 | |
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 | |
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 | |
China Mobile | Knowledge Base - Manage
The API template is available in PR#84 - Knowledge Base - Manage |
As per 83
| |
China Mobile | Q&A Assistant - Manage
The API template is available in PR#84 - Q&A Assistant - Manage |
As per 83 | |
China Mobile | Q&A Assistant - Service
The API template is available in PR#84 - Q&A Assistant - Service
|
As per 83 | |
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 | |
Telefonica | Fixed Lines in Location The API template is available in PR#92 | METING UPDATE: to be open in location group (no comments received) | |
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 |
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:
| |
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:
| |
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. ACTION Pending to validate remaining codeOwner MEETING UPDATE:
| |
KDDI | Number Recycling The API template is available 55 |