Versions Compared

Key

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

DRAFT

Attendees & Representation

...

New PRs
Panel
  • PR #67: Update CAMARA Mobile Device Identifier API.yaml
    • Commonalities v0.4.0 allows x-correlator to be any string, and not restricted to being a uuid.
    • Therefore "format: uuid" needs to be removed from the definition.

MEETING UPDATE:

    • No update

ACTIONS:

    • ALL to review and comment or approve by  
Panel
  • PR #66: Update CAMARA Mobile Device Identifier API.yaml
    • Update info section of OAS to comply with Commonalities guidelines v0.4.0

MEETING UPDATE:

    • No update

ACTIONS:

    • ALL to review and comment or approve by  
Existing PRs
Panel
  • PR #64: Incorporate Commonalities WG recommendations on Simplification of Device object
    • Add Commonalities WG recommended text on "Identifying a device from the access token"
    • Add 422 error response option
    • Explicitly define request body as optional
    • Description updated to replace device with mobile subscription identifier as appropriate 

MEETING UPDATE:

    • Huub commented that line 71 implies the access token follows a certain implementation
      • "The server will extract the mobile subscription identifier (e.g. MSISDN) from the access token, if available."
      • This text needs to be revised to be more implementation neutral. MSISDN replaced by phone number.
    • Keep PR open until to see if Commonalities revise current solution for Device object handling

ACTIONS:

Closed PRs
Panel
  • PR #63: Update Project README.md
    • Remove IMEI Fraud API from sub-project scope
    • Update links to CAMARA Wiki
    • Now merged
Panel
  • PR #62: Update CAMARA Mobile Device Identifier API.yaml
    • Re-name X-Correlator to x-correlator
    • Now merged

...

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 Discussions

None

Other Issues

  • None

AOB

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

...