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

John Levine <johnl@taugh.com> Tue, 28 July 2020 18:01 UTC

Return-Path: <johnl@iecc.com>
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 D0FBD3A0CD7 for <dmarc@ietfa.amsl.com>; Tue, 28 Jul 2020 11:01:27 -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, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=UuoLrvXe; dkim=pass (1536-bit key) header.d=taugh.com header.b=RHssMtXD
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 NzcVXqobnx69 for <dmarc@ietfa.amsl.com>; Tue, 28 Jul 2020 11:01:26 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 A33DB3A0C1D for <dmarc@ietf.org>; Tue, 28 Jul 2020 11:00:55 -0700 (PDT)
Received: (qmail 88630 invoked from network); 28 Jul 2020 18:00:54 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=15a33.5f2067d6.k2007; bh=XNMl9ru9XfWpM/85RGqQZw92Jb2t8Geh9GZhL7kAlXg=; b=UuoLrvXeUUHhGrmGXTlqvp05YKLLFzF6eTyYXqLLeWoNwpCaWsRgh+nO6SfySksTAnFrpAEHDx6c362AJ48K4z8MmMPwOVBZV13M94lgdZ8KhXhf9FykUzLxlq78X+6DCqiKWApfbb3UNPW2av9pBDZXzxc09T0qheEJFmBmg1FUqnweg5j078mfuafH0xuP6HzTEXCaIlcaN/hrzmzO649KCNXolsQXdJd3xZ6UGdZQvdfsfVzB5UTU4b5vjVKZ
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=15a33.5f2067d6.k2007; bh=XNMl9ru9XfWpM/85RGqQZw92Jb2t8Geh9GZhL7kAlXg=; b=RHssMtXDTu9dGShl262TrmBWsLh75yIlKHqRJDEkdCc8Bk6Ac9JA9o96ssJpGancBQMJPib7+dukhNXYfO+fFLWFYK5uG1EzTeu+8gkMOo0izHjV+JU+SpKncWiS4mDKSts6Gqqqtmmkt6tFEiaQ2I84/18CNpSpBKFjWz5g3FbxzQHHqCIv5hn+D3ONIX2IcX6KAfKlxUfmx9QFzZ+TayubJ6mO1kmCB/KvLpz0WZ0K+DvlMzA8uAd3NsdiHFvV
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 28 Jul 2020 18:00:53 -0000
Received: by ary.qy (Postfix, from userid 501) id 44C901D98571; Tue, 28 Jul 2020 14:00:53 -0400 (EDT)
Date: Tue, 28 Jul 2020 14:00:53 -0400
Message-Id: <20200728180053.44C901D98571@ary.qy>
From: John Levine <johnl@taugh.com>
To: dmarc@ietf.org
Cc: dcrocker@bbiw.net
In-Reply-To: <ab4d6cbc-2666-e46a-0f3f-fffc7e2bab1a@dcrocker.net>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/9o1R520rVhwLXn4eeHQFHw4RTKo>
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 18:01:33 -0000

In article <ab4d6cbc-2666-e46a-0f3f-fffc7e2bab1a@dcrocker.net> you write:
>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.

Unfortunately, we all know where to find DBOUND.

I suppose now that the smoke has somewhat cleared we might take another
run at the PSL problem, trying harder not to boil the ocean.

R's,
John

PS: https://github.com/jrlevine/bound