You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: draft-ietf-oauth-status-list.md
+27-7Lines changed: 27 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -430,21 +430,41 @@ TBD Declare whether JWT and CWT representations can be used interchangeably by t
430
430
This specification requests registration of the following Claims in the
431
431
IANA "JSON Web Token Claims" registry [@IANA.JWT] established by [@!RFC7519].
432
432
433
+
### Registry Contents
434
+
433
435
* Claim Name: `status`
434
436
* Claim Description: Reference to a status or validity mechanism containing up-to-date status information on the JWT.
435
437
* Change Controller: IETF
436
438
* Specification Document(s): [](#status-claim) of this specification
437
439
438
-
<br/>
440
+
## JWT Status Mechanism Methods Registry {#iana-registry}
439
441
440
-
* Claim Name: `status_list`
441
-
* Claim Description: A status list containing up-to-date status information on multiple other JWTs encoded as a bitarray.
442
-
* Change Controller: IETF
443
-
* Specification Document(s): [](#status-list-json) of this specification
442
+
This specification establishes the IANA "Status Mechanism Methods" registry for JWT "status" member values. The registry records the status mechanism method member and a reference to the specification that defines it.
This specification establishes the IANA "Status Mechanism Methods" registry for JWT "status" member values. The registry records the status mechanism method member and a reference to the specification that defines it.
446
+
Status Method Value:
447
+
448
+
> The name requested (e.g., "status_list"). The name is case sensitive. Names may not match other registered names in a case-insensitive manner unless the Designated Experts state that there is a compelling reason to allow an exception.
449
+
450
+
Status Method Description:
451
+
452
+
> Brief description of the status mechanism method.
453
+
454
+
Change Controller:
455
+
456
+
> For Standards Track RFCs, list the "IESG". For others, give the name of the responsible party. Other details (e.g., postal address, email address, home page URI) may also be included.
457
+
458
+
Specification Document(s):
459
+
460
+
> Reference to the document or documents that specify the parameter, preferably including URIs that can be used to retrieve copies of the documents. An indication of the relevant sections may also be included but is not required.
461
+
462
+
### Initial Registry Contents
463
+
464
+
* Status Method Value: `status_list`
465
+
* Status Method Description: A status list containing up-to-date status information on multiple other JWTs encoded as a bitarray.
466
+
* Change Controller: IETF
467
+
* Specification Document(s): [](#referenced-token-jwt) of this specification
0 commit comments