2024-08-08 API backlog minutes
Attendees
Organization | Name |
Orange | |
Charter Communications | @Christopher Aubut |
CableLabs | @Ben Hepworth |
Telefonica | |
Vodafone | @Eric Murray @Kevin Smith |
Ericsson | @Thorsten Lohmar @Jan Friman |
AT&T | @Pierre Close |
T-Mobile US | |
KDDI | |
Slagen | |
Nokia | |
China Telecom | |
ZTE | |
KPN | |
GSMA | @Reg Cox @Mark Cornall |
Centilion | |
Chunghwa Telecom | |
Deutsche Telekom | @Noel Wirzius |
MTN | @Krishna Venkatachalam Rachel |
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), #41 (Telco Scoring), #50 (Device Management), #63 (IMEI Fraud)
Other APIs: #17 (Consent and Measurement), #23 (Carrier Wholesale Pricing), #24 (Steering of Roaming Information), #60 (Dedicated Networks), 61 (network Info), 68 (Consent URL), 70 (Quality by Design)
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 1st August:
No new APIs brought to TSC
NumberRecycling
Repository was created: https://github.com/camaraproject/NumberRecycling
Initial Maintainers and Codeowners need to be defined
DeviceStatus accepted the new APIs Device Quality Indicator and Device Data Volume APIs
CAMARA admin team to create the repositories (check API Proposal issues)
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.
Backlog table
Table updated in PR#62 (merged)
Review of Action Points
AP # | AP Owner | AP description | Related issue | Due date | Status |
20240523-01 | API Backlog Governance | Ricardo to reach up TelecomXchange, Totogi and Netfocusin Technologies to see if the could connect next meetings | 23/05/2024 | Open | |
20240523-07 | DT | Best interconnection: Review whether there is overlap with EdgeCloud subproject Meeting Update:
| 23/05/2024 | Completed | |
20240627-01 | China Unicom, KDDI, Vodafone, DT | Check whether Tenure + Shutdown service + Number recycling fit in KYC (parts involved align internally) Closed for Tenure and Number Recycling (accepted and repo created) Shutdown Service pending to create repo. Codeowners to be required by email (China Unicom, China Telecom, Huawei) and reported to TSC. Meeting Update:
| 28/06/2024 | Completed | |
20240627-02 | API Backlog Governance | New use cases are usually proposed. Modify the Scope template to show this and approve | 28/06/2024 | Completed | |
20240711-01 | Netfocusin Technologies | Seek for support/commitment from the partners (technical implementation approach important) | 11/07/2024 | Open | |
20240711-02 | Telefonica | Provide comments for dedicated network | 11/07/2024 | Completed | |
20240711-03 | Vodafone | Create the template for network info | 11/07/2024 | Completed | |
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:
NOTE: Can be taken to TSC if agreement by end of ThursdayAug 15, 2024 | 11/07/2024 | Open | |
20240801-01 | Deutsche Telekom | Device Quality Indicator: To provide list of Maintainer/Codeowner Meeting Update:
| 16/08/2024 | Completed | |
20240801-02 | Deutsche Telekom | Device Data Volume: To provide list of Maintainer/Codeowner Meeting Update:
| 16/08/2024 | Completed | |
20240801-03 | China Unicom | Shutdown ServiceStatus: To provide list of Maintainer/Codeowner Meeting Update:
| 16/08/2024 | Completed | |
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:
NOTE: Can be taken to TSC if agreement by end of ThursdayAug 15, 2024 | 08/08/2024 | Open | |
20240801-05 | Cablelabs | Quality by Design: Clarification pending on the differences with current Mobile/Fixed QoD and Network info / Quality indicator APis / Connectivity Insights Meeting Update:
NOTE: Can be taken to TSC if agreement by end of ThursdayAug 15, 2024 | 08/08/2024 | Open |
Discussion
Current Issues
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. MEETING UPDATE:
| |
Governance | Adapt Project StructuresAndRoles.MD to changes in API backlog table (reduction of comments) | Ricardo is currently working on modeling a new table Struggling with the new Table model. Bring the PRs from the old repo Makes sense to bring the table to confluence? GitHub seems to be more accesible and is visited by further people (devs. etc.) The issue is not eligible to be closed yet. MEETING UPDATE:
| |
TelecomsXChange | New Proposal: Carrier Wholesale Pricing First YAML avaliable here | The issue was not treated in this conference call The issue is not eligible to be closed yet. ACTION: Ricardo to reach up TelecomXchange to see if the could connect next meetings MEETING UPDATE:
| |
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:
| |
China Mobile | 5G New Calling The API template is available PR#31 | Not treated 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:
| |
Telefonica | New API Proposal: Telco Scoring The API template is available #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 APImay fit within KYC API familiy → The issue was rised 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:
| |
Verizon | Device Management The API template is available #30 |