...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Attendees
GSMA | Helene Vigue |
Charter Communications | Chris Aubut, Justin Pace |
Ericsson | Jan Friman |
Nokia | Tanja De Groot |
Telefónica | Ricardo Serrano Gutierrez (Chairing) Ignacio Dominguez Martinez Jorge Garcia Hospital Javier Villa Labarra |
Vodafone | Kevin Smith |
T-Mobile US | Karabulut, Murat |
Netcheck | Sanjeev Shankar |
?Huawei | Kai Zhang |
IPification | Alex |
AT&T | Pierre Close |
Orange | Ludovic Robert |
ZTE | Hans Neff |
Vonage | James Emerson |
...
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
...
Approval of minutes of last conf. call
- Minutes of last API backlog WG call available here
- DECISION: minutes are aproved.
Recent Updates & Recap
Backlog table
- Table updated in PR#396
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 | OpenClosed | ||||||||||
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 | Closed | ||||||||||
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 | ||||||||||
2023012520240222-0501 | 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 | Topogi | To fill the API template and create the Proposal PR. Backlog Governance to review colissions on this API. | 2024/03/13 | Closed |
Discussion
Current Issues
330 | China Unicom | New API proposal: Device Visit Location The API template is available in PR#329 | 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 MeasurementNew API proposal: OGW Home Location Verification The API template is available in PR#386.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. |
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. From the shared RACI in the meetingit mainly aplies the step 7 and the three colums from the right. The main idea is that any change in the scope of the APIs is brought to the Backlog subgroup for approval (shame as if it was a new API) as the scope is responsibility of the Backlog (in the aproval and in the ongoing of the working group) The issue is not eligible to be closed yet. ACTION: Ricardo to share the RACI in the issue 367 comments, make CAMARA specific | ||||
372 | Totogi | New Proposal: Receive SMS The API template is available in PR#391 | 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 | ||||
376 | Deutsche Telekom | Best Interconnection. | |||||
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. | ||||
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. It was socialized the WoW RACI. From the RACI shared in the meeting it mainly aplies the step 7 and the three colums from the right (CAMARA). The main idea is that any change in the scope of the APIs is brought to the Backlog WG for approval (shame process as if it was a new API) as the scope is responsibility of the Backlog (in the aproval and in the ongoing of the working group). This RACI will be brough to TSC for validation. ACTION: Ricardo to share the RACI in the issue 367 comments, after making CAMARA specific document and validation by TSC The issue is not eligible to be closed yet. | ||||
372 | Totogi | New Proposal: Receive SMS The API template is available inCPE management PR#381 Input from OGW Drop 3 | 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 | PR#391 |
The issue was not treated in this conference call The issue is not eligible to be closed yet. |
375 | Deutsche Telekom | Device Quality Indicator |
ACTION: Write in the API template the scope of the API that have been provided as a comment in the PR#379. DECISION: Move to TSC once the template is completed with the previous AP | 383 | T-Mobile US | PR#380 | 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 |
376 | Deutsche Telekom | Best Interconnection | Murat (TMUS): showed the proposal:
Is is better to treat this in the commonalities SG as this may affect to all the APIs? DECISION: Bring this issue to the TSC for discussion The issue is not eligible to be closed yet. |
Closed Issues
New Issues
395 | TelecomsXChange | New Proposal: Carrier Wholesale PricingPR#381 | 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 First YAML avaliable here |
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
...
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
...
Charter Communications
...
Define very crearly the scope of this API and provide focused use cases let that written in the PR#379.
...
...
2023/02/13
...
Open
...
Topogi
...
To fill the API template and create the Proposal PR. Backlog Governance to review colissions on this API.
...
...
2024/03/13
...
Open
Decision Points
DP # | DP description | Related issue | |
20230125-01 | the discussion will be resumed in a call that Nick (Centillion) is able to join. | ||
20240222-02 | Charter Communications provided comments to the PR regarding the scope (scope will be the use cases proposed in these comments) ACTION: Write in the API template the scope of the API that have been provided as a comment in the PR#379. DECISION: Move to TSC once the template is completed with the previous AP | ||
383 | T-Mobile US | Capability and Runtime Restrictions |
Is is better to treat this in the commonalities SG as this may affect to all the APIs? DECISION: Bring this issue to the TSC for discussion The issue is not eligible to be closed yet. |
Closed Issues
New Issues
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. |
Action Points
AP # | AP Owner | AP description | Related issue | Due date | Status |
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 |
20240314-02 | Charter Communications | Write in the API template the scope of the API that have been provided as a comment in the PR#379. | 378 | 2024/03/14 | Open |
Decision Points
DP # | DP description | Related issue |
20240314-01 | CPE management API proposal to move foward TSC once the template is compliance with the AP 20240314-02 | |
20240314-02 | Bring this issue to the TSC for discussion as it may fit in the commonalities WG | |
20240222-01 | Device Quality Indicator to move foward to TSC for aproval (wait till April 4th) | |
20240222- |
02 | Best |
Interconnection to move foward to TSC for aproval (wait till April 4th) |
AoB
Next Backlog conf. call: 28th 27th March, 15-16 CET.
Next TSC conf. call: 21st March, 16-15 CET
Q&A
How does CAMARA API pipeline work?
...