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 6
Next »
DRAFT
Attendees & Representation
Name | Company | Attendee |
---|
Eric Murray | Vodafone (moderator) | X |
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 | X |
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 |
|
Axel Nennker | DT | X |
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 #67: Update CAMARA Mobile Device Identifier API.yaml
- Commonalities v0.4.0 allows x-correlator to be any string, and not restricted to being a uuid.
- Therefore "
format: uuid" needs to be removed from the definition.
MEETING UPDATE: ACTIONS: - ALL to review and comment or approve by
- PR #66: Update CAMARA Mobile Device Identifier API.yaml
- Update
info section of OAS to comply with Commonalities guidelines v0.4.0
MEETING UPDATE: ACTIONS: - ALL to review and comment or approve by
|
Existing 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
- Description updated to replace
device with mobile subscription identifier as appropriate
MEETING UPDATE: - Huub commented that line 71 implies the access token follows a certain implementation
"The server will extract the mobile subscription identifier (e.g. MSISDN) from the access token, if available." - This text needs to be revised to be more implementation neutral.
MSISDN replaced by phone number .
- Keep PR open until to see if Commonalities revise current solution
ACTIONS:
|
Closed PRs |
- PR #63: Update Project README.md
- Remove IMEI Fraud API from sub-project scope
- Update links to CAMARA Wiki
- Now merged
- PR #62: Update CAMARA Mobile Device Identifier API.yaml
- Re-name
X-Correlator to x-correlator - Now merged
|
Issues
New Issues |
- Issue #68: API Test Cases Required to be Defined
MEETING UPDATE: - No update. Still looking for volunteers to provide test cases.
ACTIONS: - ALL to consider providing test cases for this API
|
Existing Issues |
- Issue #21: API Definition Terminology
MEETING UPDATE: ACTIONS: - Eric to update issue text (still open)
- 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
- Will be closed by PR #64
|
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 | |
Other Issues
AOB
- Next meeting proposed to be held Friday 6th September 2024 @ 09:00 BST using Zoom