[lamps] RFC 5480 clarification for KeyUsages: keyEncipherment and dataEncipherment
Sean Turner <sean@sn3rd.com> Sat, 23 March 2019 22:19 UTC
Return-Path: <sean@sn3rd.com>
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 C77CF1200B3 for <spasm@ietfa.amsl.com>; Sat, 23 Mar 2019 15:19:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 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_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=sn3rd.com
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 ckYVLFeANe_X for <spasm@ietfa.amsl.com>; Sat, 23 Mar 2019 15:19:05 -0700 (PDT)
Received: from mail-yw1-xc2a.google.com (mail-yw1-xc2a.google.com [IPv6:2607:f8b0:4864:20::c2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 121C912AF80 for <spasm@ietf.org>; Sat, 23 Mar 2019 15:19:05 -0700 (PDT)
Received: by mail-yw1-xc2a.google.com with SMTP id e76so4438637ywa.9 for <spasm@ietf.org>; Sat, 23 Mar 2019 15:19:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=from:content-transfer-encoding:mime-version:subject:message-id:date :to; bh=Q/q1c9aFyq/Oq4nbLjjx0TYrdQyVSg+3ueJdSZVHeh8=; b=Q2ziWSV0NUSFBX/NuNDforcWD43+XKVPCVxHsG2fj2OJJSnZABOKEle//8QrnZB6QS KAUfGylggeU83AurgKus9+tf/CJlcQalrYSP91R/odJO91RxHRTWSbDyvIP0tDqchDg3 Clr1uDtdhdztI9k/EocnV/DVcHZ3ZeU7w/saM=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:message-id:date:to; bh=Q/q1c9aFyq/Oq4nbLjjx0TYrdQyVSg+3ueJdSZVHeh8=; b=YeHb/9Xkh/xJt6KvW2qDCbJshmS40liO+Ks5vDv65Tg4KUvv8P9T2dq4pVIy23aU+x 9M7EWviDZPg7H0ctaK5PpPsJPcylxlT41vcCWJlut4IuSuMvbr9eYPyvghwWDNYRrfpd jaagjhS2xOe6DwLMp8JBIBnqp7IRwVt7xFXgCokB8qvZ6uMIW+HkIShGNZ2ImvEymmsf 3ljPB7dCB6QeJeqp9yngXgfp5Gs0N7JpSoMyXr0pQiGdF4S09vRNKH5J9VKvPK48B2/5 kOgJxKocwieoLS37ZJ28G0lV2/6QPaAeRr1PLB0y048t7QUUzh6yq+piqW3FqmJ5aR/D 41Zg==
X-Gm-Message-State: APjAAAVwItoIxWQi8R6aqQTk+xejqR9qyW+MFodM6NcXgNmLxSqvlOR7 4iDqee1/LWGKA+cv7oeFC4cK2GI7yhVi0w==
X-Google-Smtp-Source: APXvYqz/HFGsFX2BAgibvjol4XdhGwZJq8T9ESLRLYSz/2aDecCy6YOv+G2dQe7VmYVnOfjXq1dV8Q==
X-Received: by 2002:a81:4a8a:: with SMTP id x132mr14481761ywa.408.1553379544199; Sat, 23 Mar 2019 15:19:04 -0700 (PDT)
Received: from [5.5.33.243] ([204.194.23.17]) by smtp.gmail.com with ESMTPSA id v204sm1600535ywc.54.2019.03.23.15.19.02 for <spasm@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 23 Mar 2019 15:19:03 -0700 (PDT)
From: Sean Turner <sean@sn3rd.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Message-Id: <74609304-E99C-419F-AE9A-00CFDD825927@sn3rd.com>
Date: Sat, 23 Mar 2019 23:19:00 +0100
To: "spasm@ietf.org" <spasm@ietf.org>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/b38SFOeko1OT2uN4n52YxAy2B0Y>
Subject: [lamps] RFC 5480 clarification for KeyUsages: keyEncipherment and dataEncipherment
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: Sat, 23 Mar 2019 22:19:07 -0000
Hi! RFC 5480 enumerates the KeyUsage values that are included for an EC key: https://tools.ietf.org/html/rfc5480#section-3 But, we neglected to mention keyEncipherment and dataEncipherment. Does that mean these values MAY be included, MUST NOT be included, or something else? And, is this worth spinning a short draft to clarify RFC 5480? spt
- [lamps] RFC 5480 clarification for KeyUsages: key… Sean Turner
- Re: [lamps] RFC 5480 clarification for KeyUsages:… Russ Housley
- Re: [lamps] RFC 5480 clarification for KeyUsages:… Jim Schaad