DRAFT MINUTES
Attendees
...
DRAFT MINUTES
Attendees
| Organization | Name |
| Orange | |
| Charter Communications | |
| Telefonica | |
| Vodafone | |
| Vodafone | |
| Ericsson | |
| AT&T | |
| DT |
Agenda Proposal
- Antitrust Policy
- Approval of minutes of last conf. call
- Recent Updates & Recap
- Review of Action Points
- Discussion )API Scope evolution: #402 #404 (QoD subgroup scope Change
- Closing Issues
- Action Points
- AOB
- Q&A
Antitrust Policy
...
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 5th 18th April:
- The API Backlog subgroup will have its own github repo. Initial Maintainers have been requested. Those of you that have been active within the last meetings have received an email requesting for comitment/refusal:
Name Company Commits? Ricardo Serrano Telefonica YES/CO Eric Murray Vodafone YES Pierre Close ATT NO Randy Levensalor CableLabs Chris Aubut Charter Communication YES Noel Wirzius Deutsche Telekom YES/CO Jan Friman Ericsson Mark Cornall GSMA YES Zhang Kai Huawei Tanja De Groot Nokia Ludovic Robert Orange YES Nitin Sood Schabodi Jorge Garcia Hospital Telefonica YES/CO Javier Villa Labarra Telefonica NO Kevin Smith Vodafone
- There was no time to treat the API proposals.
- Only CPE management: Need to decide the name and transmit this to the TSC for the subproject to be created (offline) → The TSC is aware of the proposal: Home Devices - Network Access Management
Other topics
- The subgroups are being created: Network Access Management, Most Frequent Location, Device Visit Location (Location Insights family will have the same mail adress but separated repos)
- In the sake of the health of the CAMARA group, so that the projects do not lose their activity as soon as they are born, it will be proposed that in order to approve new API proposals, these must be supported by at least 3 companies (MNO or suppliers indistinctly). An issue will be opened within governance encompassing this. TSC will take a decission next meeting
Other topics
- New API Backlog GitHub Repo have been created here. Ricardo → To migrate repos
Codeowners:
- NoelWirzius
- Jorge Garcia Hospital
- Ricardo Serrano Gutierrez
Anyone else commits to be codeowner?
Backlog table
- Table updated in PR#406
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-02 | API Backlog Governance | Approve ScopeEnhancementAPI proposal for QoD (PR#403) | 402 404 |
| Open. PR is approved. needs to be merged |
| 20240411-03 | Telefonica&DT | Modify the README for the QualityOnDemand subproject and include the new Scope enhancement | 402 404 |
| Open |
Discussion
Current Issues
| 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
The issue is not eligible to be closed yet. DECISION: not treated | ||
| 367 | Governance | Adapt Project StructuresAndRoles.MD to changes in API backlog table (reduction of comments) | The RACI was presented to the TSC and there was no objection anyhow explicit approval is not reflected in the TSC Minutes 21/03 It is assumed RACI and so new WoW as approved This way of work have been firstly adopted by the QoD subgroup which is proposing a scope change in the Working Group issues (#404 and #403) which may be treated in the next conference call The API Backlog subgroup will have its own github repo. Initial Maintainers have been requested. Those of you that have been active within the last meeting have received an email requesting for commitment/refusal: Ricardo is currently working on modeling a new table The issue is not eligible to be closed yet. | ||
| 372 | Totogi | New Proposal: Receive SMS The API template is available in PR#391 |
The issue is not eligible to be closed yet. DECISION: not treated | ||
| 375 | 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 The issue is not eligible to be closed yet. ACTION: AP: Noel updating proposal with new fields. Start in parallel while device status API is split | ||
| 395 | 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 treated | ||
| 397 | 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) | ||
Telefonica&DT | Scope Change: QoD API409 | China Telecom | New API proposal: Verified Caller The API template is available in PR#403 Noel: (mobileQoD to QoD change) Consider the combination or relationship between QoD and CPE/Home Devices subproject Eric: (provision) difficult to ensure a pfile characteristic (throughput, latency) for a long time. Let's discuss in the subgroup. Also, shall same mechanism apply to HomeQoD? to be brought tto Home QoD subgroup. DECISION: Both approvedPR#410 Input from OGW Drop 4 | ||
Deutsche Telekom | New API Proposal: Device Data Volume | The Template was merged by mistake PR#411, The PR needs to be updated |
Closing Issues
| 330 | China Unicom | New API proposal: Device Visit Location The API template is available in PR#329 | China Unicom and Telefonica to create a single family for both API: Location Insights, Use historical informations to manage location information of the user. LOCATION INSIGHTS FAMILY:
| ||||
| 336 | Telefónica | New API proposal: OGW Home Location Verification The API template is available in PR#337. Input from OGW Drop 3 | China Unicom and Telefonica to create a single family for both APIs: Location Insights, Use historical informations to manage location information of the user. TIM is supporting Home Location Verification but changing the name so to reach a wider scope.
| ||||
| 376 | 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 TSC | ||||
| 378 | Charter Communications | CPE management | CPE Management API proposal was approved by TSC. Ricardo has to provide the CODEOWNERS and initial MAINTAINERS to the TSC. This have been provided within Issue#378_comment HomeDevicesQoD owners queried to have this API in a separated github project despite having regular meetings to align common terms (API Family). This involves having more than one CODEOWNER for this API (no further problem) New github subproject to be created: Home Devices - Network Access Management DECISION: GiutHub repo name approved | 383 | 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 callDECISION: GiutHub repo name approved |
| 383 | 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 | ||||
Telefonica&DT | Scope Change: QoD API The API template is available in PR#403 | Noel: (mobileQoD to QoD change) Consider the combination or relationship between QoD and CPE/Home Devices subproject Eric: (provision) difficult to ensure a pfile characteristic (throughput, latency) for a long time. Let's discuss in the subgroup. Also, shall same mechanism apply to HomeQoD? to be brought tto Home QoD subgroup. DECISION: Both approved |
New Issues
Action Points
| AP # | AP Owner | AP description | Related issue | Due date | Status |
| 20240411-01 | Deustche Telekom | Noel updating proposal with new fields. Start in parallel while device status API is split | 375 |
| Open |
| 20240411-02 | API Backlog Governance | Approve ScopeEnhancementAPI proposal for QoD (PR#403) | 402 404 |
| Open |
| 20240411-03 | Telefonica&DT | Modify the README for the QualityOnDemand subproject and include the new Scope enhancement | 402 404 |
| Open |
Decision Points
| DP # | DP description | Related issue |
| 20240411-01 | Scope Change: QoD API. Both issues are approved (merge the ScopeChange proposal) | 402 404 |
| 20240327-04 | Discuss this in the next meeting (whenever Netfocusin Technologies is able to connect) |
...
AoB
Next Backlog conf. call: 25th April9th May, 15-16 CET10-11 UTC+2.
Next TSC conf. call: 18th April2nd May, 17-18 CET10-11,30 UTC+2
Q&A
How does CAMARA API pipeline work?
...