Attendees & Representation
| Name | Company | Attendee |
|---|---|---|
| Eric Murray | Vodafone (moderator) | X |
| Sachin Kumar | Vodafone | |
| 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 | |
| Rafal Artych | DT | X |
| Abhisek Das | Infosys | |
| Brian Smith | Shabodi | |
| Umair Ali Rashid | Shabodi | |
| Foo Ming Hui | Singtel | |
| Vilim Duganic | Infobip | |
| Surajj Jaggernath | Vodacom | X |
| Walid Trabelsi | Sofrecom (Orange) |
Agenda
- Review of previous meeting minutes
- < APPROVED >
- Review of Device Identifier API status
- Discussion on requirements for IMEI Fraud
- AOB
- Review of meeting schedule
Review of Device Identifier API status
- Current "work in progress" version can be found here
PRs
- New PRs:
- PR #57: Preparation for v0.1.0 pre-release
- Proposed changes:
- Version number changed to 0.1.0
- URL changed to "{apiRoot}/device-identifier/v0.1.0"
- Proposed changes:
- Draft release notes can be found here
- PR #57: Preparation for v0.1.0 pre-release
MEETING UPDATE:
- PR and initial release approved
- Existing PRs:
- None
- Closed PRs:
- None
Issues
- New Issues
- None
- Existing Issues
- Issue #21: API Definition Terminology
- Issue is out of date
- Issue #21: API Definition Terminology
ACTIONS:
- Eric to update issue text (still open)
- Closed Issues
- None
Discussions
- New Discussions
- None
- Existing 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
- None
Other Issues
- 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: Kevin to check how OAS viewers handle external references
Discussion on IMEI Fraud API
This API will not be further discussed until API proponents attend the sub-project meetings.
For MTN proposal for the initial YAML, see here
- 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?
- Kevin highlighted a GSMA video on their Device Check service.
- #37: IMEI Fraud API Input
AGREEMENT: MTN / Huawei will join sub-project meetings from next year, so can then drive these discussion
AOB
- Issue #48: Additional sub-project codeowner required
- UPDATE: No additional codeowner yet identified
- Next meeting proposed to be held Friday 3rd May 2024 @ 09:00 BST using Zoom
- Proposal:
- Change meeting to a fixed time, as participation from North America is limited
- Change meeting frequency to once per month from May. Proposal is first Friday of each month.
- Change meeting conference bridge to LF Zoom
- If agreed in meeting, will be circulated to mailing list first to confirm
- Meeting agreed to proposal
- Proposal: