DRAFT MINUTES
Attendees
...
Dagoberto Garavito
...
Lyle Bertz, Murat Karabulut
Agenda Proposal
- Antitrust Policy
- Approval of minutes of last conf. call
- Recent Updates & Recap
- Review of Action Points
- Discussion
- OGW Drop 3 APIs: 336, 375, 376
- Other APIs: 351, 372, 378, 383
- Governance: 367
- Action Points
- 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
- 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
...
DRAFT MINUTES
Attendees
CableLabs | Randy Levensalor |
Charter Communications | Chris Aubut, Justin Pace Jason Page |
Ericsson | Jan Friman |
GSMA | Mark Cornall |
Nokia | Tanja De Groot |
Shabodi | Nitin Sood |
Telekom | Wirzius, Noel |
Telefónica | Ricardo Serrano Gutierrez Laura Lacarra Arcos Javier Villa Labarra Lukas Wiegandt Jorge Garcia Hospital |
Totogi | Ailton Santana |
Vodafone | Eric Murray |
Slagen | Dagoberto Garavito |
T-Mobile US | Lyle Bertz Karabulut, Murat |
Agenda Proposal
- Antitrust Policy
- Approval of minutes of last conf. call
- Minutes of last API backlog WG call available here
- DECISION: The minutes are approved.
- Recent Updates & Recap
Backlog table
- Table updated in PR#387
Discussion
Current Issues
...
The issue was discussed in last TSC call (minutes available here).
Discussion held, with a proposed way forward captured:
- GSMA OGW product workstream to re-check commercial value of such an API
- Anti-fraud use case to be reviewed and clarified
- Remove marketing use case
- TSC to then agree disclaimer to be included in sub-project repository.
The issue is not eligible to be closed yet.
...
- Telefonica: still looking for supporting companies.
- TIM: interested in participating in the API (no commitment yet to becoming support).
The issue is not eligible to be closed yet.
...
PR#386 replaces the existing PR#350. Two templates published: one in the PR thread, and another one as a separate .md file. These templates differ in the "validation" row, where one claims that the API has validated with GSMA Open Gateway, mentioning Mark and Toyeeb explicitly. The chair asked Mark about this.
- Mark (GSMA):
- Clarified that Centillion approached him and Toyeeb with the API proposal, but actual validation has not been conducted. He provided a summary of what this API was about, stressing the focus on advertising (advertising-driven revenues).
- He also noted the multiple dimensions and aspects for thoughtful consideration that this API has.
- Eric (Vodafone): assked for clarification on "measurement" part in the API proposal name. Mark clarified that the intention is to validate impressions.
- Jan (Ericsson): wondered whether this API proposal is somewhat related to TMForum-led Operate API "Developer & App onboarding" API as for the consent, specially considering that the TMForum API includes scope, specifying what it is allowed to do and consume (for which purposes).
- Mark (GSMA): said that this API proposal might have nothing to do with the "Developer & App onboarding" API as for the consent, as they pursue different goals.
- Jan (Ericsson): noted that a simple figure illustrating the API logic with a high-level workflow would be very helpful. He asked Centillion to attach this figure to the PR.
ACTION: to draft a simple figure illustrating the API logic with a high-level workflow, and attach it to the PR.
- Jose (Telefónica): mentioned that the discussion started in Identity&Consent Sub-Project, and a certain point of time, it was migrated to APIBacklog WG as a new API proposal. He wondered whether there are major differences between what this new API proposes and what was originally discussed in Identity&Consent Sub-Project.
- Eric (Vodafone): clarified that the ambition of this API proposal is quite different from what was originally discussed. Mark (GSMA) acknowledges this, and stress again the focus on advertising.
- Jose (Telefónica): proposed to resume the discussion in a call that Nick (Centillion) is able to join. In the meantime, he asked the delegates to prepare a list of questions to ask Nick, so he can provide answers that can help the API proposal move forward.
...
- Review of Action Points
...
AP Owner
...
AP description
...
Related issue
...
Due date
...
Status
...
Charter Communications
...
Check potential relationship of this API proposal with existing HomeDevicesQoD, draw conclusions and propose a way forward.
...
...
2024/02/21
...
Open
...
Charter Communications
...
Re-assess how much essential is to include site info in the API, and if this info can be removed.
...
...
2024/02/21
...
Open
...
WG delegates
...
Delegates from interested parties to prepare a list of questions for this API, for Nick to answer them.
...
...
2024/02/21
...
Open
...
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
...
Deutsche Telekom
...
to improve and clarify the API proposal, based on discussion during the call.
...
...
2024/02/01
...
Closed
...
Deutsche Telekom
...
to improve and clarify the API proposal, based on discussion during the call.
...
...
2024/02/01
...
Closed
- Discussion
- OGW Drop 3 APIs: 336, 375, 376
- Other APIs: 351, 372, 378, 383
- Governance: 367
- Action Points
- 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
- 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: The minutes are approved.
Recent Updates & Recap
Backlog table
- Table updated in PR#387
Review of Action Points
AP # | AP Owner | AP description | Related issue | Due date | Status |
20230208-04 | Charter Communications | Check potential relationship of this API proposal with existing HomeDevicesQoD, draw conclusions and propose a way forward. | 2024/02/21 | Open | |
20230208-03 | Charter Communications | Re-assess how much essential is to include site info in the API, and if this info can be removed. | 2024/02/21 | Open | |
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 | |
20230125-05 | Deutsche Telekom | to improve and clarify the API proposal, based on discussion during the call. | 2024/02/01 | Closed | |
20230125-04 | Deutsche Telekom | to improve and clarify the API proposal, based on discussion during the call. | 2024/02/01 | Closed |
Discussion
Current Issues
330 | China Unicom | New API proposal: Device Visit Location The API template is available in PR#329 | The issue was discussed in last TSC call (minutes available here). Discussion held, with a proposed way forward captured:
The issue was not treated in this conference call The issue is not eligible to be closed yet. |
336 | Telefónica | New API proposal: OGW Home Location Verification The API template is available in PR#337. Input from OGW Drop 3 | The issue was not treated in this conference call The issue is not eligible to be closed yet. |
351 | Centillion | New Proposal for Authorization for Advertisements, Advertisements Consent, and Measurement The API template is available in PR#386. | The issue was not treated in this conference call DECISION: the discussion will be resumed in a call that Nick (Centillion) is able to join. The issue is not eligible to be closed yet. |
367 | Governance | Adapt Project StructuresAndRoles.MD to changes in API backlog table (reduction of comments) | Progress ongoing, and offline discussion on RACI matrix to WoW among OGW Product, CAMARA APIBacklog and CAMARA TSC. PR pending submission. The issue is not eligible to be closed yet. |
372 | Totogi | New Proposal: Receive SMS No PR available. | Proposal to recover incomes from services CPaaS increase interactivity ACTION: Ailton (Topogi) to fill the template and Backlog governance to review colissions on this. The issue is not eligible to be closed yet. |
375 | Deutsche Telekom | Device Quality Indicator | Jan Friman: Suggest to review the name and better use Device Connection Indication. Noel agreed
DECISION: Move to TSC after name harmonization |
376 | Deutsche Telekom | Best Interconnection | No colission with Edge Selecion API it is a more wide API scope oriented to for example authonomous systems. Focused in fixed lines Jorge: Two codeowners are needed in case a new SG is created (seek for support in that case by DT) DECISION: Move to TSC |
378 | Charter Communications | CPE management | ACTION: Define very crearly the scope of this API and provide focused use cases let that written in the PR#379. The issue is not eligible to be closed yet. |
383 | T-Mobile US | New Proposal: Capability and Runtime Restrictions | Murat (TMUS): showed the proposal:
The issue is not eligible to be closed yet. |
Closed Issues
New Issues
Action Points
AP # | AP Owner | AP description | Related issue | Due date | Status |
Decision Points
DP # | DP description | Related issue |
20230125-02 | the discussion will be resumed in a call that Ailton (Topogi) is able to join. | 372 |
20230125-01 | the discussion will be resumed in a call that Nick (Centillion) is able to join. |
AoB
Next conf. call: 22nd February14th March, 1510-16 11 CET.
Q&A
How does CAMARA API pipeline work?
...