Versions Compared

Version Old Version 1 New Version 2
Changes made by

Eric Murray

Eric Murray

Saved on

Key

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

DRAFT

Attendees & Representation

...

Closed PRs


Panel
borderColorred
borderStylesolid

PR #86: Reset device-identifier.yaml version to "wip"

  • Reset YAML version to wip following 0.2.0-alpha.1 release

MEETING UPDATES

:

  • Already approved and merged


Existing PRs

None

New PRs


Panel
borderColorred
borderStylesolid

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

:

  • < Meeting update >


Issues

Closed Issues


Existing Issues


Panel
borderColorred
borderStylesolid

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

:

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

:

  • Eric Murray to propose updated description for this field


Panel
borderColorred
borderStylesolid

  • Issue #21: API Definition Terminology

    • Issue is out of date

MEETING UPDATES

:

    • Still open

ACTIONS:

    • Eric to update issue text (still open)


New Issues

None

...

Closed DiscussionsNone
Existing Discussions


Panel
borderColorred
borderStylesolid

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:

:

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

:

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

:


New Discussions

None

Other Issues

  • None

AOB

  • Next meeting proposed to be held Friday 3rd January 2025 @ 09:00 UTC using Zoom

...