Versions Compared

Old Version 6

changes.mady.by.user Eric Murray

Saved on

compared with

New Version 7

changes.mady.by.user Eric Murray

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

New PRs
Panel
borderColorred
borderStylesolid

PR #72: Initial Test Definitions for DeviceIdentifier retrieve identifier

  • Proposal for test definitions in response to Issue #68
  • Final review required by more API participants

MEETING UPDATE :

  • <MEETING UPDATE>
Panel
borderColorred
borderStylesolid

PR #73: Add EUDI Wallet and Mobile Device Insurance User Stories

  • Additional user stories for Device Identifier
  • Adds a use case where the physical device itself requests its own IMEI (because OS will not provide it to the app)
  • Review required by API participants

MEETING UPDATE :

  • <MEETING UPDATE>
Panel
borderColorred
borderStylesolid

PR #78: remove misleading sentence on from where the API can be called

  • Proposal to remove description text stating that API can be called by "an application server or other 3rd party server"
  • Discussion and revision required as the API clearly can be called by an application or other 3rd party server

MEETING UPDATE :

  • <MEETING UPDATE>
Existing PRs
Closed PRs
Panel
borderColorred
borderStylesolid

PR #81: Remove 405 error response from YAML

MEETING UPDATE :

  • PR merged on as this fixes a CAMARA non-compliance
Panel
borderColorred
borderStylesolid

PR #77: Reduce telco language in the API description

  • Removes reference to UE / User Equipment in description and replaces with "physical mobile device"

MEETING UPDATE :

  • PR merged on as no comments on proposed wording
Panel
borderColorred
borderStylesolid

PR #76: Rewrite text around treatment of primary / secondary MSISDN

  • Removes reference to a specific implementation of this, and rewrites using more generic language
  • Treatment of MSISDNs as phoneNumber remains the same - the phoneNumber will be treated as the secondary MSISDN, and can thus be used to identify the IMEI of all devices

MEETING UPDATE :

  • PR merged on as no comments on proposed rewording
Panel
borderColorred
borderStylesolid

  • PR #75: Fixes the missing required property in the the error response schema

    • Fixes the missing `required` property in the the error response schema

MEETING UPDATE :

    • PR merged on as this was a clear non-compliance with the Commonalities common JSON definitions
Panel
borderColorred
borderStylesolid

  • 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 :

    • No update

MEETING UPDATE  :

    • PR merged on  as no further comments
Panel
borderColorred
borderStylesolid

  • PR #66: Update CAMARA Mobile Device Identifier API.yaml

    • Update info section of OAS to comply with Commonalities guidelines v0.4.0

MEETING UPDATE  :

    • No update

ACTIONS:

    • PR merged on  as no further comments
Panel
borderColorred
borderStylesolid

  • 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 to be replaced by phone number.
    • Keep PR open until to see if Commonalities revise current solution for Device object handling

MEETING UPDATE  :

    • Merged on as no further comments

Issues

New Issues
Panel
borderColorred
borderStylesolid

MEETING UPDATE  :

    • See PR #72
    • Issue can be closed when above PR is merged
Existing Issues
Panel
borderColorred
borderStylesolid

  • Issue #21: API Definition Terminology

    • Issue is out of date

MEETING UPDATE  :

    • No update

MEETING UPDATE :

    • <MEETING UPDATE>

ACTIONS:

    • Eric to update issue text (still open)
Closed Issues
Panel
borderColorred
borderStylesolid

  • 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

...

New DiscussionsNone
Existing Discussions
Panel
borderColorred
borderStylesolid

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

MEETING UPDATE :

  • Discussion updated by Axel Nennker with proposal to include PPID as a 3rd device identifier that can be requested (in addition to IMEI or TAC)
Closed Discussions

None

...