IETF Logo Mail Archive

[Curdle] Fwd: New Version Notification for draft-mtis-lamps-8410-ku-clarifications-00.txt

Sean Turner <sean@sn3rd.com> Wed, 12 January 2022 19:59 UTC

Return-Path: <sean@sn3rd.com>
X-Original-To: curdle@ietfa.amsl.com
Delivered-To: curdle@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11B4D3A1ADF for <curdle@ietfa.amsl.com>; Wed, 12 Jan 2022 11:59:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.098
X-Spam-Level:
X-Spam-Status: No, score=-7.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 ZT4HYAw9JikX for <curdle@ietfa.amsl.com>; Wed, 12 Jan 2022 11:59:19 -0800 (PST)
Received: from mail-qv1-xf2b.google.com (mail-qv1-xf2b.google.com [IPv6:2607:f8b0:4864:20::f2b]) (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 70C8F3A1AD9 for <curdle@ietf.org>; Wed, 12 Jan 2022 11:59:19 -0800 (PST)
Received: by mail-qv1-xf2b.google.com with SMTP id kl12so4159916qvb.5 for <curdle@ietf.org>; Wed, 12 Jan 2022 11:59:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=from:mime-version:subject:date:references:cc:to:message-id; bh=25Hf958AQUCGHLXTtRFv0+xU+Lxj1LO251BNgm+d24I=; b=V+KYeye2Q0ZiGH76pmwOcYG9Nsd/CPAcZ6pmfwl80/vdbBTUGuBW9S4gOgLHOvN4eQ DviPrmpudF0Qjc5Er0AkTZPp+0498Ey9ZYWHJvwRgF2Het4gC0PTQCDSj97vDeZBqI/J 6gtNvwoiTkYiB+B3J6PE4R+pdkcjjWCLTgfpU=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:mime-version:subject:date:references:cc:to :message-id; bh=25Hf958AQUCGHLXTtRFv0+xU+Lxj1LO251BNgm+d24I=; b=r0RMeWbrHdhhZbQbva/IzoSCOBRpBZrA/Roj6iQ+bdTWRkHgb2hkR1EHR3kjURU9dM OIzZkHMPyLCWTExCUGCq1SWV8H0Bv5ut0PGTIWADm6mWO21Jb4DrbpTuyXrksz7r1ZkK aWcoBI/9N4/0BoS61R2R6PXEdUYUMej7yD1pZfPXH2/ywszFOJt4PZNxjLN3ucVftDv5 EHLZILpalJp6jxz9z+RePNvjgGRdS4eKt5chKeOJQ6gS2OGSCiLj2SsryrQXWF/qMWI6 lI1Ml2f2g7kQeS7ybU95FLYaOjuqXspn4NPrY/Z2s084md1+DyrqMNJaXpOQLYZ+dYBW yvQw==
X-Gm-Message-State: AOAM533x1cPRg60OKg6LWgk4kdvH04RTzzJMI5e/0lXYjTLyQADjNgQ4 Cdk/WC1hJrZFYik0lc9OR12SWFXRGCtLnA==
X-Google-Smtp-Source: ABdhPJyzPrh8l8TroYtNqvVsN8LbnKa/sw4fORTAI60h8xCsnOH3ZxkLJqokFAaO1qeZNA6CIZ4F/g==
X-Received: by 2002:a05:6214:1cc3:: with SMTP id g3mr1336035qvd.53.1642017557342; Wed, 12 Jan 2022 11:59:17 -0800 (PST)
Received: from smtpclient.apple (pool-71-178-177-131.washdc.fios.verizon.net. [71.178.177.131]) by smtp.gmail.com with ESMTPSA id h1sm474789qta.54.2022.01.12.11.59.16 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 12 Jan 2022 11:59:16 -0800 (PST)
From: Sean Turner <sean@sn3rd.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_1BC6E1A3-49B7-4966-AB66-E72CAF8B5C7D"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
Date: Wed, 12 Jan 2022 14:59:16 -0500
References: <164196813912.10423.12752056700321106986@ietfa.amsl.com>
Cc: curdle@ietf.org
To: LAMPS WG <spasm@ietf.org>
Message-Id: <1C866AE7-94AF-4FA1-95C1-76D2F64BED7B@sn3rd.com>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/curdle/pIYHEBnT4zur6MNfOsD5j5wDHY8>
Subject: [Curdle] Fwd: New Version Notification for draft-mtis-lamps-8410-ku-clarifications-00.txt
X-BeenThere: curdle@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of potential new security area wg." <curdle.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/curdle>, <mailto:curdle-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/curdle/>
List-Post: <mailto:curdle@ietf.org>
List-Help: <mailto:curdle-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/curdle>, <mailto:curdle-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jan 2022 19:59:25 -0000

LAMPS,

Hi! While Ito-san and I were working on RFC 8813 (nee draft-ietf-lamps-5480-ku-clarifications, nee draft-turner-5480-ku-clarifications), Daniel McCarney asked whether we should write the same kind of clarifications for RFC 8410 [1] (algorithm identifiers for Ed25519, Ed448, X25519, and X448 in certificates). I had a look and exchanged some emails with Simon and it seems like it would be good to make sure there were the same clarifications for the x25519 and x448 identifiers that we had for the other identifiers … so we produced this I-D.

Note: I am forwarding this I-D to LAMPS for consideration and not curdle knowing that curdle is planning to close. I also alerted the chairs and am cc’ing curdle so nobody is surprised.  As this is basically, a do-over of RFC 8410 I am hoping that adopting/progressing this I-D will be non-controversial.

Cheers,
spt

[1] https://datatracker.ietf.org/doc/rfc8410/

> Begin forwarded message:
> 
> From: internet-drafts@ietf.org
> Subject: New Version Notification for draft-mtis-lamps-8410-ku-clarifications-00.txt
> Date: January 12, 2022 at 01:15:39 EST
> To: "Daniel McCarney" <daniel@binaryparadox.net>, "Sean Turner" <sean@sn3rd.com>, "Simon Josefsson" <simon@josefsson.org>, "Tadahiko Ito" <tadahiko.ito.public@gmail.com>
> 
> 
> A new version of I-D, draft-mtis-lamps-8410-ku-clarifications-00.txt
> has been successfully submitted by Sean Turner and posted to the
> IETF repository.
> 
> Name:		draft-mtis-lamps-8410-ku-clarifications
> Revision:	00
> Title:		Clarifications for Ed25519, Ed448, X25519, and X448 Algorithm Identifiers
> Document date:	2022-01-12
> Group:		Individual Submission
> Pages:		6
> URL:            https://www.ietf.org/archive/id/draft-mtis-lamps-8410-ku-clarifications-00.txt
> Status:         https://datatracker.ietf.org/doc/draft-mtis-lamps-8410-ku-clarifications/
> Html:           https://www.ietf.org/archive/id/draft-mtis-lamps-8410-ku-clarifications-00.html
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-mtis-lamps-8410-ku-clarifications
> 
> 
> Abstract:
>   This document updates RFC 8410 to clarify existing and specify
>   missing semantics for key usage bits when used in certificates that
>   support the Ed25519, Ed448, X25519, and X448 Elliptic Curve
>   Cryptography algorithms.
> 
> 
> 
> 
> The IETF Secretariat
> 
>

v2.23.0 | Report a Bug | By Email