search

decentralized-identity / didcomm.org

https://didcomm.org/
Apache License 2.0
36 stars 25 forks source link

Proposal for Message Pickup v4 #110

Open JamesKEbert opened 3 months ago

JamesKEbert commented 3 months ago

This is a proposal for message-pickup v4, motivated primarily by ambiguity when in live mode as to whether messages must still be delivered via delivery and messages-received. It was determined that clarifying that they are required would be considered a breaking change -- #105. This is also an issue in DIDComm v1, which uses pickup v2, so this protocol introduces examples for both DIDComm v1 and DIDComm v2. This also attempts to address minor inconsistencies or issues identified.

Open questions: Should a delivery-request that has 0 queued messages return a status message or an empty delivery message? I lean towards yes as it reduces complexity (if a status message is sent in response to a delivery-request due to an empty queue, and the delivery-request had a filter recipient_did specified, does the status also contain that?) - empty delivery message was the consensus during DIDComm UG discussion

See related issues: https://github.com/decentralized-identity/didcomm.org/pull/105 https://github.com/hyperledger/aries-rfcs/issues/760 https://github.com/decentralized-identity/didcomm.org/issues/87

JamesKEbert commented 1 month ago

As discussed in the DIDComm UG calls, I've updated the RFC with a changelog and made the adjustment to the behavior of handling a delivery-request when no pending messages are in the queue. Any feedback welcome. @dbluhm, your input here would also be particularly valuable here. cc: @TelegramSam