Re: [lamps] AD Review: draft-ietf-lamps-cms-mix-with-psk-05

Roman Danyliw <rdd@cert.org> Fri, 19 July 2019 23:47 UTC

Return-Path: <rdd@cert.org>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DFB851200C4 for <spasm@ietfa.amsl.com>; Fri, 19 Jul 2019 16:47:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, TRACKER_ID=0.1] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cert.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8gkn5EzF8aIR for <spasm@ietfa.amsl.com>; Fri, 19 Jul 2019 16:47:39 -0700 (PDT)
Received: from taper.sei.cmu.edu (taper.sei.cmu.edu [147.72.252.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A0047120033 for <spasm@ietf.org>; Fri, 19 Jul 2019 16:47:39 -0700 (PDT)
Received: from delp.sei.cmu.edu (delp.sei.cmu.edu [10.64.21.31]) by taper.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id x6JNlcOm007595; Fri, 19 Jul 2019 19:47:38 -0400
DKIM-Filter: OpenDKIM Filter v2.11.0 taper.sei.cmu.edu x6JNlcOm007595
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cert.org; s=yc2bmwvrj62m; t=1563580058; bh=LM+mljsx2LtscnvqWb43hArtYMhD3XapwdQkgB/iwnU=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=jDyNhZGVQ5luFWza3l82ETBUGfn/nVsaIIMtp9QSi+SJEUkQXMDv4ZgYJ2PztNTnz dNV7qUeMCJBdwKIx0REmF1gxipJ764UBuM+5/6MZ/LM4c8BRZ4TtFVnoz4OXtRsEdM OEHCoMDgzgnQrJQnebVK9laMAWmBbFxl66skrWAE=
Received: from CASCADE.ad.sei.cmu.edu (cascade.ad.sei.cmu.edu [10.64.28.248]) by delp.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id x6JNlZHP023362; Fri, 19 Jul 2019 19:47:35 -0400
Received: from MARCHAND.ad.sei.cmu.edu ([10.64.28.251]) by CASCADE.ad.sei.cmu.edu ([10.64.28.248]) with mapi id 14.03.0439.000; Fri, 19 Jul 2019 19:47:34 -0400
From: Roman Danyliw <rdd@cert.org>
To: Russ Housley <housley@vigilsec.com>
CC: "spasm@ietf.org" <spasm@ietf.org>
Thread-Topic: [lamps] AD Review: draft-ietf-lamps-cms-mix-with-psk-05
Thread-Index: AdU8EX/wJ/esCf+5ROODUoLZZ3GXMAA2of4AAGgHecA=
Date: Fri, 19 Jul 2019 23:47:34 +0000
Message-ID: <359EC4B99E040048A7131E0F4E113AFC01B33DBB8F@marchand>
References: <359EC4B99E040048A7131E0F4E113AFC01B33D5872@marchand> <8F78EFC7-1327-411D-AD08-707D6B3480E2@vigilsec.com>
In-Reply-To: <8F78EFC7-1327-411D-AD08-707D6B3480E2@vigilsec.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.64.22.6]
Content-Type: multipart/alternative; boundary="_000_359EC4B99E040048A7131E0F4E113AFC01B33DBB8Fmarchand_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/SlGV1Qzu-awEwYDJkXj4fAZouy4>
Subject: Re: [lamps] AD Review: draft-ietf-lamps-cms-mix-with-psk-05
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Jul 2019 23:47:42 -0000

Hi Russ!

Sounds good on all of the numbered items; and on waiting for all of the feedback from IETF LC to produce an update.

Thanks,
Roman

From: Russ Housley [mailto:housley@vigilsec.com]
Sent: Wednesday, July 17, 2019 2:08 PM
To: Roman Danyliw <rdd@cert.org>
Cc: spasm@ietf.org
Subject: Re: [lamps] AD Review: draft-ietf-lamps-cms-mix-with-psk-05

Roman:

Thanks for the careful review.  I will wait to see what other IETF Last Call comments come along before posting a revision.

The following is my AD review of draft-ietf-lamps-cms-mix-with-psk-05.  Given the substance of these comments, it can be handled with IETF LC comments.

(1) Section 9.  The object identifier is called "id-mod-cms-ori-psk-2017" in the IANA section (Section 9) but "id-mod-cms-ori-psk-2019" in the ASN.1 Module (Section 6).  Seems like they should be the same.

Good catch.  I have changes it to id-mod-cms-ori-psk-2019.

(2) Section B.1.  This section does not list the plaintext content

It is true.  I'll add it, but it is the same as B.3.

Alice encrypts the content using AES-256-GCM with the content-
encryption key.  The 12-octet nonce used is:
   dbaddecaf888cafebabeface

The plaintext is:
   48656c6c6f2c20776f726c6421

The resulting ciphertext is:
   fc6d6f823e3ed2d209d0c6ffcf

The resulting 12-octet authentication tag is:
   550260c42e5b29719426c1ff

(3) Improved references:

** Section 1.  Is there a citation that can be provided for the obvious "The invention of a large-scale quantum computer would pose a serious challenge for the cryptographic algorithms that are widely deployed  today"?

   [S1994]    Shor, P., "Algorithms for Quantum Computation: Discrete
              Logarithms and Factoring", Proceedings of the 35th Annual
              Symposium on Foundations of Computer Science, 1994, pp.
              124-134.

** Section 1.  Is there a citation that can be provided for "It is an open question whether or not it is feasible to build  a large-scale quantum computer ...".  Perhaps:
[NAS2019] National Academies of Sciences, Engineering, and Medicine, "Quantum Computing: Progress and Prospects", The National Academies Press, DOI 10.17226/25196, 2019.

Yes, I'll add that reference.


** Section 1.  Is there a citation that can be provided for "there are longstanding concerns about undisclosed trapdoors in Diffie-Hellman paramters"?

   [FGHT2016] Fried, J., Gaudry, P., Heninger, N., and E. Thome, "A
              kilobit hidden SNFS discrete logarithm computation",
              Cryptology ePrint Archive, Report 2016/961, 2016.
              https://eprint.iacr.org/2016/961.pdf.


(4) Editorial Nits
** Section 1. Recommend weakening the statement.  s/invulnerable to an attacker/resistant to an attacker/

Yes, that is better.


** Section 1.  Typo.  s/Diffie-Hellamn/Diffie-Hellman/

Fixed.


** Section 3 and 4.  Since Section 2 calls out that there two techniques, keyTransPSK and keyAgreePSK, should the section 3 and 4 titles be those names instead of the underlying CMS data structure names?

Okay.  The section titles have been changed.


** Section 5.  Typo.  s/ fo / of /

Fixed.


** Section 5.  Typo?.  s/deines/identifies/

No, it should be "defines"


** Section 7.  Typo.  s/materail/material/

Fixed.


** Section 7.  Typo. /an purpose/a purpose/

Fixed.


** Section 7.  Typo.  Consistently choose either "implementers" or "implementors"

There were many more "implementers", so I went with that spelling.


** Section 7.  I think it would be helpful to move the text on the ProVerif proof from the Acknowledgements up to the Security Considerations section

Done.


** Appendix A/B.  Multiple Typos.  s/omited/omitted/g

Fixed.  (I found it in two places.)


** Appendix A.*. Mutiple Places.  Typo.  s/resutling/resulting/g

Fixed. (I found it in four places.)

Russ