[rfc-dist] RFC 9509 on X.509 Certificate Extended Key Usage (EKU) for 5G Network Functions
rfc-editor@rfc-editor.org Thu, 21 March 2024 01:11 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: rfc-dist@ietfa.amsl.com
Delivered-To: rfc-dist@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26AA1C14F6BB; Wed, 20 Mar 2024 18:11:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.658
X-Spam-Level:
X-Spam-Status: No, score=-6.658 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZhmtgT9gzjx2; Wed, 20 Mar 2024 18:11:32 -0700 (PDT)
Received: from rfcpa.amsl.com (rfcpa.amsl.com [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A3C49C14F721; Wed, 20 Mar 2024 18:11:32 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 7A09F8B185; Wed, 20 Mar 2024 18:11:32 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, spasm@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20240321011132.7A09F8B185@rfcpa.amsl.com>
Date: Wed, 20 Mar 2024 18:11:32 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-dist/26Uh6x3zTBQVWU8tQbUwOu5neD8>
Subject: [rfc-dist] RFC 9509 on X.509 Certificate Extended Key Usage (EKU) for 5G Network Functions
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Mar 2024 01:11:33 -0000
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: kondtir@gmail.com,
jani.ekman@nokia.com,
daniel.migault@ericsson.com
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 rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC