draft-ietf-lamps-cms-shakes-16.txt   draft-ietf-lamps-cms-shakes-17.txt 
LAMPS WG P. Kampanakis LAMPS WG P. Kampanakis
Internet-Draft Cisco Systems Internet-Draft Cisco Systems
Updates: 3370 (if approved) Q. Dang Updates: 3370 (if approved) Q. Dang
Intended status: Standards Track NIST Intended status: Standards Track NIST
Expires: February 8, 2020 August 7, 2019 Expires: February 9, 2020 August 8, 2019
Use of the SHAKE One-way Hash Functions in the Cryptographic Message Use of the SHAKE One-way Hash Functions in the Cryptographic Message
Syntax (CMS) Syntax (CMS)
draft-ietf-lamps-cms-shakes-16 draft-ietf-lamps-cms-shakes-17
Abstract Abstract
This document updates the "Cryptographic Message Syntax Algorithms" This document updates the "Cryptographic Message Syntax Algorithms"
(RFC3370) and describes the conventions for using the SHAKE family of (RFC3370) and describes the conventions for using the SHAKE family of
hash functions in the Cryptographic Message Syntax as one-way hash hash functions in the Cryptographic Message Syntax as one-way hash
functions with the RSA Probabilistic signature and ECDSA signature functions with the RSA Probabilistic signature and ECDSA signature
algorithms. The conventions for the associated signer public keys in algorithms. The conventions for the associated signer public keys in
CMS are also described. CMS are also described.
skipping to change at page 1, line 37 skipping to change at page 1, line 37
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on February 8, 2020. This Internet-Draft will expire on February 9, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 34 skipping to change at page 2, line 34
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 12
8.1. Normative References . . . . . . . . . . . . . . . . . . 12 8.1. Normative References . . . . . . . . . . . . . . . . . . 12
8.2. Informative References . . . . . . . . . . . . . . . . . 13 8.2. Informative References . . . . . . . . . . . . . . . . . 13
Appendix A. ASN.1 Module . . . . . . . . . . . . . . . . . . . . 14 Appendix A. ASN.1 Module . . . . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18
1. Change Log 1. Change Log
[ EDNOTE: Remove this section before publication. ] [ EDNOTE: Remove this section before publication. ]
o draft-ietf-lamps-cms-shake-17:
* Minor updates for EDNOTE accuracy.
o draft-ietf-lamps-cms-shake-16: o draft-ietf-lamps-cms-shake-16:
* Minor nits. * Minor nits.
* Using bytes instead of bits for consistency. * Using bytes instead of bits for consistency.
o draft-ietf-lamps-cms-shake-15: o draft-ietf-lamps-cms-shake-15:
* Minor editorial nits. * Minor editorial nits.
skipping to change at page 6, line 27 skipping to change at page 6, line 27
id-shake256 OBJECT IDENTIFIER ::= { joint-iso-itu-t(2) id-shake256 OBJECT IDENTIFIER ::= { joint-iso-itu-t(2)
country(16) us(840) organization(1) gov(101) csor(3) country(16) us(840) organization(1) gov(101) csor(3)
nistAlgorithm(4) 2 12 } nistAlgorithm(4) 2 12 }
In this specification, when using the id-shake128 or id-shake256 In this specification, when using the id-shake128 or id-shake256
algorithm identifiers, the parameters MUST be absent. That is, the algorithm identifiers, the parameters MUST be absent. That is, the
identifier SHALL be a SEQUENCE of one component, the OID. identifier SHALL be a SEQUENCE of one component, the OID.
[I-D.ietf-lamps-pkix-shake] [ EDNOTE: Update reference with the RFC [I-D.ietf-lamps-pkix-shake] [ EDNOTE: Update reference with the RFC
when it is ready ] defines two identifiers for RSASSA-PSS signatures when it is published. ] defines two identifiers for RSASSA-PSS
using SHAKEs which we include here for convenience. signatures using SHAKEs which we include here for convenience. [
EDNOTE: Update the TBD1-2 reference when the RFC (ietf-lamps-pkix-
shake) is published. ]
id-RSASSA-PSS-SHAKE128 OBJECT IDENTIFIER ::= { iso(1) id-RSASSA-PSS-SHAKE128 OBJECT IDENTIFIER ::= { iso(1)
identified-organization(3) dod(6) internet(1) identified-organization(3) dod(6) internet(1)
security(5) mechanisms(5) pkix(7) algorithms(6) security(5) mechanisms(5) pkix(7) algorithms(6)
TBD1 } TBD1 }
id-RSASSA-PSS-SHAKE256 OBJECT IDENTIFIER ::= { iso(1) id-RSASSA-PSS-SHAKE256 OBJECT IDENTIFIER ::= { iso(1)
identified-organization(3) dod(6) internet(1) identified-organization(3) dod(6) internet(1)
security(5) mechanisms(5) pkix(7) algorithms(6) security(5) mechanisms(5) pkix(7) algorithms(6)
TBD2 } TBD2 }
The same RSASSA-PSS algorithm identifiers can be used for identifying The same RSASSA-PSS algorithm identifiers can be used for identifying
public keys and signatures. public keys and signatures.
[I-D.ietf-lamps-pkix-shake] [ EDNOTE: Update reference with the RFC [I-D.ietf-lamps-pkix-shake] [ EDNOTE: Update reference with the RFC
when it is ready ] also defines two algorithm identifiers of ECDSA when it is published. ] also defines two algorithm identifiers of
signatures using SHAKEs which we include here for convenience. ECDSA signatures using SHAKEs which we include here for convenience.
[ EDNOTE: Update the TBD3-4 reference when the RFC (ietf-lamps-pkix-
shake) is published. ]
id-ecdsa-with-shake128 OBJECT IDENTIFIER ::= { iso(1) id-ecdsa-with-shake128 OBJECT IDENTIFIER ::= { iso(1)
identified-organization(3) dod(6) internet(1) identified-organization(3) dod(6) internet(1)
security(5) mechanisms(5) pkix(7) algorithms(6) security(5) mechanisms(5) pkix(7) algorithms(6)
TBD3 } TBD3 }
id-ecdsa-with-shake256 OBJECT IDENTIFIER ::= { iso(1) id-ecdsa-with-shake256 OBJECT IDENTIFIER ::= { iso(1)
identified-organization(3) dod(6) internet(1) identified-organization(3) dod(6) internet(1)
security(5) mechanisms(5) pkix(7) algorithms(6) security(5) mechanisms(5) pkix(7) algorithms(6)
TBD4 } TBD4 }
The parameters for the four RSASSA-PSS and ECDSA identifiers MUST be The parameters for the four RSASSA-PSS and ECDSA identifiers MUST be
absent. That is, each identifier SHALL be a SEQUENCE of one absent. That is, each identifier SHALL be a SEQUENCE of one
component, the OID. component, the OID.
Two object identifiers for KMACs using SHAKE128 and SHAKE256 as Two object identifiers for KMACs using SHAKE128 and SHAKE256 as
defined in by the National Institute of Standards and Technology defined in by the National Institute of Standards and Technology
(NIST) in [shake-nist-oids] [EDNOTE: Make sure NIST has published (NIST) in [shake-nist-oids] and we include them here for convenience.
these. ] and we include them here for convenience.
id-KmacWithSHAKE128 OBJECT IDENTIFIER ::= { joint-iso-itu-t(2) id-KmacWithSHAKE128 OBJECT IDENTIFIER ::= { joint-iso-itu-t(2)
country(16) us(840) organization(1) gov(101) csor(3) country(16) us(840) organization(1) gov(101) csor(3)
nistAlgorithm(4) 2 19 } nistAlgorithm(4) 2 19 }
id-KmacWithSHAKE256 OBJECT IDENTIFIER ::= { joint-iso-itu-t(2) id-KmacWithSHAKE256 OBJECT IDENTIFIER ::= { joint-iso-itu-t(2)
country(16) us(840) organization(1) gov(101) csor(3) country(16) us(840) organization(1) gov(101) csor(3)
nistAlgorithm(4) 2 20 } nistAlgorithm(4) 2 20 }
The parameters for id-KmacWithSHAKE128 and id-KmacWithSHAKE256 are The parameters for id-KmacWithSHAKE128 and id-KmacWithSHAKE256 are
 End of changes. 7 change blocks. 
10 lines changed or deleted 16 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/