Page Comparison

Attendees & Representation

...

Discussion on IMEI Fraud API

• See API Proposal submission here

...

AGREEMENT: MTN / Huawei will join sub-project meetings from next year, so can then drive these discussion

Review of Device Identifier API status

...

• New 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"

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.

ACTION: Comment within issue if you have an opinion. PR will then be raised.

• Open Issues:
  • 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.

...

• Closed Discussions
  • Discussion #35: Age of information or device connectivity status
    • Promoted toIssue #47: Add ageOfInformation field to API response

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
  • ACTION: Kevin to check how OAS viewers handle external references

AOB

• Issue #48: Additional sub-project codeowner required
  • ACTION: Eric to advertise for new codeowners via mailing list
• Next meeting to be held Friday 26th January 2024 @ 16:00 GMT.
• One day, meetings will be held using the LFX Zoom service, but not yet

...