Re: [jose] JWS/CT - Dropping the ISE track?
Carsten Bormann <cabo@tzi.org> Sun, 12 December 2021 13:31 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 A70513A0B1E for <jose@ietfa.amsl.com>; Sun, 12 Dec 2021 05:31:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, 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 4sLWxbh2k19c for <jose@ietfa.amsl.com>; Sun, 12 Dec 2021 05:31:15 -0800 (PST)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [134.102.50.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 60E743A0AE4 for <jose@ietf.org>; Sun, 12 Dec 2021 05:31:14 -0800 (PST)
Received: from [192.168.217.118] (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 4JBlsB69YCzDCcV; Sun, 12 Dec 2021 14:31:10 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <d366eee6-e7dd-51e6-5862-0721ef1d70cc@gmail.com>
Date: Sun, 12 Dec 2021 14:31:10 +0100
Cc: "jose@ietf.org" <jose@ietf.org>
X-Mao-Original-Outgoing-Id: 661008670.449373-7b6d4e7b8e25be187389ca7ae03af45d
Content-Transfer-Encoding: quoted-printable
Message-Id: <F8F80AF8-14FA-4AAB-A360-D69D94803273@tzi.org>
References: <d366eee6-e7dd-51e6-5862-0721ef1d70cc@gmail.com>
To: Anders Rundgren <anders.rundgren.net@gmail.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/jose/lYckHPFuw26TTGFHll0efCyv4a0>
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: Sun, 12 Dec 2021 13:31:20 -0000
On 2021-12-12, at 08:41, Anders Rundgren <anders.rundgren.net@gmail.com> wrote: > > *] This informational specification has been produced outside the IETF, > is not an IETF standard, and does not have IETF consensus. This is a true statement, so I don’t know how you could be opposed. What is still not true is the “clear text” in the title. I thought we had discussed this; I’m certainly not going to engage in any repeat discussion. Keeping this term in the title smacks like intent to deceive. Grüße, Carsten
- [jose] JWS/CT - Dropping the ISE track? Anders Rundgren
- Re: [jose] JWS/CT - Dropping the ISE track? Carsten Bormann
- Re: [jose] JWS/CT - Dropping the ISE track? Anders Rundgren
- Re: [jose] JWS/CT - Dropping the ISE track? Carsten Bormann