Re: [Ietf-dkim] The DKIM WG has placed draft-chuang-dkim-replay-problem in state "Call For Adoption By WG Issued"

Scott Kitterman <ietf-dkim@kitterman.com> Wed, 05 April 2023 21:05 UTC

Return-Path: <ietf-dkim@kitterman.com>
X-Original-To: ietf-dkim@ietfa.amsl.com
Delivered-To: ietf-dkim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB7C5C15171E for <ietf-dkim@ietfa.amsl.com>; Wed, 5 Apr 2023 14:05:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.398
X-Spam-Level:
X-Spam-Status: No, score=-4.398 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_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, 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=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=kitterman.com header.b="ija6vEMa"; dkim=pass (2048-bit key) header.d=kitterman.com header.b="Kiz0gocY"
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 Cja8aqkkTLLl for <ietf-dkim@ietfa.amsl.com>; Wed, 5 Apr 2023 14:05:50 -0700 (PDT)
Received: from interserver.kitterman.com (interserver.kitterman.com [64.20.48.66]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 A1CDFC14CE51 for <ietf-dkim@ietf.org>; Wed, 5 Apr 2023 14:05:50 -0700 (PDT)
Received: from interserver.kitterman.com (interserver.kitterman.com [64.20.48.66]) by interserver.kitterman.com (Postfix) with ESMTPS id 4963BF8027F for <ietf-dkim@ietf.org>; Wed, 5 Apr 2023 17:05:40 -0400 (EDT)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903e; t=1680728725; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=Xp3ls96ZCrAY5ZxhXgYNtxsx7/E/OOLGOouC9yowoFI=; b=ija6vEMaXz2sDk4vNGblziOiOq/QZuRoFi/y6YpOEBzeOExy8BqTgvBsyxytzRbMbxWOK y1chg+u6YrH+raMCw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1680728725; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=Xp3ls96ZCrAY5ZxhXgYNtxsx7/E/OOLGOouC9yowoFI=; b=Kiz0gocY/6yfKeYqIMNyIHlH4m/pcXhZ7RgKbqtBIeRx7/bQw0/cRzg96bKHqxe+iVrD2 djhMSDMOe514eNFPz/DGS5btQueTS9GA/KKjS1OcnwKzaYZaWYcLoZP1RJuUYWB1VQatLNZ j/iSJkaz8LCjT68SL9Vs19LfHC6i8DDchlDToogEokrHa+of8Rft8WTo+Z4JRNQwk3WJpD4 rDijGNxQNikZ9sayyexxDFtK+4IdsbizVW1OuJk7YytDYMbkVM3mmwxbiM+O01PeRWAThIs gLzyYfRHe935sySCVacxH4ogwrgq8HaPOA+/03so5Fw6yDaGjJ1baSKAEmdg==
Received: from localhost.localnet (static-72-81-252-22.bltmmd.fios.verizon.net [72.81.252.22]) by interserver.kitterman.com (Postfix) with ESMTP id 2F9C1F8016D for <ietf-dkim@ietf.org>; Wed, 5 Apr 2023 17:05:25 -0400 (EDT)
From: Scott Kitterman <ietf-dkim@kitterman.com>
To: ietf-dkim@ietf.org
Date: Wed, 05 Apr 2023 17:05:20 -0400
Message-ID: <2953466.gv1mf1uc93@localhost>
In-Reply-To: <9561dc6e-3429-6067-1d43-98f2f689476b@mtcc.com>
References: <168062163862.14121.12170185470226243470@ietfa.amsl.com> <9561dc6e-3429-6067-1d43-98f2f689476b@mtcc.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-dkim/GhhWooQ9GJyoF5DCw07iHpJ2Py0>
X-Mailman-Approved-At: Thu, 06 Apr 2023 02:46:25 -0700
Subject: Re: [Ietf-dkim] The DKIM WG has placed draft-chuang-dkim-replay-problem in state "Call For Adoption By WG Issued"
X-BeenThere: ietf-dkim@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF DKIM List <ietf-dkim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-dkim>, <mailto:ietf-dkim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-dkim/>
List-Post: <mailto:ietf-dkim@ietf.org>
List-Help: <mailto:ietf-dkim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-dkim>, <mailto:ietf-dkim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Apr 2023 21:05:54 -0000

On Tuesday, April 4, 2023 12:52:51 PM EDT Michael Thomas wrote:
> While a good start, this document is far too vague about what the
> current state of the problem actually is for those who of us who are not
> part of industry groups privy to more information.

To this specific point, I think any lack of crispness about the problem in the 
draft is reflective of uncertainty about how to describe it and we need to work 
on improving it.

As it happens, I was present at the industry group meeting in question (which 
is highly unusual for me, I was there for something unrelated) and as far as I 
can recall, everything that was discussed regarding the scope of the problem 
in that meeting has also been discussed here.  I don't think there's a 
reservoir of insider data that only some people know about.  I'm sure there 
are people in the working group who have access to more data as a result of 
their day job, but that's always true.

I think the fact that this work originated out of some private discussions is 
not material to where we go from here.

Scott K