Sorry for coming in a bit after the deadline -- my first attempt to research this failed to find the right keywords and I only got back to it now. Should this document include a statement about which keyUsage value(s) may be consistent with the new EKU, akin to the list in §4.2.1.12 of RFC 5280? -Ben On Fri, Aug 25, 2023 at 01:56:32PM -0700, The IESG wrote: > > The IESG has received a request from the Limited Additional Mechanisms for > PKIX and SMIME WG (lamps) to consider the following document: - 'X.509 > Certificate Extended Key Usage (EKU) for 5G Network Functions' > <draft-ietf-lamps-nf-eku-01.txt> as Proposed Standard > > The IESG plans to make a decision in the next few weeks, and solicits final > comments on this action. Please send substantive comments to the > last-call@xxxxxxxx mailing lists by 2023-09-08. Exceptionally, comments may > be sent to iesg@xxxxxxxx instead. In either case, please retain the beginning > of the Subject line to allow automated sorting. > > Abstract > > > RFC 5280 specifies several extended key purpose identifiers > (KeyPurposeIds) for X.509 certificates. This document defines > encrypting JSON objects in HTTP messages, JSON Web Token (JWT) 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. > > > > > The file can be obtained via > https://datatracker.ietf.org/doc/draft-ietf-lamps-nf-eku/ > > > The following IPR Declarations may be related to this I-D: > > https://datatracker.ietf.org/ipr/5966/ > > > > > > > _______________________________________________ > IETF-Announce mailing list > IETF-Announce@xxxxxxxx > https://www.ietf.org/mailman/listinfo/ietf-announce -- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
