[cabfpub] XMSS became an RFC

[philliph at comodo.com]

What the IETF calls a standard and what is generally regarded as an IETF standard have long been two different things.

This is the same classification as every other IETF specified algorithm has been assigned.


My plan for enabling transition to a quantum-secure crypto scheme is focused on a client-side approach using symmetric key as the basis for authentication and encryption. Basically, use public key capabilities while we have them to pre-share secrets and tickets we can use later on if necessary.

XMSS provides a means of bootstrapping new clients (potentially).


> On Jun 6, 2018, at 3:42 PM, Ryan Sleevi via Public <public at cabforum.org> wrote:
> 
> 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 <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 <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 <public at cabforum.org <mailto:public at cabforum.org>> wrote:
> Re the post quantum crypto discussion, XMSS is now an RFC.
> 
> https://datatracker.ietf.org/doc/rfc8391/ <https://datatracker.ietf.org/doc/rfc8391/>
> 
> 
> _______________________________________________
> Public mailing list
> Public at cabforum.org <mailto:Public at cabforum.org>
> https://cabforum.org/mailman/listinfo/public <https://cabforum.org/mailman/listinfo/public>
> 
> 
> _______________________________________________
> Public mailing list
> Public at cabforum.org
> https://cabforum.org/mailman/listinfo/public

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cabforum.org/pipermail/public/attachments/20180607/2225c161/attachment-0003.html>