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.

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

The return_route extension is utilized by coordinate-mediation and messagepickup #92

Conversation

FabioPinheiro
Copy link
Contributor

We are just clarifying some things in the protocol about the return_route as discussing the last DIF DID Comm meeting.
https://us02web.zoom.us/rec/share/iwQV16LJ9pDC_xInCSKfIIeSpagNEJDjJC4b55d8P3o4MWZDTthFA8ehMTovnThy.qUtcyz8pPHOlo9YG

Initial discussion in #87

@FabioPinheiro FabioPinheiro changed the title The return_route extension is utilized for coordinate-mediation and messagepickup The return_route extension is utilized by coordinate-mediation and messagepickup Aug 18, 2023
@FabioPinheiro FabioPinheiro force-pushed the return_route_should_be_used branch from 60cba0c to 337372c Compare August 18, 2023 16:32
@TelegramSam
Copy link
Collaborator

Added a suggestion, which adds a link, some clarification about frequency of the return-route header, and fixes a spelling error. This would apply to all the protocols.

"limit": 30,
"offset": 0
}
}
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

missing "return_route": "all" ?

@FabioPinheiro FabioPinheiro force-pushed the return_route_should_be_used branch from afbf834 to 83c5a44 Compare August 25, 2023 12:36
@rodolfomiranda rodolfomiranda merged commit c2e3db3 into decentralized-identity:main Aug 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants