Device Identifier Meeting Minutes 2024-01-12

Attendees & Representation

Not discussed as no representative from MTN or Huawei joined the call

Open Discussions:
- #37: IMEI Fraud API Input
  - Proposal is just to use a single "IMEI" field, which would accept either IMEI or IMEISV
- #34: What values should the IMEI Fraud API respond with to indicate reported ownership status?
  - The GSMA appear to have an existing Device Check service, which includes an API. How does the CAMARA proposal differ from this?

AGREEMENT: MTN / Huawei will join sub-project meetings from next year, so can then drive these discussion

Closed PRs:
- PR #45: Update CAMARA Device Identifier API.yaml
  - Changes basepath from dvi/v0 to device-identifier/v0
  - Version number updated to v0.3.0
  - Fixes Issue #40: Proposed renaming of device identifier API

New Issues
- Issue #46: Rename API title to CAMARA Mobile Device Identifier API
  - Current API title is "CAMARA Device Identifier API", but the API only applies (and can only apply) to mobile devices.
  - It is proposed to make this clearer by renaming the API to "CAMARA Mobile Device Identifier API"

ACTION: Comment within issue if you have an opinion. PR will then be raised.

- Issue #47: Add ageOfInformation field to API response
  - Follows on from Discussion #35
  - Current API response gives no indication of when the physical device information was collected for the specified subscription identifier (e.g. phoneNumber). Dependent on the backend implementation, this information could have been collected some time earlier, and potentially be out of date
  - Add an ageOfInfomation field to the response. Time unit TBD, but probably "hours" is sufficient.

ACTION: Comment within issue if you have an opinion. PR will then be raised.

Open Issues:
- Issue #30: Defined scopes and meanings, being discussed in Issue
  - Issue updated to give 3 options:
    - Proposal is to have two scopes - one for all information, and one for TAC, Make and Model only
    - Alternative 1: One single scope, which gives all information
    - Alternative 2: Two scopes but two endpoints
      - Split /get-device-identifier into two separate endpoints for imei / imeisv and tac / manufacturer / model respectively, each with its own scope.

ACTION: Eric to add Vodafone preference, and to advertise issue via mailing list to try and get alternative opinions.

ACTION: Eric to update issue text (still open)

Closed Issues
- Issue #40: Proposed renaming of device identifier API
  - Fixed by PR #45: Update CAMARA Device Identifier API.yaml

Open Discussions:
- 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
- Discussion #35: Age of information or device connectivity status
  - Promoted to Issue #47: Add ageOfInformation field to API response

Kevin raised the point that YAML schemas should use the common schemas defined in CAMARA_common.yaml where appropriate. Ideally, they could be directly referenced, though this can cause issues with some OAS viewers.
- ACTION: Eric to check that current Device Identifier YAML is compliant with common schemas
- ACTION: Kevin to check how OAS viewers handle external references

Issue #48: Additional sub-project codeowner required
- ACTION: Eric to advertise for new codeowners via mailing list
Next meeting to be held Friday 26th January 2024 @ 16:00 GMT.
One day, meetings will be held using the LFX Zoom service, but not yet