Re: [dmarc-ietf] Call for Adoption: DMARC Use of the RFC5322.Sender Header Field

Alessandro Vesely <vesely@tana.it> Sat, 15 August 2020 07:59 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 4A5DB3A0913 for <dmarc@ietfa.amsl.com>; Sat, 15 Aug 2020 00:59:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.047
X-Spam-Level:
X-Spam-Status: No, score=-3.047 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.949, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1152-bit key) header.d=tana.it
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 NBYfvOij-Dkk for <dmarc@ietfa.amsl.com>; Sat, 15 Aug 2020 00:59:13 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B5193A0912 for <dmarc@ietf.org>; Sat, 15 Aug 2020 00:59:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1597478351; bh=tAD2soYNCsONGtasc27+XTVsFmTJq9VZ8B93JQgUwUc=; l=854; h=To:References:From:Date:In-Reply-To; b=B6BhbSfnWSm6sTx+uqPiEGu7g9JebDUwEIpQwRPY3znCu/YQyWbWdd6j9mPQPXOkc U6zmHQJ64uwSJ4lZNdqKyKitQOmQLDFse0QLWdfALPBaR06qofhykeM5bYGPHV3kbc ugfbAr0O6mTRwYUYTG8W8vbaPrXaeG8h7Cu3In/5EigoqBnsffxg4m7y5Psyo
Authentication-Results: tana.it; auth=pass (details omitted)
Received: from [192.168.1.102] ([5.170.69.62]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k, TLS: TLS1.3, 128bits, ECDHE_RSA_AES_128_GCM_SHA256) by wmail.tana.it with ESMTPSA id 00000000005DC042.000000005F3795CF.00004AE2; Sat, 15 Aug 2020 09:59:11 +0200
To: dmarc@ietf.org
References: <CADyWQ+H4D9+ELpsjxggEWwzg+WwUZs9mXzy8iNnLZCTfGORACA@mail.gmail.com> <745030ea-c2e6-16a4-690f-bbb639b9b8b8@bluepopcorn.net>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <a38eb7e9-6a47-871d-7352-4930f99a1db6@tana.it>
Date: Sat, 15 Aug 2020 09:59:09 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <745030ea-c2e6-16a4-690f-bbb639b9b8b8@bluepopcorn.net>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/UjI8jw_3jqIxSwmsRfzhwWJGVig>
Subject: Re: [dmarc-ietf] Call for Adoption: DMARC Use of the RFC5322.Sender Header Field
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 15 Aug 2020 07:59:14 -0000

On Fri 14/Aug/2020 21:08:56 +0200 Jim Fenton wrote:
> 
> If the Sender header field is to be used by DMARC in the manner
> described in this draft, it should be an integral part of the DMARCbis
> specification rather than a separate extension to it. In other words,
> this should be an issue on the DMARC WG issue tracker rather than a
> working group draft (and presumably eventual RFC). There are enough
> different combinations of originators and receivers that might use
> Sender (which the chart in Section 2 begins to describe) that we don't
> need the ongoing ambiguity of whether the receiver does or does not
> implement this as an extension.


100% agreed.  However, since I haven't yet understood how exactly the 
spec is going to be split among various I-Ds, I voted for adoption in 
order to boost discussion.


Best
Ale
--