Versions Compared

Old Version 4

changes.mady.by.user Eric Murray

Saved on

compared with

New Version 5

changes.mady.by.user Eric Murray

Saved on

Key

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

DRAFT

Attendees & Representation

...

New PRs
Panel
  • PR #62: Update CAMARA Mobile Device Identifier API.yaml
    • Re-name X-Correlator to x-correlator

MEETING UPDATE:

    • To be reviewed and approved offline

ACTIONS:

    • ALL to provide any comments before end of month
Panel
  • PR #63: Update Project README.md
    • Remove IMEI Fraud API from sub-project scope
    • Update links to CAMARA Wiki

MEETING UPDATE:

    • To be reviewed and approved offline

ACTIONS:

    • ALL to provide any comments before end of month
Existing 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:

    • Kevin requests NAI be expanded to Network Access Identifier
    • Otherwise approved

ACTIONS:

    • Eric to update PR as proposed by Kevin
    • Kevin to then approve and merge
Closed PRs
None

Issues

New Issues
Panel
  • Issue #61: Simplification of Device object - short term solution
    • Commonalties proposes to revise DeviceObject
      • Should be optional, with 3-legged access token normally used to identify the mobile subscription
      • If 2-legged token is used, device object should be provided to API
      • Network Access Identifier (3GPP External Id) option to be removed as support not common

MEETING UPDATE:

    • Rafal noted that YAML documentation will also
      • will
    • need to be updated to explain when device identifiers should be explicitly provided

ACTIONS:

    • All
    • ALL to review and comment before next meeting
Existing Issues
Panel
  • Issue #21: API Definition Terminology
    • Issue is out of date

MEETING UPDATE:

ACTIONS:

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

...

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

AOB

  • Issue #48: Additional sub-project codeowner required
    • UPDATE: Now closed
  • Next meeting proposed to be held Friday 5th July 2024 @ 09:00 BST using Zoom

...