...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Attendees & Representation
| Name | Company | Attendee |
|---|---|---|
| Eric Murray | Vodafone (chairmoderator) | X |
| Sachin Kumar | Vodafone | X |
| 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 | X |
...
- 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
UPDATE:
- Meeting agreed this proposal was a good idea
- 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
ageOfInfomationfield to the response. Time unit TBD, but probably "hours" is sufficient.
- Issue #47: Add ageOfInformation field to API response
UPDATE:
- Huub suggests to use time stamp, in date-time format
- Issue #30: Defined scopes and meanings, being discussed in Issue
- Issue updated to give 3 options:
- Proposal is to have two scopes for one endpoint - 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-identifierinto 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
UPDATE:
- Discussed during meeting, but pros and cons of both approaches
- Also need to think from a "product" point of view - the two scopes will represent different products, so should they not also have different endpoints?
...
- 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
Deviceschema 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
...
- Issue #48: Additional sub-project codeowner required
- UPDATE: No additional codeowner yet identified
- Next meeting to be held Friday 9th February 2024 @ 09:00 GMT.
- One day, meetings will be held using the LFX Zoom service, but not yet
...