Re: [dmarc-ietf] Separating DMARC alignment validation from DMARC policy

Dave Crocker <dhc@dcrocker.net> Tue, 28 July 2020 17:37 UTC

Return-Path: <dhc@dcrocker.net>
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 A93B93A0A4D for <dmarc@ietfa.amsl.com>; Tue, 28 Jul 2020 10:37:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 V3nNJU0o-P_W for <dmarc@ietfa.amsl.com>; Tue, 28 Jul 2020 10:37:16 -0700 (PDT)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (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 AB4EB3A0A49 for <dmarc@ietf.org>; Tue, 28 Jul 2020 10:37:16 -0700 (PDT)
Received: from [192.168.1.67] (108-226-162-63.lightspeed.sntcca.sbcglobal.net [108.226.162.63]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1.1) with ESMTP id 06SHdpUt031835 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 28 Jul 2020 10:39:51 -0700
To: "Murray S. Kucherawy" <superuser@gmail.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
References: <579385ce-b67d-9db0-0a9d-fdce9fece75d@dcrocker.net> <CAL0qLwbRj=N34KSaYq9eFFu_=iEooKpt+iU3mac1FPhLboni8A@mail.gmail.com>
Reply-To: dcrocker@bbiw.net
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <ab4d6cbc-2666-e46a-0f3f-fffc7e2bab1a@dcrocker.net>
Date: Tue, 28 Jul 2020 10:37:09 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <CAL0qLwbRj=N34KSaYq9eFFu_=iEooKpt+iU3mac1FPhLboni8A@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/HG0dHQy2EdjPCLB9AvaEMhZwxl4>
Subject: Re: [dmarc-ietf] Separating DMARC alignment validation from DMARC policy
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: Tue, 28 Jul 2020 17:37:18 -0000

On 7/28/2020 9:59 AM, Murray S. Kucherawy wrote:
> I think it was you that suggested having the determination of the 
> Organizational Domain be its own distinct process.  Would that fit into 
> the first document, or should that also be something external?


I'd wish for that to be entirely outside of DMARC, because the issue and 
the mechanism are not specific to DMARC.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net