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

Damon <deepvoice@gmail.com> Mon, 11 May 2020 19:52 UTC

Return-Path: <deepvoice@gmail.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 0954D3A0CB1 for <ietf-dkim@ietfa.amsl.com>; Mon, 11 May 2020 12:52:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 LOjwQm0mpoD5 for <ietf-dkim@ietfa.amsl.com>; Mon, 11 May 2020 12:52:40 -0700 (PDT)
Received: from mail-qk1-x735.google.com (mail-qk1-x735.google.com [IPv6:2607:f8b0:4864:20::735]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D199C3A0CA8 for <ietf-dkim@ietf.org>; Mon, 11 May 2020 12:52:39 -0700 (PDT)
Received: by mail-qk1-x735.google.com with SMTP id n14so11157802qke.8 for <ietf-dkim@ietf.org>; Mon, 11 May 2020 12:52:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=oF60SP6z6F/1gVmOSRxtFiZC8RIXWn5OYVvaHXK+9g8=; b=I0HPUwBKd/fvMheWeXgi2mWSusnPf7ziRSR7G3cgZ33TGS88EMGG3o1weaORLaWKVV 8v1ajnQJvj8HLFzReCCOztXl3hjX2zVnshpkWlpdOsRQQ+RX+RcE+riaPzXj75Co68g7 8JMfd7Ft8g4gr09n4bQJ27grb2oFuNRdcrrd1ISnUZQ4dY58VOjrE9UpyJxqm45hS2Rc qkLMCQvQfK3sb6f0sIT+vF9vuY7xEDHxARXAlJxxdsm5er7A9ZkmJb/+U4ssrubnAbs7 2ny2vBUjVZ5dGRLdIy1QbnN6Z8go6cJaLvAcSanmgAgwwDsfUaQgy3KmYWWXfB/SDKJ/ cTmQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=oF60SP6z6F/1gVmOSRxtFiZC8RIXWn5OYVvaHXK+9g8=; b=IUtfBbEKbrZ9uGtBNFeVWPShpgrs1TBEr1rYiqqJ3G3C5dEXJWzfwWJysrXVMHnYWx /g+u/ZUppj5kNsH3eivB0Cf5SOrEs7/VuwVc5UNc0QpoEFy//0/2cNWWELhOAQKkSFRb hPTzzpDz6F0jN5aNtAV85ZqdFKN4wxkGk1kf0jqUk9uGW794OzTcqM2RgaOk3g/6NElt NjQpKMDsDj3LcW+9/VPOmYyllhED5nLQ85jWQUoZ0Swp88IdBnkJxnD5EY4vNkBE1Qki GfhHCOTbFysgdhKLNfTTou8zTN67m8mdpSKti/mpVrnK/kr8erRW+Od4tKWDTR+XegOj L3Ig==
X-Gm-Message-State: AGi0Pub4wiUxBbCJlUtiKdeNYGUNyUjUy8XjW+0gBKjRw6G73zYWB75S mEuCFsMb9zcMchW2MkEQfDGqum/1JRsalcUg4BE5Gw==
X-Google-Smtp-Source: APiQypIAwlF34RQEF7goK07WToxIkTCJ4QQCH63MePvHTgfEHJhNEA+nrgOFphobM9WIhZWTloBi0AwmhRNSMxf/P38=
X-Received: by 2002:ae9:e858:: with SMTP id a85mr17211316qkg.478.1589226758765; Mon, 11 May 2020 12:52:38 -0700 (PDT)
MIME-Version: 1.0
References: <80533fb3-75a2-1d60-801d-c54d735d4094@tana.it> <7ac84ebf-e30b-6288-81c2-4a6631471d74@dcrocker.net> <CAL0qLwYYzW2J7JZMw8S8WCny8Nyh5W1X4X2uv3ZDiKe3adusuA@mail.gmail.com>
In-Reply-To: <CAL0qLwYYzW2J7JZMw8S8WCny8Nyh5W1X4X2uv3ZDiKe3adusuA@mail.gmail.com>
From: Damon <deepvoice@gmail.com>
Date: Mon, 11 May 2020 15:52:28 -0400
Message-ID: <CAK-TNkdoarq8nZPeDSXDTVyeE9hWn8gApVz7dhi8NsV0bi16yA@mail.gmail.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Cc: Alessandro Vesely <vesely@tana.it>, Dave Crocker <dcrocker@bbiw.net>, ietf-dkim@ietf.org
Content-Type: multipart/alternative; boundary="0000000000006c859205a564b0ca"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-dkim/LP_kf1cGZVV5x6kpeqtOHB2Zr7M>
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: Mon, 11 May 2020 19:52:45 -0000

Trying to follow this thread...

I am unclear as to what problem this (aim=) is trying to solve... or is
this only to add a layer of (potentially ignored) definitions?

Regards,
Damon



On Mon, May 11, 2020 at 2:23 PM Murray S. Kucherawy <superuser@gmail.com>
wrote:

> On Mon, May 11, 2020 at 10:30 AM Dave Crocker <dhc@dcrocker.net> wrote:
>
>> On 5/11/2020 10:21 AM, Alessandro Vesely wrote:
>> > The question is, what responsibility is being claimed?
>> .....
>> > Tagging keys with aim= would allow senders to choose an appropriate
>> selector
>> > under different circumstances.
>>
>> If signers want to have a standardized means of indicating the
>> fine-grained semantics behind their signature, they can do that without
>> modifying DKIM.
>>
>> Rather, define and use a header field that specifies DKIM signing
>> policy.  Cover it with the DKIM signature, of course.
>>
>> The only interesting part of this task is deciding on a standard set of
>> policy labels.
>>
>> Oh, and then figuring out why and how they are useful to provide...
>>
>
> Indeed; why would I believe what any given domain claims in this tag?
>
> If the response to that is that you will trust only what certain domains
> say here, then you probably already know the equivalent of what's in the
> tag anyway.
>
> -MSK
> _______________________________________________
> Ietf-dkim mailing list
> Ietf-dkim@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-dkim
>