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

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

Merged
merged 4 commits into from
Oct 29, 2023
Merged
Show file tree
Hide file tree
Changes from 3 commits
Commits
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
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://datatracker.ietf.org/doc/html/draft-ietf-ohai-ohttp',
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
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>
The Oblivious HTTP protocol [[?OHTTP]] is one mechanism that implementers might
consider using when fetching external resources that are associated with a
<a>verifiable credential</a> or a <a>verifiable presentation</a>.
Oblivious HTTP allows a client to make multiple requests to an origin server
without that server being able to link those requests to that client or even to
identify those requests as having come from a single client, while placing only
limited trust in the nodes used to forward the messages. Hence, Oblivious HTTP
is one privacy-preserving mechanism that can be used to reduce the possibility
of device tracking and fingerprinting.
</p>
</section>

<section class="informative">
Expand Down