DRAFT MINUTES
Attendees
| Organization | Name |
| Orange | |
| Charter Communications | Christopher Aubut |
| Telefonica | Ricardo Serrano Gutierrez @agustinmartin Jorge Garcia Hospital |
| Vodafone | Eric Murray |
| Ericsson | Jan Friman |
| AT&T | Pierre Close |
| DT | Noel Wirzus |
| T-Mobile US | |
| KDDI | Yasu Wakama |
| Slagen | |
| Nokia | |
| China Telecom | |
| ZTE | |
| KPN | |
| GSMA | Helene Vigue |
| Centilion | Nick Venezia |
Agenda Proposal
- Antitrust Policy
- Approval of minutes of last conf. call
- Recent Updates & Recap
- Review of Action Points
- Discussion
OGW Drop #3 APIs: #19 (Device Quality Indicator)
Other APIs: #17 (Consent and Measurement), #18 (Receive SMS), #23 (Carrier Wholesale Pricing), #24 (Steering of Roaming Information), #29 (Call Status), #28 (Device Data Volume)
Governance: #4 (Structures and roles, RACI, Maintainers initiative)
- Clossing Issues
#20 (Best Interconnection), #22 (Capability and Runtime Restrictions), #2 (Tenure), #27 (Verified Caller)
- Action Points
- AOB
- Q&A
...
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
...
Approval of minutes of last conf. call
- Minutes of last API backlog WG call available here
DECISION: Approved
Recent Updates & Recap
TSC meeting 18th May:
...
- Keep PRs in the old repo and the new PRs will directly need to be opened in the new repo
- Issues will be moved to the new repo
Backlog table
- Table updated in PR#51 (merged)
Review of Action Points
| AP # | AP Owner | AP description | Related issue | Due date | Status |
| 20230208-02 | WG delegates | Delegates from interested parties to prepare a list of questions for this API, for Nick to answer them. | 2024/02/21 | Open | |
| 20230208-01 | Centilion | To draft a simple figure illustrating the API logic with a high-level workflow, and attach it to the PR. | 2024/02/21 | Open | |
| 20240314-01 | Governance | Ricardo to share the RACI in the issue 367 comments, after making CAMARA specific document and validation by TSC | 367 | 2024/03/14 | Open |
| 20240411-01 | Deustche Telekom | Noel updating proposal with new fields. Start in parallel while device status API is split | 375 |
| Open |
| 20240411-03 | Telefonica&DT | Modify the README for the QualityOnDemand subproject and include the new Scope enhancement | 402 404 |
| Closed |
| 20240425-02 | Centillinon | Next API Backlog meeting, Nick to bring new use cases and endpoints | 351 |
| Open |
Discussion
Current Issues
| 17 | Centillion | New Proposal for Authorization for Advertisements, Advertisements Consent, and Measurement The API template is available in PR#386. |
The issue is not eligible to be closed yet. Nick will be working within next weeks on providing what camara can work on within this API ACTION: Next API Backlog, Nick will bring new use cases and endpoints Not treated, to be handled in nex meeting (look at APs)Finishing documentation, Waiting for Real Time Bidding (RTB) standard to come up with the last versions so to provide further details | |||
| 4 | Governance | Adapt Project StructuresAndRoles.MD to changes in API backlog table (reduction of comments) | Ricardo is currently working on modeling a new table New WoW 3 companies needed Nick propose to focus more in the Commercial viability of the proposal in orther to rise up interest of other companies Huub points out the sensibility of posting commercial strategies within this type of forums as many companies are potential competitors The Strugling with the new Table model The issue is not eligible to be closed yet. | |||
| 18 | Totogi | New Proposal: Receive SMS The API template is available in PR#391 |
This issue was not treated in this conference call The issue is not eligible to be closed yet. DECISION: not treated to be treated in following session | |||
| 19 | 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 Isue 375 and 412 would be integrating within the Device Status subprojectsubproject The subgroup people is okay with this The issue is not eligible to be closed yet. to be treated in following session | 23 | TelecomsXChange | New Proposal: Carrier Wholesale Pricing |
| 23 | 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. DECISION: not treatedto be treated in following session ACTION: Ricardo to reach up TelecomXchange to see if the could connect next meetings | |||
| 24 | Netfocusin Technologies | New Proposal: Steering of Roaming Management | Does not seem to be in the Scope of Camara. DECISION: Discuss this in the next meeting (whenever Netfocusin Technologies is able to connect) to be treated in following sessionThe issue was not treated in this conference call The issue is not eligible to be closed yet. DECISION: not treated ACTION: Ricardo to reach up Netfocusin Technologies to see if the could connect next meetings | |||
Deutsche Telekom | New API Proposal: Device Data Volume New template in PR#39 | The Template was merged by mistake PR#411, The PR needs to be updated The two APIs will be treated as new proposals that will be presented to the TSC when ready in BL ACTION: Reopen the closed pull request or make a new one with the existing files → solved To be treated in next sessionDECISION: 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 | ||||
Rogers | New API Proposal: Call Status | Nicholas to update template in PR, clarify in the issue whether this proposal come from GMSA and review existing API linked by noel in the issue To be treated in next session | Issue is closed due to lack of activity → redacted | |||
China Unicom | New API Proposal: Shutdown ServiceStatus The API tempate is available in PR#32 | Not treated (relations with device status to be considered) To be treated in next session ACTION: Open an issue within DeviceStatus subproject to check overlaps. | ||||
China Mobile | 5G New Calling The API template is available PR#31 | Not treated To be treated in next session | ||||
Telefonica | New API Proposal: Telco Scoring The API template is available #42 | Telefonica | Scope Enhancement: KYC-Match API -Scoring logic The API template is available #46Input from OGW Drop 4 | Presented slides: API-Overview-TelcoScore.pptx Scoring is a simple algortithm/model but need to be aligned within all the operators Splicit consent is needed. How the model is going to be discussed?
Unified model for all the countries may lead into dificulties in order to fit the API within CAMARA Scope ACTION: Toshi validate if This APImay fit within KYC API familiy ACTION: Jorge Reach out to Nick by email | ||
Telefonica | Scope Enhancement: KYC-Match API -Scoring logic The API template is available #46 | This is just an enhancement of the current API. Looks fine as an Enhancement. SHould work without scoring due to limitation in some countries (not all responses include scoring, some cases does not make sense). Optional parameter in the output ACTION: Toshi validate if This API may fit within KYC API participants | ||||
China Unicom | Scope Enhancement: Name change RegionUserCount The API template is available #47 |
...
| 20 | Deutsche Telekom | Best Interconnection | The issue was not treated in this conference call. Noel aplogized in advance and suggested to wait till April first week TSC meeting to move on with this API DECISION: Move to TSCSeek for support ACTION: See if there is any overlap within EdgeCloud |
| 22 | T-Mobile US | Capability and Runtime Restrictions | It was accepted by the TSC to treat this as a new API intitial YAML files to be included in the API TEMPLATE The issue was not treated in this conference call |
...
Action Points
| AP # | AP Owner | AP description | Related issue | Due date | Status |
| 20240509-01 | Vodafone | To check with KDDI (KYC family owner) if this APi discussions can fit in the KYC meeting, due to the similarity in use cases. | 2 | 9/05/2024 | Open |
Decision Points
| DP # | DP description | Related issue |
| 20240509-01 | Verified Caller API move for approval, to be treated in following TSC | |
| 20240509-02 | Tenure API move for approval, to be treated in following TSC |
AoB
Next Backlog conf. call: 23th May, 15-16 UTC+2.
Next TSC conf. call: 16th May, 16-17,30 UTC+2
Q&A
How does CAMARA API pipeline work?
...