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

What are the Essential Protocols that should be included in the DIDComm spec? #81

Closed
TelegramSam opened this issue Jul 20, 2020 · 6 comments

Comments

@TelegramSam
Copy link
Collaborator

Note, our charter ONLY includes specifying protocols necessary for establishing and maintaining the mechanics of DIDComm. Other protocols will be the work of other groups.

Proposed Essential Protocols:

  • Trust Ping
  • Feature Discovery (please disclose protocols you support)
  • Channel Teardown
    • I'm about to delete this DID and forget yours
    • Please erase my information (can serve as a GDPR erasure request)

Thoughts?

@bumblefudge
Copy link
Contributor

+1 to GDPR erasure request-- making those machine-readable and automatable upon proof of DID control would a truly GDPR-compliant DID solution make.

+1 to trust ping, that seems widely generalizable

As for feature discovery, I think maybe I missed (or was zoned out during) the part where feature discovery was discussed. Is that specific to a list of specified protocols in Aries or is that defined in a more cross-community way somewhere? or does that refer specifically to some forthcoming typology of service endpoints?

@swcurran
Copy link
Contributor

It's a request for a list of protocols supported by the other entity (or perhaps entities) that run on top of DIDComm. It's implemented in Aries but is not limited by that, so it certainly can be cross-community.

@troyronda
Copy link
Contributor

Note: there is already an essential protocol in the spec - Routing Protocol ( https://identity.foundation/didcomm-messaging/docs/spec/#routing). Also, are there other routing / mediation protocols planned for the spec?

Another related topic is the aspects of out-of-band protocol that haven't yet been covered by spec text - Particularly goal code ("please play the role of").

@troyronda
Copy link
Contributor

Beyond having a feature discovery mechanism for protocols, there is also the topic of lower layer metadata (and errors) such as supported DID methods. (#82).

@swcurran
Copy link
Contributor

Cross-cutting protocols might be called essential. I'm thinking in particular, adopted protocols (ack and problem report) and decorators -- threads, attachments, perhaps tracing.

@TelegramSam
Copy link
Collaborator Author

Closed in WG 20201109.

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

4 participants