Return-Path: <david@alkaline-solutions.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 0E1C4C15107F;
	Tue, 17 Sep 2024 16:22:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level: 
X-Spam-Status: No, score=-2.107 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,
	RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001,
	SPF_PASS=-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=alkaline-solutions.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 wKC7XwPp9Krr; Tue, 17 Sep 2024 16:22:34 -0700 (PDT)
Received: from mail.alkaline-solutions.com (caesium6.alkaline.solutions
 [157.230.133.164])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256)
	(No client certificate requested)
	by ietfa.amsl.com (Postfix) with ESMTPS id 60EFBC14F6A2;
	Tue, 17 Sep 2024 16:22:34 -0700 (PDT)
Content-Type: text/plain;
	charset=utf-8
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=alkaline-solutions.com;
	s=dkim; t=1726615353;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:cc:mime-version:mime-version:content-type:content-type:
	 content-transfer-encoding:content-transfer-encoding:
	 in-reply-to:in-reply-to:references:references;
	bh=4OOfgiTtJBeu/1Qiqh0L8nmLarbcU9nHR/OU8aZd/ZQ=;
	b=YcewAICxR+UWWQOc4bXiJNWjJWNyg05dwUM7wsELIbZhVOvK8rACx7JeeCTIA2W2eOIQA/
	9s++UukypL7fE8oimWd/OYvgrwH0VuJTpjGkA0xNKR6cnvistm2z6gMRG99fY++lsFMQON
	nBWaigC+HwT501Ktx50fGY+KT40ttY7GYFtL+R8ryX/HR3n1vXC+ySDvj/AioYq+D7XPKB
	GdY2To5fHSMoX2fCTcUxf/0+aiwovoxouN+4R+9rNwSqJ5zCLbfhI13pd6pHvQN8kO6FcO
	C50wnonPVRmfVKnakKhs8MELQzLwIcVYGCDMsALkTL3yIpLLi6NxMneDFyir3w==
Authentication-Results: mail.alkaline-solutions.com;
	auth=pass smtp.mailfrom=david@alkaline-solutions.com
Mime-Version: 1.0
From: David Waite <david@alkaline-solutions.com>
In-Reply-To: 
 <CA+mgmiOqZqu1fNjEK69zTbx3ndsum5jrLg06bzYTjtH+VQyWtA@mail.gmail.com>
Date: Tue, 17 Sep 2024 17:22:22 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <E9A8675F-DDDD-4AA0-A6CE-30A4693DCB4A@alkaline-solutions.com>
References: 
 <CA+mgmiOEbk9qjDwNTu198QVWAGqcuKNSPd2F-YtngcLZwjunZw@mail.gmail.com>
 <CA+mgmiOqZqu1fNjEK69zTbx3ndsum5jrLg06bzYTjtH+VQyWtA@mail.gmail.com>
To: Karen ODonoghue <kodonog@pobox.com>
X-Spamd-Bar: /
Message-ID-Hash: 6JYWS56QO5NCNUUAOJTQDTZLJCVS6LVM
X-Message-ID-Hash: 6JYWS56QO5NCNUUAOJTQDTZLJCVS6LVM
X-MailFrom: david@alkaline-solutions.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency;
 loop; banned-address; member-moderation; header-match-jose.ietf.org-0;
 nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size;
 news-moderation; no-subject; digests; suspicious-header
CC: JOSE WG <jose@ietf.org>, cose@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: =?utf-8?q?=5Bjose=5D_Re=3A_2nd_WGLC_for_draft-ietf-jose-fully-specified-algo?=
 =?utf-8?q?rithms_=28Fully_Specified_Algorithms=29?=
List-Id: Javascript Object Signing and Encryption <jose.ietf.org>
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/jose/csMyCqY4tmZeaVvXHvKE4AVa4ao>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jose>
List-Help: <mailto:jose-request@ietf.org?subject=help>
List-Owner: <mailto:jose-owner@ietf.org>
List-Post: <mailto:jose@ietf.org>
List-Subscribe: <mailto:jose-join@ietf.org>
List-Unsubscribe: <mailto:jose-leave@ietf.org>

I personally think this document is ready to proceed.

-DW

> On Sep 12, 2024, at 10:47=E2=80=AFAM, Karen ODonoghue =
<kodonog@pobox.com> wrote:
>=20
> JOSE and COSE working group members,
>=20
> This WGLC is currently scheduled to conclude on 13 September
> (tomorrow). I am not currently comfortable with the number and clarity
> of responses received. Please respond clearly indicating whether or
> not you think this document is ready to proceed (pending the comments
> raised in your response). To give you all a bit more time, I'm
> extending the WGLC one week to next Friday (20 September 2024).
>=20
> Please take a few minutes and review the updated draft!
>=20
> Thanks,
> Karen
>=20
> On Wed, Aug 21, 2024 at 11:10=E2=80=AFAM Karen ODonoghue =
<kodonog@pobox.com> wrote:
>>=20
>> JOSE working group members,
>>=20
>> This email initiates a second working group last call for the Fully
>> Specified Algorithms document:
>> =
https://datatracker.ietf.org/doc/draft-ietf-jose-fully-specified-algorithm=
s/
>>=20
>> The authors have updated the draft based on WGLC comments and
>> discussions at IETF 120, and the chairs have polled the working group
>> about the readiness for WGLC. Seeing no opposition, we've decided to
>> proceed with a second WGLC.
>>=20
>> Please review the document in detail and reply to this message
>> (keeping the subject line intact) with your opinion on the readiness
>> of this document for publication and any additional comments that you
>> have.
>>=20
>> This will be a three week WGLC. Please submit your responses by 13
>> September 2024.
>>=20
>> Thank you,
>> Karen (for the JOSE WG chairs)
>=20
> _______________________________________________
> jose mailing list -- jose@ietf.org
> To unsubscribe send an email to jose-leave@ietf.org

