Versions Compared

Old Version 1

changes.mady.by.user Eric Murray

Saved on

compared with

New Version 2

changes.mady.by.user Eric Murray

Saved on

Key

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

DRAFT

Attendees & Representation

...

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

PRs

...

borderColorred
borderStylesolid

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

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

...

...

  • < Meeting Update >

...

PRs

...

Closed PRs


Panel
borderColorred
borderStylesolid

PR #85: Prepare pre-release r1.1

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

MEETING UPDATES

:

  • Release r1.1 now published following Release Management review


Panel
borderColorred
borderStylesolid

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 UPDATES

:

  • Fixed by PR #85 (above)


Existing PRs

None

New 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

:

  • < Meeting Update >


Issues

New IssuesNoneClosed Issues


Panel
borderColorred
borderStylesolid

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

  • Issue associated with PR #78

MEETING UPDATES

:

  • Fixed by PR #85


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.

:

  • < Meeting Update >


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)
Closed Issues
Panel
borderColorred
borderStylesolid

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

  • Issue associated with PR #78

MEETING UPDATES

:

  • Fixed by PR #85

Discussions


New New Issues

None

Discussions

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

:

  • < Meeting Update >


Closed New Discussions

None

Other Issues

  • Meeting times
    • Meeting times must now be anchored to UTC
    • Proposal is to anchor meeting time to 09:00 UTC (current meeting time)

AOB

  • Next meeting proposed to be held Friday 6th December 2024 @ 09:00 UTC using Zoom

...