Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 2
Next »
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) |
|
Aleksander Brankovic | Ipification |
|
Agenda
- Review of previous meeting minutes
- Review of Device Identifier API status
- AOB
Review of Device Identifier API status
- Current "work in progress" version can be found here
PRs
New PRs |
- 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
MEETING UPDATE: ACTIONS:
|
Existing PRs |
- PR #62: Update CAMARA Mobile Device Identifier API.yaml
- Re-name
X-Correlator to x-correlator
MEETING UPDATE: - No comments since last meeting
ACTIONS:
- PR #63: Update Project README.md
- Remove IMEI Fraud API from sub-project scope
- Update links to CAMARA Wiki
MEETING UPDATE: - No comments since last meeting
ACTIONS:
|
Closed PRs |
- PR #59: Create Device Identifier User Story
- Adds user stories for the Retrieve Device Identifier and Retrieve Device Type use cases
MEETING UPDATE: ACTIONS:
|
Issues
New Issues | None |
Existing Issues |
- Issue #61: Simplification of Device object - short term solution
- Commonalties proposes to revise DeviceObject
- Should be optional, with 3-legged access token normally used to identify the mobile subscription
- If 2-legged token is used, device object should be provided to API
- Network Access Identifier (3GPP External Id) option to be removed as support not common
MEETING UPDATE: - Should be closed by PR #64
ACTIONS: - ALL to review and comment before next meeting
- Issue #21: API Definition Terminology
MEETING UPDATE: 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
AOB
- Next meeting proposed to be held Friday 2nd August 2024 @ 09:00 BST using Zoom