Date

Dec 17, 2024

Attendees & Representation

Community: @Jose Luis Urien Pinedo @Cetin Alpaycetin @Joachim Dahlgren @Ludovic Robert@Akos Hunyadi @Rafal Artych @Javier Carro @Rafal Artych @Maximilian Laue @Surajj Jaggernath

Agenda

Antitrust Policy

• Approve previous meeting minutes

  • Approved

• Open issues and PRs

Minutes

Spring25 Meta-release

• Created API trackers for the current 3 APIs, but next versions tbd

  • location-verification will be 1.1 or 2.0 depending on whether back-compatibility is broken

    • It seems that alignment with Commonalities implies a new major version

      • Global decision at CAMARA level must be probably reached

  • geofencing-subscriptions to be 0.4 due to the lack of any implementation certified GSMA

  • location-retrieval could be upgraded to stable but no one was particularly interested right now. We are also adding the new functionality for maxSurface and it would be good to have some feedback from customers

    • Are we all OK with targeting version 0.4 for it?

      • Initial: Orange, Telefonica, DT

      • Stable: Ericsson

      • No preference from Vodafone

      • No a formal decision is required as of now

• An issue per API created:

  • Scope of location-verification API for Spring25 Meta Release

  • Scope of location-retrieval API for Spring25 Meta Release

  • Scope of geofencing-subscriptions API for Spring25 Meta Release

• We have to create a new PR per API with all changes from Commonalities and ICM

  • Update info.description with commonalities

    • Is the update required for Geofencing?

  • Error Alignement with Commonalities

    • New error format with enums

    • New and updated error codes

      • Waiting decision in Commonalities about which errors to remove (5xx…) (issue Should errors 405, 415, 500, 501, 502, 503, 504 be listed in CAMARA_common.yaml · Issue #355 · camaraproject/Commonalities)

  • Update geofencing-subcriptions to new guidelines for subscriptions and events

  • Split the work:

    • @Jose Luis Urien Pinedo has started working on location-verification

    • @Ludovic Robert will work for location-retrieval

    • @Maximilian Laue will work for geofencing

Open topics for Spring25

• Update location-retrieval with add maxSurface management

  • Ready but we will wait before to merge to avoid collision with Meta release patch

  • Can we merge now?

    • Have a last formal review - we updated live the version in the url (vwip)

• Support of Multi-SIM lines in DeviceLocation APIs

  • Review new proposal by @Javier Carro

• Define guidelines for geofencing implementation

  • Last comment by @Maximilian Laue

    • Conversation restarted

      • Perhaps we should restrict to LOOSE & STRICT enum

• Discussion on the minimum radius on Geofencing & Location verification

  • @Maximilian Laue will raise an issue to frame discussion

Other topics

• [Retrieval] Unable to build Location object for /retrieve response

  • No further interaction

  • Close?

• Discuss data minimization for geofencing event

  • Following issue camaraproject/Commonalities#295

  • Review status, in scope for Spring25?

Backlog

• API enhancement - Support of landlines

  • This is not a short/medium term requirement for Telefonica - no prioritized for other company.

  • We keep for feature for future consideration

• Location subscription API

  • discussed:

    • Should be proposed first to API Backlog Working Group

    • Any supporters? As of now no.

Release patch r1.3

• It has been decided to skip the patch r1.3 due to the lack of relevant fixes.

  • If something important is reported in the future we will create a dedicated branch for it

  • Issue created to have a tracking: Scope for potential patch r1.3

AOB

Action items

Next meeting

Proposal

• Skip meeting on December 31st

• Next week on January 14th, following regular schedule