DRAFT
Attendees & Representation
...
- Existing 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.
- 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
...
- Closed Discussions
- Discussion #49: Get Device Identifier without exposing the phone number
- Discussion on whether device identifier can be obtained without the API consumer needing to know or learning the MSISDN
- When Identity & Consent rules are fully implemented, end user identifying data such as this will be removed from the service API call
- Discussion #49: Get Device Identifier without exposing the phone number
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: Eric to check that current Device Identifier YAML is compliant with common schemas
Device
schema needs to be updated now that IPv6 address must be a single address, but there is an outstanding PR for this schema- Will introduce a PR once the Commonalities PR is merged
- ACTION: Kevin to check how OAS viewers handle external references
- ACTION: Eric to check that current Device Identifier YAML is compliant with common schemas
Discussion on IMEI Fraud API
...