IETF Logo Mail Archive

Re: [jose] I-D Action: draft-ietf-jose-fully-specified-algorithms-00.txt

Brian Campbell <bcampbell@pingidentity.com> Wed, 31 January 2024 16:46 UTC

Return-Path: <bcampbell@pingidentity.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0761DC14F6FF for <jose@ietfa.amsl.com>; Wed, 31 Jan 2024 08:46:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=pingidentity.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U6ZECWQBL7iZ for <jose@ietfa.amsl.com>; Wed, 31 Jan 2024 08:46:09 -0800 (PST)
Received: from mail-io1-xd2c.google.com (mail-io1-xd2c.google.com [IPv6:2607:f8b0:4864:20::d2c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 76E60C14F681 for <jose@ietf.org>; Wed, 31 Jan 2024 08:46:09 -0800 (PST)
Received: by mail-io1-xd2c.google.com with SMTP id ca18e2360f4ac-7c02529b984so23590039f.1 for <jose@ietf.org>; Wed, 31 Jan 2024 08:46:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pingidentity.com; s=google; t=1706719568; x=1707324368; darn=ietf.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=HqO6nayC2sfSjpkOIUVpNGq6MPtQNoU4VAxXHOKzKwo=; b=S8Zl97xcJdROhmDMXXRcpJBPLUinzOr6rHtXgM/eOBNBImOyMqbHwHhgDN59lcWilY ESOdkswblYxObGqzr5nFHIB2MtSZgBhIKUT4n209FShqf5s+OAOy/EHkQ029rQHSUvtT 4/608iGXzQtsyvwTMAwVX8/LF5jy56Qb3hSvVObsIuPxAh+9wcRFYKhqFCjiRBr4+Tcg rV5DfzieHqRpIU0RAkslDeqjnbENxSdE8Bi4oP3OhKJom9iPYd3Do0Q8ZlGlN8iEJkXS Th61Fikg0bG+KK5hWO3ij9xt1SpyejjLmbeVtKO/xV09KXDm6Gr0l5R1iKuogA73RCqe YyZQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1706719568; x=1707324368; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=HqO6nayC2sfSjpkOIUVpNGq6MPtQNoU4VAxXHOKzKwo=; b=arSi0BaVCrynS7cn9lo2PALMMparVCv+wrHnHgGT9SYkQpVJwckOeIhGcTn0PNeduq aFwUsTO8NmhYd16EYAdY87PPo0KwJr6Clux7WO0lJlhD8Q/3thB6dIMM/nrsWZV97Uum htr5rwZEx/4ymcLe4xNVHdE78DxcQjYbV18pgIf2DZiM4DMXwi72rHCx0zZeW3T0m2Vs sRkMAgdmT3+6bW088vpy/YPARJU7N3WC27SB1fcv/xAAROqJSb+zuYGsDcd1I5aAFp35 lw0jTqYuqy6lYlm4zFQElDNQ8APQzItdpqN/kGahkOMtb4beVp2jEJGreeGFhuxJAO66 X8sw==
X-Gm-Message-State: AOJu0YwaIkKYhX24XLXK2oyuKEz7WJWkmDdbW9xPiDW24SPszYt6bvAz OiJSCULgVK4+dpf6DQqq4eq5XSKGae0j2Yh2Bob5y8dsZwYgvD7U1SfE6u6jdbxgKJRUd6hZvsK inmaQ/caVdcuLt4K/HN+mRBu2hsKD2CWveuOObTo37RypUHxGwuIPEhrBTHbxRdr3+cYpplUiwV 8vcDaj97yHx/j4tuBp9TDhwg==
X-Google-Smtp-Source: AGHT+IGC4x1bYUEIBjto9sYwftte9/jDhixX2/4nvt34ZdJ7zFz1q6CQbJEj/dCUSQUyPWsx7K98dMBGVpPKavv8OYs=
X-Received: by 2002:a92:cd49:0:b0:363:86fd:9673 with SMTP id v9-20020a92cd49000000b0036386fd9673mr2513132ilq.10.1706719568104; Wed, 31 Jan 2024 08:46:08 -0800 (PST)
MIME-Version: 1.0
References: <170623763383.46235.14533165444845043784@ietfa.amsl.com>
In-Reply-To: <170623763383.46235.14533165444845043784@ietfa.amsl.com>
From: Brian Campbell <bcampbell@pingidentity.com>
Date: Wed, 31 Jan 2024 09:45:37 -0700
Message-ID: <CA+k3eCQ=qYE3AG1PBXVM6-no+73SP6OvWOGAbG1cXWusz8MQCA@mail.gmail.com>
To: jose@ietf.org
Content-Type: multipart/alternative; boundary="00000000000096aa580610409df1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/jose/EaHheqlNmufaGiIsyvoMHqMI98s>
Subject: Re: [jose] I-D Action: draft-ietf-jose-fully-specified-algorithms-00.txt
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Javascript Object Signing and Encryption <jose.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jose>, <mailto:jose-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jose/>
List-Post: <mailto:jose@ietf.org>
List-Help: <mailto:jose-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jose>, <mailto:jose-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Jan 2024 16:46:13 -0000

Logistics nit - would it be possible for the chairs or authors to mark this
one as replacing draft-jones-jose-fully-specified-algorithms? The linkage
doesn't currently show up in datatracker.

https://datatracker.ietf.org/doc/draft-ietf-jose-fully-specified-algorithms/

https://datatracker.ietf.org/doc/draft-jones-jose-fully-specified-algorithms/



On Thu, Jan 25, 2024 at 7:54 PM <internet-drafts@ietf.org> wrote:

> Internet-Draft draft-ietf-jose-fully-specified-algorithms-00.txt is now
> available. It is a work item of the Javascript Object Signing and
> Encryption
> (JOSE) WG of the IETF.
>
>    Title:   Fully-Specified Algorithms for JOSE and COSE
>    Authors: Michael B. Jones
>             Orie Steele
>    Name:    draft-ietf-jose-fully-specified-algorithms-00.txt
>    Pages:   11
>    Dates:   2024-01-25
>
> Abstract:
>
>    This specification refers to cryptographic algorithm identifiers that
>    fully specify the cryptographic operations to be performed, including
>    any curve, key derivation function (KDF), hash functions, etc., as
>    being "fully specified".  Whereas, it refers to cryptographic
>    algorithm identifiers that require additional information beyond the
>    algorithm identifier to determine the cryptographic operations to be
>    performed as being "polymorphic".  This specification creates fully-
>    specified algorithm identifiers for all registered JOSE and COSE
>    polymorphic algorithm identifiers, enabling applications to use only
>    fully-specified algorithm identifiers.
>
> The IETF datatracker status page for this Internet-Draft is:
>
> https://datatracker.ietf.org/doc/draft-ietf-jose-fully-specified-algorithms/
>
> There is also an HTMLized version available at:
>
> https://datatracker.ietf.org/doc/html/draft-ietf-jose-fully-specified-algorithms-00
>
> Internet-Drafts are also available by rsync at:
> rsync.ietf.org::internet-drafts
>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose
>

-- 
_CONFIDENTIALITY NOTICE: This email may contain confidential and privileged 
material for the sole use of the intended recipient(s). Any review, use, 
distribution or disclosure by others is strictly prohibited.  If you have 
received this communication in error, please notify the sender immediately 
by e-mail and delete the message and any file attachments from your 
computer. Thank you._

v2.23.0 | Report a Bug | By Email