Device Identifier and Device Authenticity Meeting Minutes 2026-06-05

Eric Murray

Vodafone (moderator)

Sachin Kumar

Vodafone

Kevin Smith

Vodafone

Matthew Hornsey

TMT ID

Sébastien Synold

Intersec

S, Vigneshwaran

Cognizant

Karthik Raj Rethinakumar

Cognizant

Manish Jain

Cognizant

Huub Appelboom

KPN

Rafal Artych

DT

Axel Nennker

DT

Abhisek Das

Infosys

Brian Smith

Shabodi

Umair Ali Rashid

Shabodi

Foo Ming Hui

Singtel

Vilim Duganic

Infobip

Surajj Jaggernath

Vodacom

Walid Trabelsi

Sofrecom (Orange)

Aleksander Brankovic

Ipification

Ali Iqbal

xFlow

Alberto Ramos

Telefonica

168

OPEN

https://github.com/camaraproject/DeviceIdentifier/issues/168

• Update required to the API definition to fix majority of warnings and hints detected here

• PR created

  • https://github.com/camaraproject/DeviceIdentifier/pull/167

  • Remaining warnings and errors can be seen here

    • 1 warning and 3 hints remaining

Jun 5, 2026

• Approved and merged

156

OPEN

https://github.com/camaraproject/DeviceIdentifier/issues/156

• release-plan.yaml needs to be updated by end of the month to signal that device-identifier will participate in the Sync'26 release

• Need to decide:

  • whether to participate and, if so

  • whether to only do a minor version update (to 0.4.0) or go for a stable release (1.0.0)

Apr 10, 2026

• Agreed to participate with minor version update to 0.4.0

• @Kevin Smith to check on use of field target_release_type

May 1, 2026

• release-plan.yaml updated with intention to release a release candidate

• Merging triggered the following PR, which needs to be approved and merged:

  • https://github.com/camaraproject/DeviceIdentifier/pull/162

  • DECISION: Approved and merged

• And the following issue for release management:

  • Release r3.1 (RC) — Sync26 · Issue #163 · camaraproject/DeviceIdentifier

• Should review whether a release candidate or alpha would be more appropriate once scale of rework required to be compliant with updated linting rules becomes apparent

  • DECISION: Stick with RC

Jun 5, 2026

• Commonalities have now released v0.8.0 as r4.3, and hence release plan needs to be updated

  • Given that some test definitions are still missing (see #159) and others need to be review (see #158), it is proposed to now start with an alpha release

    • PR created to update release-plan:

      • https://github.com/camaraproject/DeviceIdentifier/pull/166

    • Merging this PR will trigger more PRs from release management

      • Existing Issue #163 and PR #165 can be closed once that happens, as they will be no longer required

• Decision: Approved and merged

159

OPEN

https://github.com/camaraproject/DeviceIdentifier/issues/159

• Follows on from merging of #151

• May be fixed by the following PR:

  • https://github.com/camaraproject/DeviceIdentifier/pull/160

May 1, 2026

• PR needs to be reviewed and then approved

• Review of all test files required for consistency

Jun 5, 2026

• Still to be reviewed

158

OPEN

https://github.com/camaraproject/DeviceIdentifier/issues/158

• Language of test specifications needs to be tighter

• Before a PR is created, updated tests adopted by other APIs should be reviewed

Jun 5, 2026

• Still to be reviewed

163

OPEN

https://github.com/camaraproject/DeviceIdentifier/issues/163

• Release tracker created by release-automation

  • Associated PR: https://github.com/camaraproject/DeviceIdentifier/pull/165

• Can both be closed once updated release-plan.yaml is merged

Jun 5, 2026

• Automatically updated for alpha release based on Commonalities r4.3

164

OPEN

https://github.com/camaraproject/DeviceIdentifier/issues/164

• Reminder to delete redundant workflows when no longer required

• Keep open until Sync’26 release is complete

143

OPEN

https://github.com/camaraproject/DeviceIdentifier/discussions/143

Mar 6, 2026

• We should add more comments to this discussion and ensure it aligns with how other APIs handle similar use cases, then incorporate those approaches.

Apr 10, 2026

• Some comments added to the discussion

• Feel free to add more comments

Jun 5, 2026

• No additional discussion

6

OPEN

https://github.com/camaraproject/DeviceAuthenticity/issues/6

• Create API documentation

• Draft PR

  • https://github.com/camaraproject/DeviceAuthenticity/pull/9

Feb 6, 2026

• User story template is here Commonalities/documentation/Userstory-template.md at main · camaraproject/Commonalities

• User stories go here DeviceAuthenticity/documentation/API_documentation at main · camaraproject/DeviceAuthenticity

• Additional documentation goes here https://github.com/camaraproject/DeviceAuthenticity/tree/main/documentation/SupportingDocuments

Jun 5, 2026

• No discussion

13

OPEN

https://github.com/camaraproject/DeviceAuthenticity/issues/13

• API design should take into account original requirements from MTN and Chenosis

Mar 6, 2026

• @ALI IQBAL will review the MTN proposal and its YAML file, and incorporate any necessary changes into the new PR request.

Jun 5, 2026

• No discussion

14 (PR)

OPEN

https://github.com/camaraproject/DeviceAuthenticity/pull/14

• File renamed, with minor documentation updates

Jun 5, 2026

• No discussion

16

OPEN

https://github.com/camaraproject/DeviceAuthenticity/issues/16

• Reminder that legacy validation flow definitions will be deleted following Sync’26 GA

Jun 5, 2026

• No discussion