Skip to content

Commit 6929d06

Browse files
authored
Update draft-iab-privacy-partitioning.md
1 parent 1d18388 commit 6929d06

File tree

1 file changed

+8
-1
lines changed

1 file changed

+8
-1
lines changed

draft-iab-privacy-partitioning.md

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -254,7 +254,14 @@ Privacy Pass is an example of a case that can be either interactive or not,
254254
depending on if tokens can be cached and reused. CONNECT-style proxying and
255255
Oblivious HTTP often require bidirectional and interactive communication.
256256

257-
257+
- The degree to which contexts need to be partitioned depends in part
258+
on the client's threat models and level of trust in various protocol participants. For example,
259+
in Oblivious HTTP, clients allow relays to learn that clients are accessing a particular
260+
application-specific gateway. If clients do not trust relays with this information, they can
261+
instead use a multi-hop CONNECT-style proxy approach wherein no single party learns
262+
whether specific clients are accessing a specific application. This is the default trust model
263+
for systems like Tor, where multiple hops are used to drive down the probability of privacy
264+
violations due to collusion or related attacks.
258265
# A Survey of Protocols using Partitioning
259266

260267
The following section discusses currently on-going work in the IETF

0 commit comments

Comments
 (0)