Re: [dmarc-ietf] Been Quiet Around Here - Org Domain? Tree Walk?

Scott Kitterman <sklist@kitterman.com> Tue, 05 April 2022 22:44 UTC

Return-Path: <sklist@kitterman.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 261E83A1394 for <dmarc@ietfa.amsl.com>; Tue, 5 Apr 2022 15:44:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.11
X-Spam-Level:
X-Spam-Status: No, score=-7.11 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, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=kitterman.com header.b=Cg0vjxwj; dkim=pass (2048-bit key) header.d=kitterman.com header.b=NklY9f65
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 Vwmdc5ZS-LR8 for <dmarc@ietfa.amsl.com>; Tue, 5 Apr 2022 15:44:53 -0700 (PDT)
Received: from interserver.kitterman.com (interserver.kitterman.com [64.20.48.66]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 117223A137A for <dmarc@ietf.org>; Tue, 5 Apr 2022 15:44:52 -0700 (PDT)
Received: from interserver.kitterman.com (interserver.kitterman.com [IPv6:2604:a00:6:1039:225:90ff:feaa:b169]) by interserver.kitterman.com (Postfix) with ESMTPS id 35693F80260 for <dmarc@ietf.org>; Tue, 5 Apr 2022 18:44:51 -0400 (EDT)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903e; t=1649198691; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=TqqpqYnkM8PHk4m9yjdyMz7coo/wGZQdM4EoWRKnbQI=; b=Cg0vjxwjVYz/cKkRNWCzOonW+5BDDx5MCqHTe1JGfk01m/m2ix9609zvkL3QhmjcZQha1 J1O6cT0j7+0K8AlAQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1649198691; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=TqqpqYnkM8PHk4m9yjdyMz7coo/wGZQdM4EoWRKnbQI=; b=NklY9f65ZTUStYWYdxCYSPyvS/fVXFEOHOeznuJN0wbkV+FJegTvGJmP/Qb76GTFde7sw UKfdLo65/REfMjLLhxPSZEA8/FKfA034e/D6P4arOwm7tdfg5B8v8ZMnMjKxvEuQdAMoZOd MwpkW3Lh7N5u3to1oN2EshgvN9NuNxf04mDs4uS9jKezRFdSUU1Ka2SCgfC7s9GRoQwjMNp g3byTgK333rL4ix8HnDQFr/ZDKiXLwkPFneTW9UvSh26Bj30XEjD8hJCVlSghySvVMrKsge gpV9Zr304ileoFlldweXaTt2HK6jhlA/T6JmwhmvYkDHWuzF9mTpJ/KwNMUA==
Received: from zini-1880.localnet (static-72-81-252-22.bltmmd.fios.verizon.net [72.81.252.22]) by interserver.kitterman.com (Postfix) with ESMTP id 17D01F8014F for <dmarc@ietf.org>; Tue, 5 Apr 2022 18:44:51 -0400 (EDT)
From: Scott Kitterman <sklist@kitterman.com>
To: dmarc@ietf.org
Date: Tue, 05 Apr 2022 18:44:50 -0400
Message-ID: <15132233.jvnO6Z6p63@zini-1880>
In-Reply-To: <e63165a8-3b1c-ec0d-e81f-17c138c90133@tana.it>
References: <20220317195040.E6EFD3954931@ary.qy> <4570053.8rGbQFW28E@zini-1880> <e63165a8-3b1c-ec0d-e81f-17c138c90133@tana.it>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/Trn57rS6l82VTYR18ic3-rEyFPM>
Subject: Re: [dmarc-ietf] Been Quiet Around Here - Org Domain? Tree Walk?
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, 05 Apr 2022 22:44:58 -0000

On Monday, April 4, 2022 1:39:35 PM EDT Alessandro Vesely wrote:
> On Mon 04/Apr/2022 15:14:07 +0200 Scott Kitterman wrote:
> > On Sunday, April 3, 2022 12:15:23 PM EDT Alessandro Vesely wrote:
> >> On Mon 21/Mar/2022 23:02:03 +0100 Scott Kitterman wrote:
> >>> On March 21, 2022 5:42:42 PM UTC, Alessandro Vesely <vesely@tana.it> 
wrote:
> >>>> According to the definition, two identical domains having psd=y
> >>>> are in strict alignment but not in relaxed alignment, which is
> >>>> somewhat counterintuitive.
> >>> 
> >>> Actually, no:
> >>> 
> >>> "If this process does not determine the Organizational Domain, then
> >>> 
> >>>     the initial target domain is the Organizational Domain."
> >>> 
> >>> This text in DMARCbis06 addresses that case.
> >> 
> >> While that's true, it could be possible to revise the comparison
> >> process so as to account for identical domains.  In that case, we
> >> could avoid to call Organizational Domain one with no DMARC record.
> > 
> > I thought I had covered this already in Section 4.8.  I'll add it to the
> > list in the note.
> 
> Yeah, the text you wrote Sunday night looks better.  I'd say:
> 
>     If this process does not determine the Organizational Domain, then
>     there is no Organizational Domain.
> 
> That requires rewording the definitions of relaxed alignment.  For example:
> 
> OLD
>     In relaxed mode, the Organizational Domains of both the DKIM-
>     authenticated signing domain (taken from the value of the d= tag in
>     the signature) and that of the RFC5322.From domain must be equal if
>     the identifiers are to be considered to be aligned.  In strict mode,
>     only an exact match between both Fully Qualified Domain Names (FQDNs)
>     is considered to produce Identifier Alignment.
> 
> NEW
>     In strict mode, an exact match between both Fully Qualified Domain Names
> (FQDNs) is required to produce Identifier Alignment.  In relaxed mode, an
> exact match of either both identifiers or of their respective
> Organizational Domains, if both exist, is considered to produce Identifier
> Alignment.

So far, I don't think we've messed with those definitions.  I'd prefer not to  
change them.

Scott K