/
Device Identifier Meeting Minutes 2024-05-03

Device Identifier Meeting Minutes 2024-05-03

Owned by Eric Murray
Last updated: Jun 07, 2024
2 min read

Attendees & Representation

Name

Company

Attendee

Name

Company

Attendee

Eric Murray

Vodafone (moderator)

X

Sachin Kumar

Vodafone

X

Kevin Smith

Vodafone

ย 

Alex Ferreira

Phronesis

ย 

Matthew Hornsey

Phronesis

ย 

Matthew Hand

Phronesis

ย 

Sรฉbastien Synold

Intersec

ย 

S, Vigneshwaran

Cognizant

ย 

Karthik Raj Rethinakumar

Cognizant

ย 

Manish Jain

Cognizant

ย 

Huub Appelboom

KPN

X

Rafal Artych

DT

ย 

Abhisek Das

Infosys

ย 

Brian Smith

Shabodi

ย 

Umair Ali Rashid

Shabodi

ย 

Foo Ming Hui

Singtel

ย 

Vilim Duganic

Infobip

ย 

Surajj Jaggernath

Vodacom

X

Walid Trabelsi

Sofrecom (Orange)

ย 

Aleksander Brankovic

Ipification

X

Agenda

  • Review of previous meeting minutes

    • APPROVED

  • Review of Device Identifier API status

  • IMEI Fraud API status

  • AOB

Review of Device Identifier API status

  • Current "work in progress" version can be found here

PRs

New PRs

  • PRย #59: Create Device Identifier User Story

    • Adds user stories for the Retrieve Device Identifier and Retrieve Device Type use cases

MEETING UPDATE:

  • ย 

    • No comments

  • PRย #60: Update MAINTAINERS.MD

    • Adds github usernames to maintainers file in preparation for more automated sub-project management

MEETING UPDATE:

  • ย 

    • No comments

Existing PRs

None

Closed PRs

None

Issues

New Issues

None

Existing Issues

  • Issueย #21: API Definition Terminology

    • Issue is out of date

ACTIONS:

  • ย 

    • Eric to update issue text (still open)

Closed Issues

None

Discussions

New Discussions

None

Existing Discussions

  • 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 Discussions

None

Other Issues

  • None

IMEI Fraud API status

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.

See API Proposal submission here.ย For MTN proposal for the initial YAML, seeย here.

Open Discussions:

  • #37: IMEI Fraud API Input

    • Proposal is just to use a single "IMEI" field, which would accept either IMEI or IMEISV

  • 34: What values should the IMEI Fraud API respond with to indicate reported ownership status?

    • The GSMA appear to have an existingย Device Checkย service, which includes anย API. How does the CAMARA proposal differ from this?

    • Kevin highlighted a GSMAย video on their Device Check service.

AOB

  • Issue #48: Additional sub-project codeowner required

    • UPDATE:ย No additional codeowner required 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

ย