2024-05-09 API backlog minutes

Attendees


OrganizationName
Orange
Charter Communications

Christopher Aubut Justin Pace

Telefonica
Vodafone
Ericsson
AT&T
DT
T-Mobile US
KDDI
Slagen
Nokia
China Telecom
ZTE
KPN


Agenda Proposal

  • Antitrust Policy
  • Approval of minutes of last conf. call
  • Recent Updates & Recap
  • Review of Action Points
  • Discussion
    • OGW Drop #3 APIs #19 (Device Quality Indicator)

    • OGW Drop #4 APIs: #27 (Verified Caller), #35 (5G New Calling), #34 (Shutdown Service Status), #2 (Tenure)

    • Other APIs:  #17 (Consent and Measurement), #18 (Receive SMS),  #23 (Carrier Wholesale Pricing),  #24 (Steering of Roaming Information), #29 (Call Status), #28 (Device Data Volume)

    • Governance: #4 (Structures and roles, RACI, Maintainers initiative)

  • Clossing Issues
    • #20 (Best Interconnection), #22 (Capability and Runtime Restrictions)

  • 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 **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)
  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: Approved

Recent Updates & Recap

TSC meeting 18th April:

  • 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
    • This issue seems to be under discussion, some companies have commited to make a more relaxed alternative such a sandbox

Other topics

  • New API Backlog GitHub Repo have been created here. Issues have been migrated, PRs will be migrated once they are approved. New PRs and Issues need to be opened in the new repo.

Codeowners:

Anyone else commits to be codeowner?

Next steps:

    • Keep PRs in the old repo and the new PRs will directly need to be opened in the new repo
    • Issues will be moved to the new repo

Backlog table

  • Table updated in PR#38 (merged)

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.

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


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-01Deustche TelekomNoel updating proposal with new fields. Start in parallel while device status API is split375

 

Open
20240411-03Telefonica&DTModify the README for the QualityOnDemand subproject and include the new Scope enhancement402 404

 

Open
20240425-01API Backlog GovernanceTo include Chris as a Codeowner in the new API Backlog Repo--

 

Closed
20240425-02CentillinonNext API Backlog meeting, Nick to bring new use cases and endpoints351

 

Open
20240425-03China TelecomInclude in the template that the scope is not limited to mobile lines and the shared slides in the template as supporting documents409

 

Closed

Discussion

Current Issues 

17 CentillionNew Proposal for Authorization for Advertisements, Advertisements Consent, and Measurement
The API template is available in PR#386.


  • AP 20230208-01 still open.

The issue is not eligible to be closed yet.

Nick will be working within next weeks on providing what camara can work on within this API


ACTION: Next API Backlog, Nick will bring new use cases and endpoints

Not treated, to be handled in nex meeting (look at APs)

4

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.

Ricardo is currently working on modeling a new table

New WoW 3 companies needed

Nick propose to focus more in the Commercial viability of the proposal in orther to rise up interest of other companies

Huub points out the sensibility of posting commercial strategies within this type of forums as many companies are potential competitors

The issue is not eligible to be closed yet.

18TotogiNew Proposal: Receive SMS
The API template is available in PR#391

This issue was not treated in this conference call

The issue is not eligible to be closed yet.

DECISION: not treated

to be treated in following session

19

Deutsche Telekom

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

Noel proposed Device Status subgroup to integrate their APIs within Noel's. Noel to make the proposal to the API Backlog and provide update

Two proposals Isue 375 and 412 would be integrating within the Device Status subproject

The issue is not eligible to be closed yet.

to be treated in following session

23

TelecomsXChange

New Proposal: Carrier Wholesale Pricing
The API template is available in PR#393

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

to be treated in following session

24

Netfocusin Technologies

New Proposal: Steering of Roaming Management
The API template is available in PR#398


Does not seem to be in the Scope of Camara. 

DECISION: Discuss this in the next meeting (whenever Netfocusin Technologies is able to connect)


to be treated in following session

27 

China Telecom

New API proposal: Verified Caller 

The API template is available in PR#410

Input from OGW Drop 4

Additional information in PR#418

Eric: Is the initial customer making a call to the API to show the brand to clients?

Jason: Yes, it would be eg the hospital or the bank.

Not limited to mobile lines.

Start by API aproach and then include de registration flows and interworkings

All the information need to be preprovided in the systems for the API to work (templates)

Verified call can not be spufed or faked by criminals as there is the mobile number


ACTION: Include in the template that the scope is not limited to mobile lines →  Solved

ACTION: Include the shared slides in the template as supporting documents → Solved


DECISION: Ready for closing, to be brought to TSC for approval.

28

Deutsche Telekom

New API Proposal: Device Data Volume

New template in PR#39

The Template was merged by mistake PR#411, The PR needs to be updated

The two APIs will be treated as new proposals that will be presented to the TSC when ready in BL

ACTION: Reopen the closed pull request or make a new one with the existing files → solved

To be treated in next session

29

Rogers

New API Proposal: Call Status

Nicholas to update template in PR, clarify in the issue whether this proposal come from GMSA and review existing API linked by noel in the issue

To be treated in next session

2

Vodafone

New API Proposal: Tenure

The API template is availale in PR#1

Input from OGW Drop 4

Reviewed, including existing yaml proposal. 

Proposal to become part of a separate repo/subproject considering that it owns enough supporters, proposal to get the API for approval

ACTION: to check with KDDI (KYC family owner) if this APi discussions can fit in the KYC meeting, due to the similarity in use cases.


Decision: move for approval, to be treated in following TSC

34

China Unicom

New API Proposal: Shutdown ServiceStatus

The API tempate is available in PR#32

Not treated

(relations with device status to be considered)


To be treated in next session

35

China Mobile

5G New Calling

The API template is available PR#31

Not treated


To be treated in next session

Closing Issues

20

Deutsche Telekom

Best Interconnection
The API template is available in PR#381
Input from OGW Drop 3

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

22

T-Mobile US

Capability and Runtime Restrictions
The API template is available in PR#384

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

Closed Issues

Issue

Owner

API

Repository

5

China Unicom

Device Visit Location

Location Insights

16

Telefonica

Most Frequent Location

Location Insights

21

Charter

CPE Management

Network Access Management

New Issues

37VodafoneMove Simple Edge Discovery to own repositoryClosed, moved to new separate repo.

Action Points

AP #

AP Owner

AP description

Related issue

Due date

Status

20240509-01VodafoneTo check with KDDI (KYC family owner) if this APi discussions can fit in the KYC meeting, due to the similarity in use cases.29/05/2024Open

Decision Points

DP #

DP description

Related issue

20240509-01

Verified Caller API move for approval, to be treated in following TSC

27

20240509-02

Tenure API move for approval, to be treated in following TSC

2


AoB

Next Backlog conf. call: 23th May, 15-16 UTC+2.

Next TSC conf. call: 16th May, 16-17,30 UTC+2

Q&A

How does CAMARA API pipeline work?

The pipeline consists of FOUR stages:
A. Submission of the API proposal.
B. Evaluation of the API proposal.
C. API proposal voting & decision.
D. Sub-Project setup.

The following clauses provides details on individual stages.

Stage A: Submission of the API proposal

Participants: API owner.
Description: The proccess is detailed here. To proceed with the submission, the API owner shall follow these steps:

  1. Fill in the template available here and save it with the following name: "APIproposal_<APIname>_<owner>. md" locally.
  2. Create a new issue in the API Backlog Working Group repository, labeled with "API Backlog".
  3. Upload the filled-in template to GitHub repository folder for API proposals via Pull Request. This Pull Request shall be associated to the issue created in the previous step.


Stage B: Evaluation of the API proposal

Participants: API owner, API backlog WG.
Description: The proccess is detailed here. Upon submission, the API owner will present the proposal in the next API backlog WG meeting, to socialize it with the rest of partners. In paralell..

  1. The WG chair checks that the template is duly filled in. Otherwise, the API owner is requested to provide missing information.
  2. After this sanity check, each WG participant declares their support. If a company wants to become supporter of an API, then a delegate of this company needs to add the company's name in the 'supporters' column in the API backlog table. The more support an API proposal gets, the better (it may get more traction).
  3. When the API owner considers the API proposal is in good shape to go for approval, it informs the WG chair accordingly.
  4. Upon receiving this information, the WG chair merges the Pull Request into the main branch, and sends the API proposal to the Technical Steering Committee (TSC) of CAMARA. This action shall be completed at least one week prior to the TSC meeting where the API proposal will be voted upon.

The whole procedure (steps 1-4) should be done within 2 regular meetings of the API Backlog WG. Nonetheless, it is up to the API owner to decide if it wants to shorten or extend this time period.


Stage C: API proposal & voting decision

Participants: TSC.
Description: The proccess is detailed here. Upon receiving the API proposal and notification from the API backlog WG chair, the TSC studies the proosal and votes it at the next TSC meeting.

NOTE 1: Possible decisions outcomes:

  • Not Accepted: The API proposal is rejected, and thus will not be included in any API Sub-Project. The TSC will need to inform the API backlog WG of this decision, and clarify next steps: either (1) remove this API proposal from backlog, with objecting companies providing justifications why; or (2) ask for changes (e.g., clarifications, corrections, gaps to be addressed) required in order for the API to be re-submitted by the API supporters.
  • Accepted: In this case, the TSC shall specify whether the API proposal is to be hosted by a new or existing Sub Project.

NOTE 2: The TSC may also propose changes to an API proposal and take the decision considering these changes. The TSC documents the decision in the CAMARA API overview list (fills in columns TSC date and TSC decision / Sub Project; in case of a No-Go "Rejected" is documented there).


Stage D: Sub-Project setup

Participants: API backlog WG, TSC, CAMARA admin team
Description: If an API proposal is accepted and there is a neeed to open a new Sub-Project, the following steps are needed:

  1. Supporting companies propose their initial maintainers to be added for the Sub-Project. The API backlog WG chair centralizes this information, and sends it to the TSC.
  2. The TSC will use this input to oficially nominate the initial maintainers by next TSC meeting.
  3. The CAMARA admin team creates the Sub-Project repository.

NOTE: After the initial maintainers are nominated, the criteria for further maintainers would be three months of active contribution to the sub project. Code owners are to be decided by the maintainers within the subproject.