Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


DRAFT MINUTES

Attendees

...

Chris Aubut,

 Justin Pace

Jason Page

...

Nitin Sood

...

Wirzius, Noel

...

Ricardo Serrano Gutierrez

Laura Lacarra Arcos

Javier Villa Labarra 

Lukas Wiegandt

Jorge Garcia Hospital

...

Dagoberto Garavito

...

Lyle Bertz

Karabulut, Murat

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:

  1. 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.
  2. New schedule of conf. calls
    • 2nd Thursday of the month (10-11 CET)
    • 4th Thursday of the month (15-16 CET)
  3.  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

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. 

...

378

...

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. 

...

378

...

2024/02/21

...

Open

...

WG delegates

...

Delegates from interested parties to prepare a list of questions for this API, for Nick to answer them.

...

351

...

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.  

...

351

...

2024/02/21

...

Open

...

Deutsche Telekom

...

to improve and clarify the API proposal, based on discussion during the call.

...

376

...

2024/02/01

...

Closed

...

Deutsche Telekom

...

to improve and clarify the API proposal, based on discussion during the call.

...

375

...

2024/02/01

...

Closed

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 was not treated in this conference call

The issue is not eligible to be closed yet.

...

The issue was not treated in this conference call

The issue is not eligible to be closed yet.

...

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.

...

Governance

...

Adapt Project StructuresAndRoles.MD to changes in API backlog table (reduction of comments)
The aim is to update the governing document to reflect on the updated changes on API submission pipeline, according to the new structure of the API backlog table.

...


DRAFT MINUTES

Attendees


CableLabsRandy Levensalor
Charter Communications

Chris Aubut,

 Justin Pace

Jason Page

EricssonJan Friman
GSMAMark Cornall
NokiaTanja De Groot
Shabodi

Nitin Sood

Telekom

Wirzius, Noel

Telefónica

Ricardo Serrano Gutierrez

Laura Lacarra Arcos

Javier Villa Labarra 

Lukas Wiegandt

Jorge Garcia Hospital

TotogiAilton Santana
VodafoneEric Murray
Slagen

Dagoberto Garavito

T-Mobile US

Lyle Bertz

Karabulut, Murat


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.


 

Image Added

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:

  1. 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.
  2. New schedule of conf. calls
    • 2nd Thursday of the month (10-11 CET)
    • 4th Thursday of the month (15-16 CET)
  3.  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

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. 

378

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. 

378

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.

351

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.  

351

2024/02/21

Open

20230125-05

Deutsche Telekom

to improve and clarify the API proposal, based on discussion during the call.

376

2024/02/01

Closed

20230125-04

Deutsche Telekom

to improve and clarify the API proposal, based on discussion during the call.

375

2024/02/01

Closed

Discussion

Current Issues 

330China UnicomNew 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.


336TelefónicaNew 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.

351CentillionNew 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 

  • AP 20230208-01 still open.

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 aim is to update the governing document to reflect on the updated changes on API submission pipeline, according to the new structure of the API backlog table.

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.

372TotogiNew 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
The API template is available in PR#380
Input from OGW Drop 3

Jan Friman: Suggest to review the name and better use Device Connection Indication. Noel agreed

  • AP 20230125-05 still open.

DECISION: Move to TSC after name harmonization (This was done before the Call ended)

376

Deutsche Telekom

Best Interconnection
The API template is available in 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

CPE management
The API template is available in PR#379.       First YAML available here.

  • AP 20230208-04 still open

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
The API template is available in PR#384


Murat (TMUS): showed the proposal:

The issue is not eligible to be closed yet.

372

Closed Issues

...

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.

...

Deutsche Telekom

...

Device Quality Indicator
The API template is available in PR#380
Input from OGW Drop 3

...

Jan Friman: Suggest to review the name and better use Device Connection Indication. Noel agreed

  • AP 20230125-05 still open.

DECISION: Move to TSC after name harmonization

...

Deutsche Telekom

...

Best Interconnection
The API template is available in 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

...

Charter Communications

...

CPE management
The API template is available in PR#379.       First YAML available here.

...





...

New Issues






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. 

378

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.

351

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.  

351

2024/02/21

Open

20240222-02

Charter Communications

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
The API template is available in PR#384

Murat (TMUS): showed the proposal:

The issue is not eligible to be closed yet.

Closed Issues

New Issues

Action Points

Status
AP #

AP Owner

AP description

Related issue

Due date

written in the PR#379.   

378

2023/02/13

Open

20240222-01

Topogi

To fill the API template and create the Proposal PR. Backlog Governance to review colissions on this API.

372

2024/03/13

Open

Decision Points

DP #

DP description

Related issue

20230125-
02
01

the discussion will be resumed in a call that

Ailton

Nick (

Topogi

Centillion) is able to join.

37220230125-01

the discussion will be resumed in a call that Nick (Centillion) is able to join. 

351

 

351

20240222-02

Device Quality Indicator to move foward to TSC for aproval

375

20240222-01

Best Interconnection to move foward to TSC for aproval

376


AoB

Next conf. call: 14th March, 10-11 CET.

Q&A

How does CAMARA API pipeline work?

...