Add anonymous credentials and reverse flow #2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Specify a mechanism through which teh origin can issue it's own tokens. This is based on reverse flow privacy pass, and allow the origin to leverage privately verifiable tokens, as well as anonymous credentials.
This is to be presented at IETF 124 in Montreal. If this is the right direction, the draft could be reorganised to consider this mode as a base case.
There are some discussion to have regarding the use of
origin_infovsredemption_contextwith anonymous credentials.I also have not mentioned new development with Anonymous credit token as the draft is yet to be published (later today). That could be an interesting evolution. The current writting focuses on what can be deployed today.