A new Request for Comments is now available in online RFC libraries.

        
        RFC 9509

        Title:      X.509 Certificate Extended Key Usage (EKU)
                    for 5G Network Functions 
        Author:     T. Reddy.K,
                    J. Ekman,
                    D. Migault
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2024
        Mailbox:    [email protected],
                    [email protected],
                    [email protected]
        Pages:      9
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-lamps-nf-eku-05.txt

        URL:        https://www.rfc-editor.org/info/rfc9509

        DOI:        10.17487/RFC9509

RFC 5280 specifies several extended key purpose identifiers
(KeyPurposeIds) for X.509 certificates. This document defines
encrypting JSON objects in HTTP messages, using JSON Web Tokens
(JWTs), and signing the OAuth 2.0 access tokens KeyPurposeIds for
inclusion in the Extended Key Usage (EKU) extension of X.509 v3
public key certificates used by Network Functions (NFs) for the 5G
System.

This document is a product of the Limited Additional Mechanisms for PKIX and 
SMIME Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email protected].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC

_______________________________________________
IETF-Announce mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ietf-announce

Reply via email to