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.

Sign up for GitHub

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

Jump to bottom

fix: link to raw content change from master to main #2663

Merged
merged 1 commit into from
Dec 9, 2023
Merged

fix: link to raw content change from master to main #2663

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/GettingStartedAriesDev/RoutingEncryption.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ Many Aries edge agents do not directly receive messages from a peer edge agent -

Thus, when a DIDComm message is sent from one edge agent to another, it is routed per the instructions of the receiver and for the needs of the sender. For example, in the following picture, Alice might be told by Bob to send messages to his phone (agent 4) via agents 9 and 3, and Alice might always send out messages via agent 2.

![image](https://github.com/hyperledger/aries-rfcs/raw/master/features/0067-didcomm-diddoc-conventions/domains.jpg)
![image](https://github.com/hyperledger/aries-rfcs/raw/main/features/0067-didcomm-diddoc-conventions/domains.jpg)

The following looks at how those requirements are met with mediators (for example, agents 9 and 3) and relays (agent 2).

Expand Down