-
General message constructs section is missing ACKs section
awoie updated
2 years ago
-
Some who approach DIDComm may view it simply as a transport mechanism, with the purpose being to enable arbitrary messages to flow securely. That is not wrong, exactly -- but it's incomplete. A major …
-
There isn't a special message for a reuse case with Connection protocol. If an invitation contains the handshake protocols, but does not contain a request~attach and there is an existing connection. T…
-
I don't use ION but it looks like there might be some limitations here based on this discussion.
https://github.com/decentralized-identity/ion-tools/issues/16#issuecomment-925402311
I'm concerne…
-
It seems the only content encryption algorithms supported by ECDH-1PU draft4 are the AES-CBC+HMAC-SHA ones. See discussion in [PR-212](https://github.com/decentralized-identity/didcomm-messaging/pull/…
-
A developer wanting to implement the spec read this section:
>https://identity.foundation/didcomm-messaging/spec/#protecting-the-skid-header
His comment was that there is not enough detail to im…
-
-
I suggest imagine multiple situations to think and answer:
1. We have Signed message from Alice to Bob, but `from` field in plaintext is empty or different.
- Should implementation check it and…
-
Original Issue: https://github.com/hyperledger/aries-rfcs/issues/72
-
The charter at https://www.w3.org/2017/vc/WG/charter.html states that APIs and protocols for using the Verifiable Credentials Data Model is out of scope. Yet the new charter adds possible non-normati…