Device Identifier Meeting Minutes 2024-12-06

PR #87: Update Device object handling and description

• Other APIs passing a Device object do this by passing a separate parameter named device, even if that is the only object passed in the request.
• This PR updates the Device Identifier API to use this pattern. Documentation on identifying the device from the access token is also updated following the current agreement in Commonalities.

MEETING UPDATES

06 Dec 2024:

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

04 Oct 2024 :

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

01 Nov 2024:

• Eric Murray to propose updated description for this field

• Issue #21: API Definition Terminology

  • Issue is out of date

MEETING UPDATES

01 Nov 2024:

• • Still open

ACTIONS:

• • Eric to update issue text (still open)

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 UPDATES:

06 Sep 2024:

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

04 Oct 2024 :

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

01 Nov 2024:

• Waiting for proposal from Axel Nennker