Re: [Ietf-dkim] Adding an aim= tag to DKIM Signature Tag Specifications

Scott Kitterman <ietf-dkim@kitterman.com> Tue, 12 May 2020 13:26 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 B9F0C3A0932 for <ietf-dkim@ietfa.amsl.com>; Tue, 12 May 2020 06:26:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, SPF_HELO_FAIL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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=N5/th5mY; dkim=pass (2048-bit key) header.d=kitterman.com header.b=PwNNtp2N
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 CLgMI_EUzLHr for <ietf-dkim@ietfa.amsl.com>; Tue, 12 May 2020 06:26:32 -0700 (PDT)
Received: from interserver.kitterman.com (interserver.kitterman.com [IPv6:2604:a00:6:1039:225:90ff:feaa:b169]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 32FB73A0936 for <ietf-dkim@ietf.org>; Tue, 12 May 2020 06:26:32 -0700 (PDT)
Received: from interserver.kitterman.com (interserver.kitterman.com [64.20.48.66]) by interserver.kitterman.com (Postfix) with ESMTPS id 3E800F80276 for <ietf-dkim@ietf.org>; Tue, 12 May 2020 09:26:31 -0400 (EDT)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903e; t=1589289991; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=mIWNqj5POStByXSTCahViFWsBabjmvnSZb07OFmdW/4=; b=N5/th5mY6da5MKyKy86pHHHU9JVimLoXC6vwTFMJGe9Kg6oGAK0JiVHiWFyqf0CGSfUNm QExXD8M7FRcK3bvDg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1589289991; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=mIWNqj5POStByXSTCahViFWsBabjmvnSZb07OFmdW/4=; b=PwNNtp2N0Frl7S7ckKK5m2MT9G+LwyaW9b4K2WDxIc5K7STwP5W0z+otxLMrtXdbE5XXb gqigHXHV6EKCjLwNKSpPop11ZtUmeb8I+vws0HaXuYMnfocLX68zAX1WzWjhJLGT0KLWSh9 LEVrqs2rBMavpg/pZp4QupQS8M29Ub6ROalWL0grSiQ8vH/Gu25E01m/VAsCXrSis0X6LZu p8W0qWiqZxWjGb2WSvD/HSSUgaI3lQe9sPktJ4rQILYvkQ6Z0XTUt7HdYgayJHb7ZTFcHTP L17gqhkg2Mxvq+JNIsVW0O6Jr6eMNmEmrquSZyt+fOjoy51ivO/0/zDz8d9g==
Received: from sk-desktop.localnet (static-72-81-252-22.bltmmd.fios.verizon.net [72.81.252.22]) by interserver.kitterman.com (Postfix) with ESMTP id 121DDF801F8 for <ietf-dkim@ietf.org>; Tue, 12 May 2020 09:26:31 -0400 (EDT)
From: Scott Kitterman <ietf-dkim@kitterman.com>
To: ietf-dkim@ietf.org
Date: Tue, 12 May 2020 09:26:30 -0400
Message-ID: <2917738.G2pOncIj4s@sk-desktop>
In-Reply-To: <0cb1fa41-b51b-ad5c-80a1-4794983def97@wordtothewise.com>
References: <80533fb3-75a2-1d60-801d-c54d735d4094@tana.it> <551162f8-6c95-071c-3b2e-6a265b1c9783@tana.it> <0cb1fa41-b51b-ad5c-80a1-4794983def97@wordtothewise.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-dkim/rcGGeQW5sPlUq2McxDMqkFxwIx4>
Subject: Re: [Ietf-dkim] Adding an aim= tag to DKIM Signature Tag Specifications
X-BeenThere: ietf-dkim@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 12 May 2020 13:26:34 -0000

On Tuesday, May 12, 2020 5:31:30 AM EDT Steve Atkins wrote:
> On 12/05/2020 09:20, Alessandro Vesely wrote:
> > On Tue 12/May/2020 00:08:15 +0200 Dave Crocker wrote:
> >> On 5/11/2020 1:33 PM, Jim Fenton wrote:
> >>> There might also be the situation where a domain wants to delegate a key
> >> 
> >> Hence my suggestion that figuring out such details is where discussion
> >> could get interesting, if only because people will raise all sorts of
> >> combinatorial theories, independent of demonstrated need, and this is a
> >> space with lots of combinatorials...
> > 
> > Besides delegated keys, some other obvious classes I'd propose —without
> > venturing to forge English keywords— are as follows:
> > 
> > * 1st class personal messages (with or without From: restrictions),
> > 
> > * mailing lists (with or without From: rewrite),
> > 
> > * bulk messages (including transactional confirmations, complaints, ...),
> > 
> > * forwarded mail (after severe/loose antispam filtering).
> > 
> > Perhaps, the keywords should be dash-separated jumbles of terms chosen
> > from a predefined grab bag, to allow for combinations.
> 
> Some prior work in this space is TEOS.
> 
> https://www.researchgate.net/publication/301324998_Trusted_Email_Open_Standa
> rd_A_Comprehensive_Policy_and_Technology_Proposal_for_Email_Reform

I looked through it.  It is so 2003 FUSSP.

Scott K