Future roadmap: WiFi and non-handset IoT device support in Device Identifier API

[albertoramosmonagas]

Hi team,

We’ve been reviewing the Device Identifier v0.3 implementation under the CAMARA framework, and had two questions regarding potential future extensions:

1. WiFi scenarios:
Currently, the API seems limited to mobile devices authenticated through the mobile core (HLR/HSS/UDM). Are there any plans to extend /retrieve-identifier or /retrieve-type to support WiFi-attached sessions, for example when the subscriber device is connected through a broadband CPE or trusted WiFi gateway?

2. IoT and non-handset devices:
The documentation mentions support for IoT/M2M when a SIM/eSIM is present. Could the API, in future releases, be generalized to identify non-handset devices (e.g., connected cars, drones, smart home devices) that use a mobile subscription or NAI — potentially through an extended TAC or IoT registry?

We’re exploring use cases in connected mobility and device trust frameworks (EUDI Wallet, fraud prevention) and would like to understand if these scenarios are considered in the roadmap.

Thanks in advance for any clarification.