For those not familiar with the IETF process, there are four independent document streams: IETF, IRTF, IAB, and Independent
Further, there are different document statuses - https://tools.ietf.org/html/rfc1796 provides information about that, aptly titled "Not all RFCs are Standards" This particular document is published under the IRTF Informational stream - meaning it's not itself a Proposed Standard - but documents the algorithm presented. This is not terribly unfamiliar for CAs - RFC 3447 is itself an Informational document, but describes the core of RSA signatures and keys. Algorithms having an RFC does not itself represent an endorsement of the algorithm specified - merely a consistent and stable reference for the algorithm. If this is as clear as Mississippi Mud, well, the IETF and IAB hears you, which is why https://trac.tools.ietf.org/bof/trac/#General the RFC++ BOF exists, to gather feedback from the community and help make it clearer what an "RFC" means. On Wed, Jun 6, 2018 at 9:19 AM, philliph--- via Public <[email protected]> wrote: > Re the post quantum crypto discussion, XMSS is now an RFC. > > https://datatracker.ietf.org/doc/rfc8391/ > > > _______________________________________________ > Public mailing list > [email protected] > https://cabforum.org/mailman/listinfo/public > >
_______________________________________________ Public mailing list [email protected] https://cabforum.org/mailman/listinfo/public
