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

Add suggestion to use Oblivious HTTP when fetching resources. #1322

Merged
merged 4 commits into from
Oct 29, 2023
Merged

Add suggestion to use Oblivious HTTP when fetching resources. #1322

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
668a581
Add suggestion to use Oblivious HTTP when fetching resources.
msporny Oct 21, 2023
30de700
Fix grammar in OHTTP section.
msporny Oct 24, 2023
0c37885
Update link to OHTTP draft at IETF.
msporny Oct 24, 2023
0234a2b
Add concrete examples of when OHTTP is useful.
msporny Oct 29, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions common.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -82,6 +82,13 @@ var vcwg = {
authors: ['Daniel Buchner', 'Brent Zundel', 'Martin Riedel', 'Kim Hamilton Duffy'],
status: 'DIF Ratified Specification',
publisher: 'Decentralized Identity Foundation'
},
'OHTTP': {
title: 'Oblivious HTTP ',
href: 'https://ietf-wg-ohai.github.io/oblivious-http/draft-ietf-ohai-ohttp.html',
Copy link

Choose a reason for hiding this comment

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

I'd suggest using the official IETF datatracker link: https://datatracker.ietf.org/doc/html/draft-ietf-ohai-ohttp

Copy link
Member Author

@msporny msporny Oct 24, 2023 •
edited
Loading

Choose a reason for hiding this comment

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

Done in 0c37885, thank you!

msporny marked this conversation as resolved.
Show resolved Hide resolved
authors: ['Martin Thomson', 'Christopher A. Wood'],
status: 'Working Group Draft',
publisher: 'IETF Oblivious HTTP Application Intermediation'
}
}
};
Expand Down
14 changes: 13 additions & 1 deletion index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4385,7 +4385,7 @@ <h3>Long-Lived Identifier-Based Correlation</h3>
</section>

<section class="informative">
<h3>Device Fingerprinting</h3>
<h3>Device Tracking and Fingerprinting</h3>

<p>
There are mechanisms external to <a>verifiable credentials</a> that are used to
Expand All @@ -4406,6 +4406,18 @@ <h3>Device Fingerprinting</h3>
In some cases, tracking technologies might need to be disabled on devices that
transmit <a>verifiable credentials</a> on behalf of a <a>holder</a>.
</p>

<p>
One mechanism that implementers might consider utilizing when fetching external
resources that are associated with a <a>verifiable credential</a> or a
<a>verifiable presentation</a> is the Oblivious HTTP protocol [[?OHTTP]].
msporny marked this conversation as resolved.
Show resolved Hide resolved
Oblivious HTTP allows a client to make multiple requests to an origin server
without that server being able to link those requests to the client or to
identify the requests as having come from the same client, while placing only
limited trust in the nodes used to forward the messages. Using Oblivious HTTP
is one privacy-preserving mechanism that can be used to reduce the possibility
of device tracking and fingerprinting.
msporny marked this conversation as resolved.
Show resolved Hide resolved
</p>
</section>

<section class="informative">
Expand Down