RFC 9901: Selective Disclosure for JSON Web Tokens
In plain English — editorial summary, not part of the RFC
This specification defines a mechanism for the selective disclosure of individual elements of a JSON data structure used as the payload of a JSON Web Signature (JWS). The primary use case is the selective disclosure of JSON Web Token (JWT) claims.
Document record
- Document ID
- RFC9901
- Published
- November 2025
- Authors
- D. Fett; K. Yasuda; B. Campbell
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 88
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 10027Best Current Practice for Security of Cross-Device FlowsCurrent
August 2026
- RFC 9470OAuth 2.0 Step Up Authentication Challenge ProtocolCurrent
September 2023
- RFC 9449OAuth 2.0 Demonstrating Proof of Possession (DPoP)Current
September 2023
- RFC 9396OAuth 2.0 Rich Authorization RequestsCurrent
May 2023
- RFC 9207OAuth 2.0 Authorization Server Issuer IdentificationCurrent
March 2022
- RFC 9126OAuth 2.0 Pushed Authorization RequestsCurrent
September 2021
- RFC 10007Clarification to Processing Key Usage Values During Certificate Revocation List (CRL) ValidationCurrent
June 2026
- RFC 9770Notification of Revoked Access Tokens in the Authentication and Authorization for Constrained Environments (ACE) FrameworkCurrent
June 2025
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?