Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[transport-ble] Discussions on implementation #197

Open
jimezesinachi opened this issue Mar 22, 2023 · 2 comments
Open

[transport-ble] Discussions on implementation #197

jimezesinachi opened this issue Mar 22, 2023 · 2 comments

Comments

@jimezesinachi
Copy link
Contributor

The BLE transport is still in its early stages. Discussions on the future trajectory of the project are held here, to be moved to a better location in the future if necessary.

@tbloomfi
Copy link

tbloomfi commented May 8, 2023

This is not specific to the implementation of the transport which is a great step forward but a more general observation on the implementation of working solutions.

Without a precise specification, implementations will not be interoperable. See the ISO eID/mDL and the very early draft of the OpenID4VCP over BLE for examples of the level of detail I am thinking of. Aries either needs to adapt to one of the above-listed specs or develop an RFC that provides the level of precision required by vendors.

Device vendors are going to build to the ISO spec as a default stance - NFC/QR engagement with BLE transport.

@TimoGlastra
Copy link
Contributor

Good point Tim! For now we've mostly been targeting https://github.com/decentralized-identity/didcomm-bluetooth/blob/main/spec.md.

Once we have a fully working implementation, we'll contribute back to that specification, revise it and make sure we learn from the OpenID4VP over BLE

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants