Versions Compared

Old Version 15

changes.mady.by.user Eric Murray

Saved on

compared with

New Version 16

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

...

Panel
    • PR #59: Create Device Identifier User Story
      • Adds user stories for the Retrieve Device Identifier and Retrieve Device Type use cases

MEETING UPDATE:

      • <Discussion>

...

    • PR #60: Update MAINTAINERS.MD
      • Adds github usernames to maintainers file in preparation for more automated sub-project management

MEETING UPDATE:

      • <Discussion>
New PRs

...

Panel
  • PR #59: Create Device Identifier User Story
    • Adds user stories for the Retrieve Device Identifier and Retrieve Device Type use cases

MEETING UPDATE:

    • <Discussion>
Panel
  • PR #60: Update MAINTAINERS.MD
    • Adds github usernames to maintainers file in preparation for more automated sub-project management

MEETING UPDATE:

    • <Discussion>
Existing PRs

...

None

...

Closed PRs

...

None

Issues

New IssuesNone
Existing Issues
Panel
  • Issue #21: API Definition Terminology
    • Issue is out of date

ACTIONS:

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

Discussions

New DiscussionsNone
Existing Discussions

...

Panel
  • 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 DiscussionsNone

Other Issues

  • None

IMEI Fraud API status

Note

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.

...