Re: [keyassure] Opening issue #21: "Need to specify which crypto

[Chris Palmer <[e-mail]>]

On Mar 7, 2011, at 5:03 PM, Paul Hoffman wrote:

> One specific thing that this author would like to see is what you and others specifically mean by "a slot for SHA-3" and "a plan for SHA-3". To me, those are quite different. We already have slots for SHA-3, SHA-42, and so on; they are not named as such, but they are there.

Change this:

"""
4.3.  TLSA Hash Types

   This document creates a new registry, "Hash Types for TLSA Resource
   Records".  The registry policy is "Specification Required".  The
   initial entries in the registry are:

   Value        Short description       Ref.
   -----------------------------------------------------
   0            No hash used            [This]
   1            SHA-1                   NIST FIPS 180-2
   2            SHA-256                 NIST FIPS 180-2
   3            SHA-384                 NIST FIPS 180-2
   4-254        Unassigned

   Applications to the registry can request specific values that have
   yet to be assigned.
"""

To something like this:

4.3.  TLSA Hash Types

   This document creates a new registry, "Hash Types for TLSA Resource
   Records".  The registry policy is "Specification Required".  The
   initial entries in the registry are:

   Value        Short description       Ref.
   -----------------------------------------------------
   0            No hash used            [This]
   1            SHA-1                   NIST FIPS 180-2
   2            SHA-256                 NIST FIPS 180-2
   3            SHA-384                 NIST FIPS 180-2
   4            Reserved
   5            Reserved
   6-254        Unassigned

   Applications to the registry can request specific values that have
   yet to be assigned. Note that that types 4 and 5 are reserved to
   indicate the SHA-3 algorithm, when it is defined. Future revisions
   to this document SHALL require implementations to support SHA-3, and
   implementors SHOULD prepare for this with a flexible implementation
   strategy.

I don't really speak RFC-ese, but hopefully this makes enough sense. :)


-- 
Chris Palmer
Technology Director, Electronic Frontier Foundation