Merge pull request #52 from intarchboard/mirjak-patch-6

Add text about RFC6973 to intro

Author: tfpauly

draft-iab-privacy-partitioning.md

@@ -86,6 +86,15 @@ of privacy partitioning, including OHAI, MASQUE, Privacy Pass, and PPM. This doc
 work in those groups and describes a framework for reasoning about the resulting privacy posture of different
 endpoints in practice.
 
+{{?RFC6973}} discusses data minimization, especially in the context of
+user identity and identity management systems.
+In these systems usually an identify provider issues credentials that can be used to access a
+service without revealing the user's identity by relying on the authentication assertion from
+the identity provider (see {{Section 6.1.4 of RFC6973}}). This describes a specific form of
+privacy partitioning, similar as used for privacy pass (see Section {{privacypass}}).
+Privacy partitioning as defined in this document goes further, to consider different deployment
+models that can create multiple contexts where data is minimized in each context.
+
 # Privacy Partitioning
 
 For the purposes of user privacy, this document focuses on user-specific information. This
@@ -443,7 +452,7 @@ Oblivious DNS over HTTPS {{?ODOH=RFC9230}} applies the same principle as Oblivio
 DNS messages only. As a precursor to the more generalized Oblivious HTTP, it relies on the same
 HPKE cryptographic primitives, and can be analyzed in the same way.
 
-## Privacy Pass
+## Privacy Pass {#privacypass}
 
 Privacy Pass is an architecture {{?PRIVACYPASS=I-D.ietf-privacypass-architecture}} and set of protocols
 being developed in the Privacy Pass working group that allow clients to present proof of verification in