Device Identifier Meeting Minutes 2024-10-04

Owned by Eric Murray
Last updated: Nov 01, 2024
3 min read

Attendees & Representation

NameCompanyAttendee
Eric MurrayVodafone (moderator)

X

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

Agenda

  • Review of previous meeting minutes
    • Approved
  • Review of Device Identifier API status
    • PRs
    • Issues
    • Discussions
  • AOB

Review of Device Identifier API status

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

PRs

New PRs

PR #85: Prepare pre-release r2.1

  • Preparation of release r2.1 for device-identifier v0.2.0-alpha.1

MEETING UPDATE :

  • Leave open for review and comments until at least . Also review if further changes required if Commonalities or ICM announce major changes for Spring25 meta-release.
Existing PRs

PR #78: remove misleading sentence on from where the API can be called

  • Proposal to remove description text stating that API can be called by "an application server or other 3rd party server"
  • Discussion and revision required as the API clearly can be called by an application or other 3rd party server

MEETING UPDATE :

  • Replace references to server with "API consumer"
Closed PRs

PR #83: Add global tag definitions to OAS definition

  • Add global tag definitions to avoid annoying linting warning

MEETING UPDATE :

  • Approved and merged on  

PR #84: Rename CAMARA Mobile Device Identifier API.yaml to device-identifier.yaml

  • Update API filename using convention agreed in Commonalities
  • New name is device-identifier.yaml

MEETING UPDATE :

  • Approved and merged on  

PR #72: Initial Test Definitions for DeviceIdentifier retrieve identifier

  • Proposal for test definitions in response to Issue #68
  • Final review required by more API participants

MEETING UPDATE :

  • Approved and merged on  

PR #73: Add EUDI Wallet and Mobile Device Insurance User Stories

  • Additional user stories for Device Identifier
  • Adds a use case where the physical device itself requests its own IMEI (because OS will not provide it to the app)
  • Review required by API participants

MEETING UPDATE :

  • Approved and merged on  

Issues

New IssuesNone
Existing Issues

Issue #71: Why "The API can be called by an application server or other 3rd party server"

  • Issue associated with PR #78

MEETING UPDATE :

  • < Meeting Update >

Issue #80: Purpose of the lastChecked field in the response?

  • lastChecked response field is not clear to all potential API consumers
  • This is the last time that the API provider checked which IMEI was being used by a specific MSISDN
    • Could be "now", or could be some minutes ago. Implementation dependent.
  • How to fix?
    • Rename field (maybe to lastConfirmed)?
    • Better description in YAML itself?

MEETING UPDATE :

  • Leave issue open for now. Axel Nennker to review how this would be supported by DT.

  • Issue #21: API Definition Terminology

    • Issue is out of date

MEETING UPDATE :

    • To be done after alpha release

ACTIONS:

    • Eric to update issue text (still open)
Closed Issues

Issue #79: Use API name as file name of the the YAML and with the info.title field

  • Naming standard has been informally adopted for meta-release APIs, but not yet formally defined by Commonalities

MEETING UPDATE :

  • Closed by PR #84

MEETING UPDATE  :

    • See PR #72
    • Issue can be closed when above PR is merged

Discussions

New DiscussionsNone
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

MEETING UPDATE :

  • Discussion updated by Axel Nennker with proposal to include PPID as a 3rd device identifier that can be requested (in addition to IMEI or TAC)

MEETING UPDATE :

  • Axel Nennker to review and make proposal for additional physical device identifier
Closed Discussions

None

Other Issues

  • None

AOB

  • Next meeting proposed to be held Friday 1st November 2024 @ 09:00 GMT using Zoom