|
Re: [openpgp] SHA3 algorithm ids.
2015-08-09 20:20:39
Just on the process crapology...
On 08/08/15 14:48, Phillip Hallam-Baker wrote:
This is an IANA maintained registry so IANA picks the code points while
they are in charge.
But what is sometimes done when there is a working group working on a
protocol with a lot of code points, the registry is moved out of IANA
control and someone in the WG manages it. This is the way PKIX worked.
That's out of date. We've moved those PKIX registries to IANA and Russ
no longer manages 'em and more importantly here we've put in place a
process for early allocation of IANA code points in RFC 7020. [1]
In terms of code points for use of sha-3 in pgp, my reading of 7120
would be that the list will discuss and the chairs will judge if rough
consensus has been reached at which point the chairs will have the
backing of folks participating in the WG to allocate code points
early.
Cheers,
S.
PS: A nice side-effect of using 7120 - IANA regularly send the IESG a
summary of the early allocations that will soon expire. That's a
great way to kick a WG into finishing a bit of work they ought have
gotten done ages before:-)
[1] https://tools.ietf.org/html/rfc7120
It is also possible that the way to do this would be for a single document
to propose code points for all the active crypto specs.
On Sat, Aug 8, 2015 at 5:21 AM, Werner Koch <wk(_at_)gnupg(_dot_)org> wrote:
Hi!
Now that an official SHA3 specs has been published I would like to see
algorithm ids assigned. Although it is some time until we can publish
rfc-4880bis, it would be useful to agree on the algorithm ids now.
This would be helpful for experimental implementations. Thus what about
this new table with the SHA2 drop in replacements:
ID Algorithm Text Name
-- --------- ---------
1 - MD5 [HAC] "MD5"
2 - SHA-1 [FIPS180] "SHA1"
3 - RIPE-MD/160 [HAC] "RIPEMD160"
4 - Reserved
5 - Reserved
6 - Reserved
7 - Reserved
8 - SHA256 [FIPS180] "SHA256"
9 - SHA384 [FIPS180] "SHA384"
10 - SHA512 [FIPS180] "SHA512"
11 - SHA224 [FIPS180] "SHA224"
12 - SHA3-224 [FIPS202] "SHA3-224"
13 - SHA3-256 [FIPS202] "SHA3-256"
14 - SHA3-384 [FIPS202] "SHA3-384"
15 - SHA3-512 [FIPS202] "SHA3-512"
100 to 110 - Private/Experimental algorithm
Note that I ordered SHA3-224 first; when we did SHA2 we forgot about 224
and thus it ended up out of order.
I am not sure about the text name. Is a dash okay (cf. armor header)?
The OIDS are:
The hexadecimal representations for the
currently defined hash algorithms are as follows:
[...]
- SHA3-224: 0x60, 0x86, 0x48, 0x01, 0x65, 0x03, 0x04, 0x02, 0x07
- SHA3-256: 0x60, 0x86, 0x48, 0x01, 0x65, 0x03, 0x04, 0x02, 0x08
- SHA3-384: 0x60, 0x86, 0x48, 0x01, 0x65, 0x03, 0x04, 0x02, 0x09
- SHA3-512: 0x60, 0x86, 0x48, 0x01, 0x65, 0x03, 0x04, 0x02, 0x0a
The ASN.1 Object Identifiers (OIDs) are as follows:
[...]
- SHA3-224: 2.16.840.1.101.3.4.2.7
- SHA3-256: 2.16.840.1.101.3.4.2.8
- SHA3-384: 2.16.840.1.101.3.4.2.9
- SHA3-512: 2.16.840.1.101.3.4.2.10
The full hash prefixes for these are as follows:
[...]
SHA3-224: 0x30, 0x51, 0x30, 0x0d, 0x06, 0x09, 0x60, 0x86,
0x48, 0x01, 0x65, 0x03, 0x04, 0x02, 0x07, 0x05,
0x00, 0x04, 0x40
SHA3-256: 0x30, 0x51, 0x30, 0x0d, 0x06, 0x09, 0x60, 0x86,
0x48, 0x01, 0x65, 0x03, 0x04, 0x02, 0x07, 0x05,
0x00, 0x04, 0x40
SHA3-384: 0x30, 0x51, 0x30, 0x0d, 0x06, 0x09, 0x60, 0x86,
0x48, 0x01, 0x65, 0x03, 0x04, 0x02, 0x07, 0x05,
0x00, 0x04, 0x40
SHA3-512: 0x30, 0x51, 0x30, 0x0d, 0x06, 0x09, 0x60, 0x86,
0x48, 0x01, 0x65, 0x03, 0x04, 0x02, 0x07, 0x05,
0x00, 0x04, 0x40
Shalom-Salam,
Werner
--
Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
_______________________________________________
openpgp mailing list
openpgp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/openpgp
_______________________________________________
openpgp mailing list
openpgp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/openpgp
_______________________________________________
openpgp mailing list
openpgp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/openpgp
|
|