Hi, Mike. You're most welcome, and thank you for sending us the links to your writeup!
Best, Lynne (Lynne Bartholomew / RFC Production Center) > On Oct 30, 2025, at 4:04 PM, Michael Jones <[email protected]> > wrote: > > Thanks for everything you did, Lynne! I wrote about this one at > https://www.linkedin.com/posts/selfissued_fully-specified-algorithms-for-jose-and-cose-activity-7389784719816769536-O8LS/ > and https://self-issued.info/?p=2762. > > -- Mike > > -----Original Message----- > From: Lynne Bartholomew <[email protected]> > Sent: Thursday, October 30, 2025 1:02 PM > To: Michael Jones <[email protected]> > Cc: [email protected]; [email protected]; [email protected]; > [email protected]; [email protected]; [email protected]; > [email protected] > Subject: Re: AUTH48: RFC-to-be 9864 > <draft-ietf-jose-fully-specified-algorithms-13> > > 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%2Fstandards&data=05%7C02%7C%7C267a6cd314ae4e0a320f08de17ef39ed%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638974513395385732%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=W9MXub5v1tfz0KYJhBA8SbkuL%2BmxR29%2BaW8zFEowxRo%3D&reserved=0) >> 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.i/ >> etf.org%2Fmailman%2Flistinfo%2Fietf-announce&data=05%7C02%7C%7C267a6cd >> 314ae4e0a320f08de17ef39ed%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7 >> C638974513395405486%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIl >> YiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0 >> %7C%7C%7C&sdata=zXNgGzC%2FWwug9ru4Pn%2BqMOjKH2HlYrEUKn%2BTtuwlxJE%3D&r >> eserved=0 >> >> https://mailm/ >> an.rfc-editor.org%2Fmailman%2Flistinfo%2Frfc-dist&data=05%7C02%7C%7C26 >> 7a6cd314ae4e0a320f08de17ef39ed%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1% >> 7C0%7C638974513395426070%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRyd >> WUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3 >> D%7C0%7C%7C%7C&sdata=24MmfrqGzCAmKS1qEg8OruxZ0Pb4xrLh3GAmMV6B47g%3D&re >> served=0 >> >> For searching the RFC series, see >> https://www.r/ >> fc-editor.org%2Fsearch&data=05%7C02%7C%7C267a6cd314ae4e0a320f08de17ef3 >> 9ed%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638974513395444574%7C >> Unknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAi >> OiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=DnICPh >> FwupDmGPvp9whsmHFac6iJxJJ7NHxORrNGLTI%3D&reserved=0 >> For downloading RFCs, see >> https://www.r/ >> fc-editor.org%2Fretrieve%2Fbulk&data=05%7C02%7C%7C267a6cd314ae4e0a320f >> 08de17ef39ed%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638974513395 >> 462554%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDA >> wMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sda >> ta=9Kc8swNkwGaduZ6voFGeZEyZ7Me%2FBSdh04wx9eUw%2BWs%3D&reserved=0 >> >> 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]
