Versions Compared

Old Version 18

changes.mady.by.user Eric Murray

Saved on

compared with

New Version 19

changes.mady.by.user Eric Murray

Saved on

Key

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

DRAFT

Attendees & Representation

NameCompanyAttendee
Eric MurrayVodafone (moderator)

X

Sachin KumarVodafoneX
Kevin SmithVodafone
Alex FerreiraPhronesis
Matthew HornseyPhronesis
Matthew HandPhronesis
Sébastien SynoldIntersec
S, VigneshwaranCognizant
Karthik Raj RethinakumarCognizant
Manish JainCognizant
Huub AppelboomKPNX
Rafal ArtychDT
Abhisek DasInfosys
Brian SmithShabodi
Umair Ali RashidShabodi
Foo Ming HuiSingtel
Vilim DuganicInfobip
Surajj JaggernathVodacomX
Walid TrabelsiSofrecom (Orange)
Aleksander BrankovicIpificationX

Agenda

  • Review of previous meeting minutes
    • < APPROVED >
  • Review of Device Identifier API status
  • IMEI Fraud API status
  • AOB

...

New PRs
Panel
  • PR #59: Create Device Identifier User Story
    • Adds user stories for the Retrieve Device Identifier and Retrieve Device Type use cases

MEETING UPDATE:

    • <Discussion>No comments
Panel
  • PR #60: Update MAINTAINERS.MD
    • Adds github usernames to maintainers file in preparation for more automated sub-project management

MEETING UPDATE:

    • <Discussion>
    • No comments
Existing PRs
None
Closed PRs
None

...

New DiscussionsNone
Existing Discussions
Panel
  • Discussion #36: Alternative device identifiers
    • An alternative proposal is to salt the IMEI with an API consumer specific salt and then hash it
    • This would a less useful identifier (only useful to the API consumer) but easier to justify providing under an opt-out or no consent basis
    • Use cases for such an alternative identifier are not clear

AGREEMENT: Leave discussion open for now, but prioritise returning IMEI / IMEISV

Closed DiscussionsNone

Other Issues

  • None

IMEI Fraud API status

Note

The IMEI Fraud API use case has been referred back to the GSMA OGW Product Workstream for re-evaluation. If the use case is still valid, it will be re-submitted the CAMARA API Backlog WG for re-approval. If approved, a separate repository will be created for the API. Discussions on this API can continue in these meetings if desired.

...

  • Issue #48: Additional sub-project codeowner required
    • UPDATE: No additional codeowner yet identifiedrequired as IMEI Fraud will no longer be part of Device Identifier repository. Issue to be closed.
  • Next meeting proposed to be held Friday 7th June 2024 @ 09:00 BST using Zoom

...