Update draft-ietf-oauth-status-list.md

Co-authored-by: Christian Bormann <8774236+c2bo@users.noreply.github.com>
oauth-wg · Jan 31, 2025 · c7e1ea7 · c7e1ea7
1 parent 30d9572
commit c7e1ea7
Showing 1 changed file with 8 additions and 8 deletions.
diff --git a/draft-ietf-oauth-status-list.md b/draft-ietf-oauth-status-list.md
@@ -903,14 +903,14 @@ Alternatively, the Status Issuer may use the same web-based key resolution that
 ┌────────┐  host keys  ┌──────────────────────┐
 │ Issuer ├────────┬───►│ .well-known metadata │
 └─┬──────┘        │    └──────────────────────┘
-  ▼ update status │                           
-┌───────────────┐ │                           
-│ Status Issuer ├─┘                           
-└─┬─────────────┘                             
-  ▼ provide Status List                       
-┌─────────────────┐                           
-│ Status Provider │                           
-└─────────────────┘                           
+  ▼ update status │
+┌───────────────┐ │
+│ Status Issuer ├─┘
+└─┬─────────────┘
+  ▼ provide Status List
+┌─────────────────┐
+│ Status Provider │
+└─────────────────┘
 ~~~
 If the Issuer of the Referenced Token is a different entity than the Status Issuer, then the keys used for the Status List Token may be cryptographically linked, e.g. by an Certificate Authority through an x.509 PKI. The certificate of the Issuer for the Referenced Token and the Status Issuer should be issued by the same Certificate Authority and the Status Issuer's certificate should utilize [extended key usage](#eku).