DRAFT
Attendees & Representation
Name | Company | Attendee |
---|---|---|
Eric Murray | Vodafone (moderator) | |
Sachin Kumar | Vodafone | |
Kevin Smith | Vodafone | |
Alex Ferreira | Phronesis | |
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 | |
Abhisek Das | Infosys | |
Brian Smith | Shabodi | |
Umair Ali Rashid | Shabodi | |
Foo Ming Hui | Singtel | |
Vilim Duganic | Infobip | |
Surajj Jaggernath | Vodacom | |
Walid Trabelsi | Sofrecom (Orange) |
Agenda
- Review of previous meeting minutes
- < APPROVED >
- Review of Device Identifier API status
- IMEI Fraud API status
- AOB
Review of Device Identifier API status
- Current "work in progress" version can be found here
PRs
- New PRs:
- PR #59: Create Device Identifier User Story
- Adds user stories for the Retrieve Device Identifier and Retrieve Device Type use cases
- PR #59: Create Device Identifier User Story
MEETING UPDATE:
- <Discussion>
- PR #60: Update MAINTAINERS.MD
- Adds github usernames to maintainers file in preparation for more automated sub-project management
- PR #60: Update MAINTAINERS.MD
MEETING UPDATE:
- <Discussion>
- Existing PRs:
- None
- Closed PRs:
- None
Issues
- New Issues
- None
- Existing Issues
- Issue #21: API Definition Terminology
- Issue is out of date
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
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
The IMEI Fraud API use case has been referred back to the GSMA OGW Product Workstream for re-evaluation. If the use case is still valid, it will be re-submitted the CAMARA API Backlog WG for re-approval. If approved, a separate repository will be created for the API. Discussions on this API can continue in these meetings if desired.
- See API Proposal submission here. For MTN proposal for the initial YAML, see 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
AOB
- Issue #48: Additional sub-project codeowner required
- UPDATE: No additional codeowner yet identified
- Next meeting proposed to be held Friday 7th June 2024 @ 09:00 BST using Zoom