...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Attendees
Organization | Delegates |
---|---|
AT&T | Pierre Close |
CableLabs | Randy Levensalor |
Charter Communications | Chris Aubut, Justin Pace, Jason Page |
Deutsche Telekom | Noel Wirzius |
Ericsson | Jan Friman |
Infosys | Chintan Lodariya |
Huawei | Zhang Kai |
Nokia | Tanja De Groot |
Telecom Italia | Fabrizio Moggio |
Telefónica | Jose Ordonez-Lucena, Jorge García Hospital |
Vodafone | Eric Murray, Kevin Smith |
...
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: The minutes are approved.
Recent Updates & Recap
Technical Steering Committee (TSC)
- Last TSC call held on Jan 18th. Minutes available here.
- "Device Location retrieval API proposal" was approved
- ongoing in Device Location repo → issue 343 is closed
- "Network Slicing API proposal" was approved
- TSC noted that the proposed sub-project name "on-demand network slicing" was not appropriate. They asked backlog WG to decide on a new sub-project name.
- Two options for the sub-project name: 1) Network Slicing Booking; 2) Network Slicing Reservation.
- Huawei has commented their preference to option 1.
Backlog table
- Table updated in PR#382
Review of Action Points
AP | Owner | Description | Issue | Due Date | Status |
---|---|---|---|---|---|
20240111-04 | Telefónica | Open a new PR to update governing document for API submission pipeline | 2024/02/15 | Open | |
20240111-03 | WG operators | Post position on what the scope (mobile-only or mobile+fixed) of "Call Forwarding" API should be | 2024/01/24 | Not pursued | |
20240111-02 | China Unicom, Orange | Submit PRs for their companies to become supporters of the Call Forwarding API | 2024/01/24 | Closed | |
20240111-01 | China Unicom | Update the API template on Network Slicing, clarifying the issues covered in the deck and questions covered in the call. | 2024/01/12 | Closed |
Discussion
Current Issues
Issue | Owner | Description | Discussion |
---|---|---|---|
317 | China Unicom | New Proposal: Network Slicing API |
DECISION: "Network Slice Booking" is the sub-project name. ACTION: WG chair to inform TSC on the decision, so that CAMARA admin can proceed with the repo creation. The issue is not eligible to be closed yet. |
330 | China Unicom | New API proposal: Device Visit Location The API template is available in PR#329 | The issue was not treated in this conf. 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 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#350. | No delegate from Centillion attended. The issue was not treated in this conf. call. The issue is not eligible to be closed yet. |
359 | Telecom Italia | New API proposal: Call Forwarding Signal |
DECISION: API proposal is WG endorsed. The proposed Sub-Project name is Call Forwarding Signal. ACTION: to send out information to TSC, asking for API approval. ACTION: to seek codeowners/maintainers from Orange and China Unicom. The issue is not eligible to be closed yet. |
367 | Governance | Adapt Project StructuresAndRoles.MD to changes in API backlog table (reduction of comments) | The issue was not treated in this conference call. No progress. The issue is not eligible to be closed yet. |
372 | New Proposal: Receive SMS No PR available. | The issue was not treated in this conference call. The issue is not eligible to be closed yet. |
...
Issue | Owner | Description | Discussion |
---|---|---|---|
343 | Orange | New API proposal: Device Location Retrieval The API template is available in PR#366. | The API definition is ongoing in Device Location repo. |
...
Issue | Owner | Description | Discussion |
---|---|---|---|
375 | Deutsche Telekom | Device Quality Indicator |
ACTION: to improve and clarify the API proposal, based on discussion during the call. The issue is not eligible to be closed yet. |
376 | Deutsche Telekom | Best Interconnection |
ACTION: to improve and clarify the API proposal, based on discussion during the call. The issue is not eligible to be closed yet. |
378 | Charter Communications | CPE management | Charter Communications presented a slide deck to elaborate on API proposal. There was no time to really discuss the topic, since we ran out of time . We will resume the discussion next call. ACTION: to submit the deck here, and link it to the issue. The issue is not eligible to be closed yet. |
Action Points
AP | Owner | Description | Issue | Due Date | Status |
---|---|---|---|---|---|
20230125-06 | Charter Communications | o submit the deck here, and link it to the issue. | 2024/02/01 | Open | |
20230125-05 | Deutsche Telekom | to improve and clarify the API proposal, based on discussion during the call. | 2024/02/01 | Open | |
20230125-04 | Deutsche Telekom | to improve and clarify the API proposal, based on discussion during the call. | 2024/02/01 | Open | |
20230125-03 | Telecom Italia | to seek codeowners/maintainers from Orange and China Unicom. | 359 | 2024/02/07 | Open |
20230125-02 | Telefónica | To send out information to TSC, asking for API approval. | 359 | 2024/01/25 | Open |
20230125-01 | Telefónica | To inform TSC on the decision of Sub-Project name, so that CAMARA admin can proceed with the repo creation | 317 | 2024/01/25 | Open |
Decision Points
DP | Description | Issue |
---|---|---|
20230125-02 | API proposal is WG endorsed. The proposed Sub-Project name is Call Forwarding Signal. | |
20230125-01 | "Network Slice Booking" is the sub-project name. |
AoB
Next conf. call: 8th February, 10-11 CET.
Q&A
How does CAMARA API pipeline work?
...