Re: [jose] JWS/CT - Dropping the ISE track?

Carsten Bormann <cabo@tzi.org> Mon, 13 December 2021 05:37 UTC

Return-Path: <cabo@tzi.org>
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 C51273A0E00 for <jose@ietfa.amsl.com>; Sun, 12 Dec 2021 21:37:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 NqRgtwOkpXoH for <jose@ietfa.amsl.com>; Sun, 12 Dec 2021 21:37:04 -0800 (PST)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 05F313A0DF5 for <jose@ietf.org>; Sun, 12 Dec 2021 21:37:03 -0800 (PST)
Received: from smtpclient.apple (p5089a436.dip0.t-ipconnect.de [80.137.164.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4JC9HY40ZczDChN; Mon, 13 Dec 2021 06:36:57 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <bf7fba66-cb51-0290-bdb7-617c24912e45@gmail.com>
Date: Mon, 13 Dec 2021 06:36:56 +0100
Cc: "jose@ietf.org" <jose@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <D013365A-B083-4AD7-BD96-A303FCC8600D@tzi.org>
References: <d366eee6-e7dd-51e6-5862-0721ef1d70cc@gmail.com> <F8F80AF8-14FA-4AAB-A360-D69D94803273@tzi.org> <bf7fba66-cb51-0290-bdb7-617c24912e45@gmail.com>
To: Anders Rundgren <anders.rundgren.net@gmail.com>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/jose/lv6UrXa6LVXmybYTtmCjT4eacrk>
Subject: Re: [jose] JWS/CT - Dropping the ISE track?
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 13 Dec 2021 05:37:08 -0000

On 13. Dec 2021, at 05:47, Anders Rundgren <anders.rundgren.net@gmail.com> wrote:
> 
> As I wrote the issue here is how to deal with ISE documents, now, and in the future.  JWS/CT is a recent example highlighting a problem that the IETF may need to address.

The Independent Stream works great for what it is supposed to do.
The fact that you do not seem to like the conditions for publishing there doesn’t mean there is an “issue” that invalidates the whole stream.

Please note that the Independent Stream is, as the name kind of reveals, independent of the IETF.
The JOSE mailing list of the IETF is certainly not the place to bring up any desire to change it.

Grüße, Carsten