Skip to content

Latest commit

 

History

History
25 lines (20 loc) · 2.08 KB

Mediation.md

File metadata and controls

25 lines (20 loc) · 2.08 KB

Mediation flow

Concepts and extensions

  • DIDComm Message Forwarding - Sending an encrypted message to its recipient by first sending it to a third party responsible for forwarding the message on. Message contents are encrypted once for the recipient then wrapped in a forward message encrypted to the third party.
  • DIDComm queue transport - Messages are held at the sender for pickup by the recipient. Recipient should explicitly declare this route option

Using a Mediator

There are two variants to pull inbound messages from mediator:

  1. recipient establish P2P connection with mediator (see schemas below) via rfc-0160 rfc-0023 protocol, then mediator declare endpoint URL (typically ws:// or http:// url) to retrieve forwarded messages
  2. recipient establish P2P connection with mediator via rfc-0160 rfc-0023 protocol, unlike previous case, recipient set didcomm:transport/queue as endpoint, in this case mediator will queue all incoming forwarded messages to make available to poll messages by recipient via pickup protocol.

Mediator Message Flow Overview

See sample code of establish connection with mediator here

Mediator Message Flow