Page History

DRAFT

Attendees & Representation

Agenda

• Review of previous meeting minutes
  [ Decision ]
  • Approved
• Review of Device Identifier API status
• Discussion on requirements for IMEI Fraud
• AOB

...

• • PR #53: Add X-Correlator to OAS and update linting rules
    • Requirement in latest version of API Design Guidelines
    • Linting rules agreed in Commonalities, but still not merged

UPDATE: Rafal suggested newline issue was due to Windows newline format being used rather than Linux

• • PR #52: Rename project to CAMARA Mobile Device Identifier API
    • As agreed in Issue #46

...

lastChecked:
  description: Last time that the associated device identity was checked and updated if necessary
  type: string
  format: date-time

MEETING UPDATE:

• • • Huub proposed lastRecorded 
      • AGREED
        ACTION: Eric to raise PR
    • Huub raised issue of primary / secondary MSISDNs and multi-SIM
      • ACTION: Eric to open discussion on multi-SIM scenarios
      • ACTION: Eric to update documentation on MSISDN being treated as secondary MSISDN by network

• • Issue #30: Defined scopes and meanings, being discussed in Issue 
    • The two use cases (retrieve all parameters or only tac / manufacturer / model), two separate scopes are required
    • Should they be two scopes of same endpoint, or associated with separate endpoints

...

• • • Updated proposal is to have two separate endpoints as follows:

      get-identifier with scope device-identifier:get-identifier which returns:

      • imeisv
      • imei
      • tac
      • model
      • manufacturer

      get-type with scope device-identifier:get-type which returns:

      • tac
      • model
      • manufacturer

MEETING UPDATE:

• • • Alex supports two endpoints
    • Kevin suggests retrieve-identifier  and retrieve-type 
    • AGREED to use retrieve-identifier  and retrieve-type 
      ACTION: Eric to raise PR

• • Issue #21: API Definition Terminology
    • Issue is out of date

...