Use of the SHAKE One-Way Hash Functions in the Cryptographic Message Syntax (CMS)
draft-ietf-lamps-cms-shakes-18

[Ballot comment]
As per Roman's reply: the document should clarify that values TBD1..TBD4 are defined in another document and should be updated in this draft once the other document gets published.

[Ballot comment]

Thank you for the work put into this document. I second Alexey's DISCUSS that is easy to fix.

Regards,

-éric

== COMMENTS ==

-- Section 4.1 --

Can you check whether the begin and the end of this section are consistent ? I.e. "id-shake128 and id-shake256 OIDs" vs. "output length of SHA256 or SHAKE256" ? I must admit that my knowledge of crypto is not paramount but I find this weird.

-- Section 4.2.1 --

Is there any reason why length are measured in bytes while in other sections it is in bits? Readers can do the math of course but why making the text more complex to parse?

== NITS ==

-- Section 3 --

Why are some object identifier are fully in lowercase and some are a mix of lower and uppercase characters?

[Ballot discuss]
This is a fine document, but I have one quick question:

Values TBD1..TBD4 are not listed in the IANA Considerations section. Should they be?

(Via drafts-lastcall@iana.org): IESG/Authors/WG Chairs:

The IANA Functions Operator has completed its review of draft-ietf-lamps-cms-shakes-11. If any part of this review is inaccurate, please let us know.

The IANA Functions Operator understands that, upon approval of this document, there is a single action which we must complete.

In the SMI Security for S/MIME Module Identifier (1.2.840.113549.1.9.16.0) registry on the Structure of Management Information (SMI) Numbers (MIB Module Registrations) registry page located at:

https://www.iana.org/assignments/smi-numbers/

a single new registration is to be made as follows:

Decimal: [ TBD-at-Registration ]
Description: CMSAlgsForSHAKE-2019
Reference: [ RFC-to-be ]

As this document requests registrations in a Specification Required (see RFC 8126) registry, we will initiate the required Expert Review via a separate request. An expert review will need to be completed before your document can be approved for publication as an RFC.

The IANA Functions Operator understands that this is the only action required to be completed upon approval of this document.

Note:  The actions requested in this document will not be completed until the document has been approved for publication as an RFC. This message is meant only to confirm the list of actions that will be performed.

Thank you,

Sabrina Tanamal
Senior IANA Services Specialist

The following Last Call announcement was sent out (ends 2019-07-03):

From: The IESG
To: IETF-Announce
CC: rdd@cert.org, draft-ietf-lamps-cms-shakes@ietf.org, Russ Housley , lamps-chairs@ietf.org, housley@vigilsec.com, spasm@ietf.org
Reply-To: ietf@ietf.org
Sender:
Subject: Last Call:  (Use of the SHAKE One-way Hash Functions in the Cryptographic Message Syntax (CMS)) to Proposed Standard


The IESG has received a request from the Limited Additional Mechanisms for
PKIX and SMIME WG (lamps) to consider the following document: - 'Use of the
SHAKE One-way Hash Functions in the Cryptographic Message
  Syntax (CMS)'
  as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2019-07-03. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the beginning of
the Subject line to allow automated sorting.

Abstract


  This document describes the conventions for using the SHAKE family of
  hash functions with the Cryptographic Message Syntax (CMS) as one-way
  hash functions with the RSA Probabilistic signature and ECDSA
  signature algorithms, as message digests and message authentication
  codes.  The conventions for the associated signer public keys in CMS
  are also described.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-lamps-cms-shakes/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-lamps-cms-shakes/ballot/


No IPR declarations have been submitted directly on this I-D.


The document contains these normative downward references.
See RFC 3967 for additional information:
    rfc8017: PKCS #1: RSA Cryptography Specifications Version 2.2 (Informational - IETF stream)

Shepherd Write-up for draft-ietf-lamps-cms-shakes-05


(1) What type of RFC is being requested (BCP, Proposed Standard, Internet
Standard, Informational, Experimental, or Historic)?  Why is this the
proper type of RFC?  Is this type of RFC indicated in the title page
header?

  Proposed Standard.  Yes, the header call for Standards Track.
 

(2) The IESG approval announcement includes a Document Announcement
Write-Up.  Please provide such a Document Announcement Write-Up.  Recent
examples can be found in the "Action" announcements for approved
documents.  The approval announcement contains the following sections:

  Technical Summary:

  This document describes the conventions for using the SHAKE family of
  hash functions with the Cryptographic Message Syntax (CMS) as one-way
  hash functions with the RSA Probabilistic signature and ECDSA
  signature algorithms, as message digests and message authentication
  codes.  The conventions for the associated signer public keys in CMS
  are also described.

  Working Group Summary:

    There is consensus for this document in the LAMPS WG.

  Document Quality:

    S/MIME has wide support, and it depends on the CMS.  A few people
    have expressed interest in using SHAKE in their implementations.

  Personnel:

    Russ Housley is the document shepherd.
    Eric Rescorla is the responsible area director.


(3) Briefly describe the review of this document that was performed by
the Document Shepherd.  If this version of the document is not ready for
publication, please explain why the document is being forwarded to the
IESG.

  The document shepherd did a thorough review of the document during
  WG Last Call.  All issues raised have been resolved.


(4) Does the document Shepherd have any concerns about the depth or
breadth of the reviews that have been performed?

  No concerns.


(5) Do portions of the document need review from a particular or from
broader perspective, e.g., security, operational complexity, AAA, DNS,
DHCP, XML, or internationalization?  If so, describe the review that took
place.

  No special review needed.


(6) Describe any specific concerns or issues that the Document Shepherd
has with this document that the Responsible Area Director and/or the IESG
should be aware of?  For example, perhaps he or she is uncomfortable with
certain parts of the document, or has concerns whether there really is a
need for it.  In any event, if the WG has discussed those issues and has
indicated that it still wishes to advance the document, detail those
concerns here.

  No concerns.


(7) Has each author confirmed that any and all appropriate IPR
disclosures required for full conformance with the provisions of BCP 78
and BCP 79 have already been filed.  If not, explain why?

  The authors have explicitly stated that they are unaware of any
  IPR related to this document.


(8) Has an IPR disclosure been filed that references this document?  If
so, summarize any WG discussion and conclusion regarding the IPR
disclosures.

  No IPR disclosures have been submitted against this Internet-Draft.


(9) How solid is the WG consensus behind this document?  Does it
represent the strong concurrence of a few individuals, with others being
silent, or does the WG as a whole understand and agree with it?

  There is consensus for this document in the LAMPS WG.


(10) Has anyone threatened an appeal or otherwise indicated extreme
discontent?  If so, please summarise the areas of conflict in separate
email messages to the Responsible Area Director.  (It should be in a
separate email because this questionnaire is publicly available.)

  No one has threatened an appeal.


(11) Identify any ID nits the Document Shepherd has found in this
document.  (See http://www.ietf.org/tools/idnits/ and the Internet-Drafts
Checklist).  Boilerplate checks are not enough; this check needs to be
thorough.

  This document has a normative reference to Informational RFC 8017,
  which is not already in the downref registry.  See the response to
  question (15) below.
 
 
(12) Describe how the document meets any required formal review criteria,
such as the MIB Doctor, media type, and URI type reviews.

  None needed.


(13) Have all references within this document been identified as either
normative or informative?

  Yes, the references are divided into normative and informative.


(14) Are there normative references to documents that are not ready for
advancement or are otherwise in an unclear state?  If such normative
references exist, what is the plan for their completion?

  All normative references are already published.


(15) Are there downward normative references references (see RFC 3967)?
If so, list these downward references to support the Area Director in the
Last Call procedure.

  This document has a normative reference to Informational RFC 8017.
  I am quite surprised there is not a previous downref to PKCS#1 v2.2.
  I observe that PKCS#1 v2.1 (RFC 3447) is already in the downref
  registry.  Please call out the normative reference to RFC 8017 in the
  IETF Last Call, and then add RFC 8017 to the downref registry.


(16) Will publication of this document change the status of any existing
RFCs?  Are those RFCs listed on the title page header, listed in the
abstract, and discussed in the introduction?  If the RFCs are not listed
in the Abstract and Introduction, explain why, and point to the part of
the document where the relationship of this document to the other RFCs is
discussed.  If this information is not in the document, explain why the
WG considers it unnecessary.

  Publication of this document will not change the status of any other
  documents.


(17) Describe the Document Shepherd's review of the IANA considerations
section, especially with regard to its consistency with the body of the
document.  Confirm that all protocol extensions that the document makes
are associated with the appropriate reservations in IANA registries.
Confirm that any referenced IANA registries have been clearly identified.
Confirm that newly created IANA registries include a detailed
specification of the initial contents for the registry, that allocations
procedures for future registrations are defined, and a reasonable name
for the new registry has been suggested (see RFC 5226).

  One ASN.1 module identifier needs to be assigned by IANA.  In
  addition, it is worth noting that NIST will assign the needed
  algorithm identifiers once the document is approved.


(18) List any new IANA registries that require Expert Review for future
allocations.  Provide any public guidance that the IESG would find useful
in selecting the IANA Experts for these new registries.

  No new IANA registries are needed.


(19) Describe reviews and automated checks performed by the Document
Shepherd to validate sections of the document written in a formal
language, such as XML code, BNF rules, MIB definitions, etc.

  ASN.1 is used.  I compiled the module in Appendix A.