Re: [dmarc-ietf] Two basic Issues to address to help complete DMARCbis

Alessandro Vesely <vesely@tana.it> Mon, 24 April 2023 11:22 UTC

Return-Path: <vesely@tana.it>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F0D31C15152B for <dmarc@ietfa.amsl.com>; Mon, 24 Apr 2023 04:22:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, NICE_REPLY_A=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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=tana.it header.b="YfyzrFRU"; dkim=pass (1152-bit key) header.d=tana.it header.b="B9k2YNHo"
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 AubAuERw5Y6B for <dmarc@ietfa.amsl.com>; Mon, 24 Apr 2023 04:22:15 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [94.198.96.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 87C02C14CE3F for <dmarc@ietf.org>; Mon, 24 Apr 2023 04:22:13 -0700 (PDT)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=tana.it; s=epsilon; t=1682335329; bh=rLzIzYnzYZ1R2l2D/5df9G+vE6VIkQUp2nzOa1vzjCE=; h=Author:Date:Subject:To:References:From:In-Reply-To; b=YfyzrFRU9ZzAo3bbbupSOEWwQz16RGHR/2i3xCd1VkWJ+uD8NKr48KoKVACwVza0E rRj3klTb1W3oB96CkZlAw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1682335329; bh=rLzIzYnzYZ1R2l2D/5df9G+vE6VIkQUp2nzOa1vzjCE=; h=Date:Subject:To:References:From:In-Reply-To; b=B9k2YNHoKZ8js6fVWJqZhfUs51OsAM89JiSSo06KKz6w7Pib/bdcBNOeyCRv7PUxz adnz/SCruLUTBuolnfgj/2ZRDz8DtepzdySm1CaWSVmuKY8jWaxkvPpCpyjSUmkaVm VKvsjko5dI3k/yFVn9LqmCC0pRZ9p8qZ9rZ4BmLt22Fe1JzleYQNWZbGzTT50
Original-Subject: Re: [dmarc-ietf] Two basic Issues to address to help complete DMARCbis
Author: Alessandro Vesely <vesely@tana.it>
Received: from [172.25.197.111] (pcale.tana [172.25.197.111]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k, TLS: TLS1.3, 128bits, ECDHE_RSA_AES_128_GCM_SHA256) by wmail.tana.it with ESMTPSA id 00000000005DC083.0000000064466661.00005157; Mon, 24 Apr 2023 13:22:09 +0200
Message-ID: <bc4f7f74-2753-fa0b-b866-a0b45968345a@tana.it>
Date: Mon, 24 Apr 2023 13:22:09 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.9.0
Content-Language: en-US, it-IT
To: dmarc@ietf.org
References: <0abf9711-ca1c-bfcf-afb2-15e16b9de149@tana.it> <20230420153727.DB568C106CE9@ary.qy> <CAJ4XoYeyoOYeXW1QN+yeMbxt4SF7Kn2Xi=FP7VmX4MhKiDi9hQ@mail.gmail.com> <C3D9E708-EDC7-43BC-AE5E-DF4FFAECCC2B@kitterman.com> <7e2ae4c0-6ebf-4539-55b9-e5d85765a024@tana.it> <185759A8-10CD-40F8-89C8-FE774B077F52@kitterman.com> <a31a3a91-1fe1-40b0-ae4c-0e76520e722c@tana.it> <644568C6.4000407@isdg.net>
Authentication-Results: tana.it; auth=pass (details omitted)
From: Alessandro Vesely <vesely@tana.it>
In-Reply-To: <644568C6.4000407@isdg.net>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/WcSXf4q4XD7dHvWb1UayGuuXkxE>
Subject: Re: [dmarc-ietf] Two basic Issues to address to help complete DMARCbis
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmarc>, <mailto:dmarc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Apr 2023 11:22:23 -0000

On Sun 23/Apr/2023 19:20:06 +0200 Hector Santos wrote:
> On 4/23/2023 6:10 AM, Alessandro Vesely wrote:
>>
>> Meanwhile, digressions about ATPS and similar schemes can help casting some 
>> light on future evolution.  From: rewriting cannot be the final solution; it 
>> is a temporary hack.  Digressions don't slow down the publication, as 
>> discussions about actual text quickly prevail.  They are just a mean to help 
>> convergence toward a common vision of the future.
>
> With each year, that "temporary hack" becomes the new normal and it will be 
> harder to clean up. It is not the right way and I don't  its too late to 
> reverse.  However, it has been 17 years and DMARCbis is not finished without 
> some clean up in this area.
>
> First, Section 4.4.3 should have text on using extended tag methods to provide 
> 3rd party authorization methods.  Just add the RFC 6541 abstract or version of it:


Proposing to add text to DMARCbis about 3rd party auth is not a digression.  We 
cannot solve the problem before publishing DMARCbis.  The text to add to 
DMARCbis can mention that From: rewriting will fade out, but cannot say how. 
(This is not a rule, just a scheduling requirement.)


Best
Ale
--