Register DIDComm accept and routingKeys service properties#337
Open
yno9 wants to merge 2 commits into
Open
Conversation
A DIDCommMessaging service endpoint carries accept and routingKeys alongside uri, but the registry maps neither. A did:dht document can therefore express the endpoint's URI and nothing else, and a resolver that reads it learns where to deliver without learning the routing keys needed to wrap the message for the recipient's mediator — so mediated delivery, the ordinary case for a client that isn't itself reachable, can't be completed. Both are already defined by DIDComm Messaging and registered in the DID Specification Registries; this only supplies the DNS packet mapping the registry requires. Abbreviated to ac/rk to conserve packet space, per the spec's own size-constraints guidance.
The sig row gives enc=E as its DNS representation and enc=1 as its example; the enc row gives sig=S and sig=2. Each describes the other.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A
DIDCommMessagingservice endpoint carriesacceptandroutingKeysalongsideuri, but the registry maps neither — so adid:dhtdocument can express the endpoint's URI and nothing else. A resolver reading it learns where to deliver, but not the routing keys needed to wrap the message for the recipient's mediator, so mediated delivery — the ordinary case for a client that isn't itself reachable — can't be completed.Both properties are already defined by DIDComm Messaging and registered in the DID Specification Registries; this only supplies the DNS packet mapping the registry requires. Abbreviated to
ac/rkto conserve packet space, per the spec's own size constraints guidance.Implemented and interoperating in biset, which uses
did:dhtas its identity layer and DIDComm v2 for messaging.The second commit is unrelated and separable: the existing
sigandencrows have their DNS representation and example swapped (thesigrow documentsenc=Ewith exampleenc=1, and vice versa). Happy to drop it or split it into its own PR.