Hi, Mike. On behalf of the RPC, congratulations on the publication of this document, and thank you for your attentiveness to it!
Best, Lynne Bartholomew RFC Production Center > On Oct 28, 2025, at 10:01 AM, Michael Jones <[email protected]> > wrote: > > Perfect! This is one that the world has been wanting and waiting for! There > are already normative reference to it both from IETF specs and also W3C, FIDO > Alliance, and OpenID Foundation specifications. > > Best wishes, > -- Mike > From: [email protected] > Subject: RFC 9864 on Fully-Specified Algorithms for JSON Object Signing and > Encryption (JOSE) and CBOR Object Signing and Encryption (COSE) > Date: October 30, 2025 at 12:50:15 PM PDT > To: [email protected], [email protected] > Cc: [email protected], [email protected], [email protected] > > A new Request for Comments is now available in online RFC libraries. > > > RFC 9864 > > Title: Fully-Specified Algorithms for JSON Object > Signing and Encryption (JOSE) and CBOR > Object Signing and Encryption (COSE) > Author: M.B. Jones, > O. Steele > Status: Standards Track > Stream: IETF > Date: 2025-10-30 > Mailbox: [email protected], > [email protected] > Pages: 16 > Updates: RFC 7518, RFC 8037, RFC 9053 > > I-D Tag: draft-ietf-jose-fully-specified-algorithms-13.txt > > URL: https://www.rfc-editor.org/info/rfc9864 > > DOI: 10.17487/RFC9864 > > This specification refers to cryptographic algorithm identifiers that > fully specify the cryptographic operations to be performed, including > any curve, key derivation function (KDF), and hash functions, as > being "fully specified". It refers to cryptographic algorithm > identifiers that require additional information beyond the algorithm > identifier to determine the cryptographic operations to be performed > as being "polymorphic". This specification creates fully-specified > algorithm identifiers for registered JSON Object Signing and > Encryption (JOSE) and CBOR Object Signing and Encryption (COSE) > polymorphic algorithm identifiers, enabling applications to use only > fully-specified algorithm identifiers. It deprecates those > polymorphic algorithm identifiers. > > This specification updates RFCs 7518, 8037, and 9053. It deprecates > polymorphic algorithms defined by RFCs 8037 and 9053 and provides > fully-specified replacements for them. It adds to the instructions to > designated experts in RFCs 7518 and 9053. > > This document is a product of the Javascript Object Signing and Encryption > 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 > -- auth48archive mailing list -- [email protected] To unsubscribe send an email to [email protected]
