| Internet-Draft | IETF URN Sub-Namespace for JWT Claims | March 2025 |
| Charabaruk | Expires 4 September 2025 | [Page] |
This document establishes an IETF URN Sub-namespace for use with JSON Web Token claims.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 4 September 2025.¶
Copyright (c) 2025 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
Various systems related to authentication and identity use URIs to identify values and value types. This document creates and registers an IETF URN Sub-namespace, as documented in [RFC3553], to map claims specified in the JSON Web Token Claims registry to URIs.¶
Per [RFC3553], this document registers a new URN Sub-namespace, urn:ietf:params:jwt-claims.¶
There are no additional security considerations beyond those already inherent to URNs or JSON Web Tokens. Security considerations for URNs in general can be found in [RFC8141]. Security considerations for JWTs in general can be found in [RFC7519].¶