[Gen-art] draft-ietf-lamps-5480-ku-clarifications-01

worley@ariadne.com Mon, 02 March 2020 04:00 UTC

Return-Path: <worley@alum.mit.edu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86A493A0AAB for <gen-art@ietfa.amsl.com>; Sun, 1 Mar 2020 20:00:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.983
X-Spam-Level:
X-Spam-Status: No, score=-0.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcastmailservice.net
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 4HQT2hHKk7UZ for <gen-art@ietfa.amsl.com>; Sun, 1 Mar 2020 20:00:32 -0800 (PST)
Received: from resqmta-ch2-05v.sys.comcast.net (resqmta-ch2-05v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:37]) (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 A85FE3A0AAA for <gen-art@ietf.org>; Sun, 1 Mar 2020 20:00:31 -0800 (PST)
Received: from resomta-ch2-16v.sys.comcast.net ([69.252.207.112]) by resqmta-ch2-05v.sys.comcast.net with ESMTP id 8c6EjSD2P9yxw8cFqjAMEq; Mon, 02 Mar 2020 04:00:30 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20180828_2048; t=1583121630; bh=gU7yxbZkDoh4d73aG8tCA5rO3nPYMkpWT/zVhcTE+KA=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=OMHUqjc1/GFcsS93+/5BU5Q18QVL1JlvbXPvK7vsurNx7loRI8KdKJjWwT6gMTBnu IAbYvnyDYARYtLEXYGghic8uoJVfDHazH02+cEX6wyurVIOC59fexUFrFZO4dU4NPm Ny3a/uDktN8MtL/OozqmdBR2WKP/l/jcYpfuSpN3rNiOp3xK9K+Q3eblOycNF3gl3p uzxpgYuFrCIZMeQYJ+EDT0NIdrBE+i5cD4LFm+doI1tttkg9Vlmysb6A5ev2CabjP8 X7xwIxj/ocz+YvwV9aCXHbiB9Dc+g8VGh8+u/B+EmlsH4HO7deRdQKh18Jvdplrg71 6Ih2uHDVurEKQ==
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4600:c190:222:fbff:fe91:d396]) by resomta-ch2-16v.sys.comcast.net with ESMTPA id 8cFpjv8ns7vgv8cFpj9B8u; Mon, 02 Mar 2020 04:00:30 +0000
X-Xfinity-VMeta: sc=-100.00;st=legit
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id 02240RhD010191; Sun, 1 Mar 2020 23:00:27 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id 02240QUW010181; Sun, 1 Mar 2020 23:00:26 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
To: Sean Turner <sean@sn3rd.com>
Cc: gen-art@ietf.org, draft-ietf-lamps-5480-ku-clarifications.all@ietf.org, last-call@ietf.org, spasm@ietf.org
In-Reply-To: <6888D55C-5A3D-4C8E-AF6C-ED96235A1691@sn3rd.com> (sean@sn3rd.com)
Sender: worley@ariadne.com
Date: Sun, 01 Mar 2020 23:00:26 -0500
Message-ID: <878skjcso5.fsf@hobgoblin.ariadne.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/l7au2YojMTsSUrJWoMkGT-nBe5s>
Subject: [Gen-art] draft-ietf-lamps-5480-ku-clarifications-01
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Mar 2020 04:00:36 -0000

Looking at draft-ietf-lamps-5480-ku-clarifications-01, these points
occur to me:

   1.  Introduction

   This document corrects this omission, by updating Section 3 of
   [RFC5480] to make it clear that neither keyEncipherment nor the
   dataEncipherment key usage bits are set for key agreement algorithms.

I think it would be more accurate to say something like "neither ... are
set in certificates that specify key agreement algorithms" -- usage bits
are logically a component of a certificate rather than a feature of an
algorithm.

But it's unclear to me whether id-ecPublicKey is only used in key
agreement certificates.  RFC 5480 states that if the cert uses id-ecDH
or id-ecMQV and provides keyUsage, then keyAgreement must be set.  So
it's clear that certs with id-ecDH or id-ecMQV are key agreement certs.
But RFC 5480 says that if the cert lists id-ecPublicKey, then
keyAgreement is optional.  That suggests to me that some certs can use
id-ecPublicKey without being key agreement certs.  In turn, section 1 of
this I-D suggests the I-D is not intended to apply to those certs, but
section 3 seems to apply to them anyway.

To try to distill it to one sentence:  Can id-ecPublicKey appear in
certs that are not for key agreement, and if so, are keyEncipherment and
dataEncipherment allowed in the keyUsage of those certs?

   3.  Updates to Section 3

   If the keyUsage extension is present in a certificate that indicates
   in SubjectPublicKeyInfo, then following values MUST NOT be present:
---^

Is "id-ecPublicKey" missing here?

   If the keyUsage extension is present in a certificate that indicates
   id-ecDH or id-ecMQV in SubjectPublicKeyInfo, then the following
   values also MUST NOT be present:

Is it a fact that all certificates with these three algorithms are
certificates for key agreement?  If so, it would be nice to state that
either in section 3 or section 1, to show how section 3 is connected
with "for key agreement algorithms" in section 1.  Otherwise, the
connection between the two requires information that is stated
elsewhere.

Dale