IETF Logo Mail Archive

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

Roman Danyliw <rdd@cert.org> Tue, 16 July 2019 20:07 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 BA9D312061D for <spasm@ietfa.amsl.com>; Tue, 16 Jul 2019 13:07:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] 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 QE_Tzk9HqTlV for <spasm@ietfa.amsl.com>; Tue, 16 Jul 2019 13:07:52 -0700 (PDT)
Received: from veto.sei.cmu.edu (veto.sei.cmu.edu [147.72.252.17]) (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 B40CD12060E for <spasm@ietf.org>; Tue, 16 Jul 2019 13:07:52 -0700 (PDT)
Received: from korb.sei.cmu.edu (korb.sei.cmu.edu [10.64.21.30]) by veto.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id x6GK7pDs002585 for <spasm@ietf.org>; Tue, 16 Jul 2019 16:07:51 -0400
DKIM-Filter: OpenDKIM Filter v2.11.0 veto.sei.cmu.edu x6GK7pDs002585
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cert.org; s=yc2bmwvrj62m; t=1563307671; bh=5yygbzAQpMqSKpk1VFxd6dx1744ShXDf85SNQJK0zc8=; h=From:To:Subject:Date:From; b=At32nUHyU7r0JvpNsz3rn9/7nL+jHSgHidyNaGyKQK0dZ6z9w+kV6jUmas6raD019 KsjfwMtPpKfnfOojhGUu6IBiyZe79CZxWJ0IKS7jFC2qgS1xTgr8Nt5Ucm6YO/5dnZ /Ej918mLka7WoIemBS5rmrMsRGhRgMudketP1PhM=
Received: from CASSINA.ad.sei.cmu.edu (cassina.ad.sei.cmu.edu [10.64.28.249]) by korb.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id x6GK7pwe011984 for <spasm@ietf.org>; Tue, 16 Jul 2019 16:07:51 -0400
Received: from MARCHAND.ad.sei.cmu.edu ([10.64.28.251]) by CASSINA.ad.sei.cmu.edu ([10.64.28.249]) with mapi id 14.03.0439.000; Tue, 16 Jul 2019 16:07:51 -0400
From: Roman Danyliw <rdd@cert.org>
To: "spasm@ietf.org" <spasm@ietf.org>
Thread-Topic: AD Review: draft-ietf-lamps-cms-mix-with-psk-05
Thread-Index: AdU8EX/wJ/esCf+5ROODUoLZZ3GXMA==
Date: Tue, 16 Jul 2019 20:07:51 +0000
Message-ID: <359EC4B99E040048A7131E0F4E113AFC01B33D5872@marchand>
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/tkMuMESBPxi2Km0nPWi06c_aKc8>
Subject: [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: Tue, 16 Jul 2019 20:07:55 -0000

Hi!

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.

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

(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"?

** 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.

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

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

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

** 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?

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

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

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

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

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

** 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

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

** Appendix A.1.  Multiple Places.  Typo.  s/resutling/resulting/g

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

v2.23.0 | Report a Bug | By Email