Re: [Spasm] New Version Notification for draft-wconner-blake2sigs-00.txt

As a matter of taste, I’d prefer to see the Object Identifiers assigned in the PKIX algorithm arc:
https://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml#smi-numbers-1.3.6.1.5.5.7.6 <https://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml#smi-numbers-1.3.6.1.5.5.7.6>

The Object Identifiers will be slightly smaller, but not enough to argue about.  My preference is to have them assigned in an arc that is managed by IANA.

I think more needs to be said about the parameters field.  For example, RFC 4055 provides a syntax for parameters for RSASSA-PSS
and RSAES-OAEP.  I think that the intent here is that the object identifier implies a value for each of those parameters.  The text needs to be expanded to give the details.  Using RSAES-OAEP as an example, you need to say that the hashFunc is BLAKE2b-512, the maskGenFunc is MGF1 with BLAKE2b-512, and the pSourceFunc is pSpecifiedEmptyIdentifier (which in the nullOctetString).

Security considerations are needed.  At a minimum, you should point to the security considerations in RFC 5280 and https://blake2.net/blake2_20130129.pdf <https://blake2.net/blake2_20130129.pdf>.

Russ

> On Apr 28, 2017, at 12:40 PM, William Conner <wconner@google.com> wrote:
> 
> I believe that this submission is relevant to this working group.  Feedback welcome.
> 
> Thanks,
> William
> 
> ---------- Forwarded message ----------
> From: <internet-drafts@ietf.org <mailto:internet-drafts@ietf.org>>
> Date: Fri, Apr 14, 2017 at 9:51 AM
> Subject: New Version Notification for draft-wconner-blake2sigs-00.txt
> To: Adam Langley <agl@google.com <mailto:agl@google.com>>, William Conner <wconner@google.com <mailto:wconner@google.com>>, Andrei Popov <Andrei.Popov@microsoft.com <mailto:Andrei.Popov@microsoft.com>>, Andrei Popov <andrei.popov@microsoft.com <mailto:andrei.popov@microsoft.com>>, Ryan Sleevi <sleevi@google.com <mailto:sleevi@google.com>>
> 
> 
> 
> A new version of I-D, draft-wconner-blake2sigs-00.txt
> has been successfully submitted by William Conner and posted to the
> IETF repository.
> 
> Name:           draft-wconner-blake2sigs
> Revision:       00
> Title:          BLAKE2 Algorithms and Identifiers for use in the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile
> Document date:  2017-04-14
> Group:          Individual Submission
> Pages:          6
> URL:            https://www.ietf.org/internet-drafts/draft-wconner-blake2sigs-00.txt <https://www.ietf.org/internet-drafts/draft-wconner-blake2sigs-00.txt>
> Status:         https://datatracker.ietf.org/doc/draft-wconner-blake2sigs/ <https://datatracker.ietf.org/doc/draft-wconner-blake2sigs/>
> Htmlized:       https://tools.ietf.org/html/draft-wconner-blake2sigs-00 <https://tools.ietf.org/html/draft-wconner-blake2sigs-00>
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-wconner-blake2sigs-00 <https://datatracker.ietf.org/doc/html/draft-wconner-blake2sigs-00>
> 
> 
> Abstract:
>    This document describes the conventions for using the BLAKE2b-512
>    hash function with each of the following signature algorithms: RSA
>    Public-Key Cryptography Standards #1 version 1.5 (RSA PKCS#1 v1.5),
>    RSA Probabilistic Signature Scheme (RSASSA-PSS), RSA Encryption
>    Scheme - Optimal Asymmetric Encryption Padding (RSAES-OAEP), Elliptic
>    Curve Digital Signature Algorithm (ECDSA), and Edwards-curve Digital
>    Signature Algorithm (EdDSA).  This specification applies to the
>    Internet X.509 Public Key Infrastructure (PKI) when digital
>    signatures are used to sign certificates and certificate revocation
>    lists (CRLs).  This document also specifies the object identifiers
>    (OIDs) for the combinations of the BLAKE2b-512 hash function with the
>    aforementioned signature algorithms.
> 
> 
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org <http://tools.ietf.org/>.
> 
> The IETF Secretariat
> 
> 
> _______________________________________________
> Spasm mailing list
> Spasm@ietf.org
> https://www.ietf.org/mailman/listinfo/spasm