Add concrete examples of when OHTTP is useful.

index.html

@@ -4416,8 +4416,26 @@ <h3>Device Tracking and Fingerprinting</h3>
 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.
+of device tracking and fingerprinting. Concrete examples for how Oblivious HTTP
+can benefit ecosystem participants are included below.
         </p>
+
+        <ul>
+          <li>
+A <a>holder</a> using a digital wallet can reduce the chances that they
+will be tracked by a 3rd party when accessing external links within a
+<a>verifiable credential</a> stored in their digital wallet.
+For example, a digital wallet might fetch and render linked images, or
+check the validity of a <a>verifiable credential</a> by fetching an
+externally linked revocation list.
+          </li>
+          <li>
+A <a>verifier</a> can reduce signalling to an <a>issuer</a> that the
+<a>verifier</a> has received a specific <a>verifiable credential</a>.
+For example, a <a>verifier</a> might fetch an externally linked revocation
+list while performing status checks on a <a>verifiable credential</a>.
+          </li>
+        </ul>
       </section>
 
       <section class="informative">