Attendees & Representation
Name | Company | Attendee |
---|---|---|
Eric Murray | Vodafone (chair) | X |
Sachin Kumar | Vodafone | X |
Kevin Smith | Vodafone | X |
Alex Ferreira | Phronesis | X |
Matthew Hornsey | Phronesis | |
Matthew Hand | Phronesis | |
Sébastien Synold | Intersec | |
S, Vigneshwaran | Cognizant | |
Karthik Raj Rethinakumar | Cognizant | |
Manish Jain | Cognizant | |
Huub Appelboom | KPN | X |
Rafal Artych | DT | X |
Abhisek Das | Infosys | |
Brian Smith | Shabodi | |
Umair Ali Rashid | Shabodi | |
Foo Ming Hui | Singtel | |
Vilim Duganic | Infobip | |
Surajj Jaggernath | Vodacom |
Agenda
- Review of previous meeting minutes
- Discussion on requirements for IMEI Fraud
- Review of Device Identifier API status
- AOB
Discussion on IMEI Fraud API
- See API Proposal submission here
- 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?
- #37: IMEI Fraud API Input
AGREEMENT: MTN / Huawei will join sub-project meetings from next year, so can then drive these discussion
Not discussed as no representative from MTN or Huawei joined the call
Review of Device Identifier API status
- Current "work in progress" version can be found here
PRs
- New PRs:
- None
- Open PRs:
- None
- Closed PRs:
Issues
- 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"
- Issue #46: Rename API title 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.
- Issue #47: Add ageOfInformation field to API response
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.
- Split
- Issue updated to give 3 options:
- Issue #30: Defined scopes and meanings, being discussed in Issue
ACTION: Eric to add Vodafone preference, and to advertise issue via mailing list to try and get alternative opinions.
- Issue #21: API Definition Terminology
- Issue is out of date
- Issue #21: API Definition Terminology
ACTION: Eric to update issue text (still open)
- Closed Issues
Discussions
- New Discussions
- None
- 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
- Discussion #36: Alternative device identifiers
AGREEMENT: Leave discussion open for now, but prioritise returning IMEI / IMEISV
- Closed Discussions
AOB
- 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