2024-09-26 API backlog minutes
- Jorge Garcia Hospital
- G. Murat Karabulut
- Pierre Close
DRAFT MINUTES
Attendees
ย
Organization | Name |
Orange | @Ludovic Robert |
Charter Communications | ย |
CableLabs | ย |
Telefonica | @Jorge Garcia Hospital |
Vodafone | @Eric Murray @Kevin Smith |
Ericsson | @Thorsten Lohmar |
AT&T | @Pierre Close |
T-Mobile US | @G. Murat Karabulut |
KDDI | Yusuke Nakano |
Slagen | ย |
Nokia | ย |
China Telecom | ย |
ZTE | ย |
KPN | @Huub Appelboom |
GSMA | Reg Cox @Mark Cornall |
Centilion | ย |
Chunghwa Telecom | ย |
Deutsche Telekom | ย |
MTN | ย |
China Mobile | @Haojie Li @Keguang He @zhangruqian |
Verizon | @Mahesh Chapalamadugu |
ย
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),ย
Other APIs: ย #17ย (Consent and Measurement), ย #23ย (Carrier Wholesale Pricing), ย #24 (Steering of Roaming Information),ย #66ย (network Info),ย #68 (Consent URL), #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: Approved
Recent Updates & Recap
TSC meeting 19th September:
Repository for QualityByDesign created (as decided last meeting)
New API proposal brought to TSC (2):
See messageย https://lists.camaraproject.org/g/tsc/message/227
ย
TelcoIndex API
Supported by Telefonica, DT, Vodafone
API proposal: Link
Discussion:
Naming discussion:ย https://github.com/camaraproject/APIBacklog/pull/42#issuecomment-2348157633
Decision: Start this API in sandbox (repo) and then work on the name
Jorge Garcia Hospital propose first to ask to supporter companies if OK to start with this name.
Axel.Nennker@telekom.de explained that for DT the term risk indicator was used. The use of score term is very risky (from regulation). We must be clear that it will not be used to discriminate people. If it based on AI model, the model must be shared to allow people to challenge it.
Dedicated Networks API
Supported by Ericsson, Nokia, Telefonica, Vodafone
API proposal: Link
Decision : Start the work in a sandbox (repo) and then with provided assets check/reassess collision/overlap with other CAMARA API (like network slicing booking API but other APIs could be affected)
ย
Other topics
GSMA informed CAMARA Backlog that Open Gateway is considering certainย Drop2/3ย 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 |
17ย | Centillion | New Proposal for Authorization for Advertisements, Advertisements Consent, and Measurement | 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 MEETING UPDATE: Clarifying with interested parties whether this may be a possible API or a Framework etc. |
Governance | Adapt Project StructuresAndRoles.MD to changes in API backlog table (reduction of comments) | 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 MEETING UPDATE: Partners to review and validate | |
TelecomsXChange | New Proposal: Carrier Wholesale Pricing 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 ย | 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) Pending to clarify scope with VerifedCaller MEETING UPDATE: 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 Operators open to comment/ask for clarification and support the API. | |
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 MEETING UPDATE: API proposal presented by @Mahesh Chapalamadugu , clarified this proposal is targeted for IoT device management to activate/deactivate/manage the connection of those devices. @Mahesh Chapalamadugu to upload current yaml for clarification in PR#30, and present again in next meeting. | |
61ย | 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
MEETING UPDATE:ย ย Device status WG, as part of Device status reachability, considered this enhancement. Device Status Issue143 Enhancement proposal to be updated by @Kevin Smith according to final scope agreed in Device Status group, TSC to be informed about final decision. |
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
MEETING UPDATE: @Eric Murray : (IMEI status) service related, but GSMA is ok for this proposal. Waiting for MTN for moving on with this API. Maybe to be included in the Device Identifier family. ย | |
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.
MEETING UPDATE: @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) Proposal to be brought to TSC if no other concern is raised before end of week. | |
Deutsche Telekom | Best Interconnection | 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:
ย | |
China Mobile | Model As A Service Family | China Mobile presented the API MEETING UPDATE: 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. ย | |
China Mobile | Knowledge Base - Manage | ย MEETING UPDATE: ย | |
China Mobile | Q&A Assistant - Manage | ย MEETING UPDATE: | |
China Mobile | Q&A Assistant - Service | ย MEETING UPDATE: | |
China Mobile | IP High-throughput Elastic Networkย The API template is available inย PR#90 | Not to be treated in this meeting. |
Closing Issues
Issue # | Company | Summary | Status Update |
T-Mobile US | Capability and Runtime Restrictions | 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 |
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:
| |
Deutsche Telekom | New Proposal: Device Quality Indicator | Noel proposed Device Status subgroup to integrate their APIs within Noel's. Noel to make the proposal to the API Backlog and provide update Two proposals Issueย 19ย andย 28ย would be integratingย within the Device Status subprojectย The subgroup people is okay with this The issue is not eligible to be closed yet. Move to TSC, check wether there is support for this API (Interested parties provide comments in the Issue, Vodafone committed and a third supporter is being queried) Both issue 19ย andย 28ย to the DeviceStatus family and separate repositories (deviceStatus) โ ย Device Quality Indicator DECISIONย formal agreement from the Device Status subgroup is required. To be treated in next meeting (Device Status) DECISIONย There is agreement Orange, DT and VDF, next backlog meeting there should be the outcome for this issue Pending to confirm codeowner/maintainers for repo creation, email sent
MEETING UPDATE:
| |
Deutsche Telekom | New API Proposal: Device Data Volume New template inย PR#39 | Move to TSC, check wether there is support for this API (Interested parties provide comments in the Issue) Both issueย 19ย andย 28ย to the DeviceStatus family and separate repositories (deviceStatus) โย Device Data Volume DECISIONย formal agreement from the Device Status subgroup is required. To be treated in next meeting (Device Status) DECISIONย There is agreement Vonage, DT and VDF, next backlog meeting there should be the outcome for this issue Pending to confirm codeowner/maintainers for repo creation, email sent 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. MEETING UPDATE:
| |
KDDI | Number Recycling The API template is availableย 55 | Pending Codeowners and maintainers (requested in comment) MEETING UPDATE:
| |
Cablelabs | New API proposal - Quality by Design The API template is availableย #71 | 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 ย
DECISION :
MEETING UPDATE:
| |
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 MEETING UPDATE: 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.ย ย MEETING UPDATE:
| |
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 03/10/24 at 10:00 CEST / 08:00 UTC / 01:00 PST 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 | 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
Meeting Update: | 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.
Meeting Update: Closed as per issue update | 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
Meeting Update: Closed as per issue update | Closed | |
20240822-01 | Telefonica | Consent URL API: Discussion to follow offline in the issue/PR around Consent URL API use cases/user stories
Meeting Update: Closed as per issue updateย | Closed | |
20240822-02 | Vodafone | Scope Enhancement for Network info: Kevin openedย PR#72 to complement Issue 66. Both still open about destination of API
Meeting Update: Closed as per issue update | Closed | |
20240912-01 | Cablelabs | QualityByDesign:
ย | Open | |
20240926-01 | Telefonica | Telco Scoringย
| ย 41 | Open |
20240926-02 | Ericsson | Dedicated Networks
| Open | |
20240926-03 | China Mobile | 5G New Calling
| Open | |
20240926-04 | Verizon | Device Management
| Open | |
20240926-05 | Vodafone | Scope Enhancement for Network info
| Open |
Decision Points
DP # | DP description |
1 | Increase backlog meeting duration from 1 to 1:30:
|
ย | ย |
ย | ย |
ย | ย |
ย | ย |
AoB
Proposal to extend meeting half hour (1:30 total) to accomodate all new APIs and also the track of existing.
@all to comment
Next Backlog conf. call: 10th October, 10-11ย CET/UTC+2.
Next TSC conf. call: 3rd October, 10-11: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.