Re: [dmarc-ietf] A few old nits

Alessandro Vesely <vesely@tana.it> Thu, 23 June 2022 11:36 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 0F8DFC180A8B for <dmarc@ietfa.amsl.com>; Thu, 23 Jun 2022 04:36:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.006
X-Spam-Level:
X-Spam-Status: No, score=-9.006 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=-1.876, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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=tana.it header.b=FNLg14CV; dkim=pass (1152-bit key) header.d=tana.it header.b=C2b9m06k
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 J6XggBfHvBVv for <dmarc@ietfa.amsl.com>; Thu, 23 Jun 2022 04:36:21 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) (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 36BECC184159 for <dmarc@ietf.org>; Thu, 23 Jun 2022 04:36:18 -0700 (PDT)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=tana.it; s=epsilon; t=1655984173; bh=6kSc7P6PxBClsdMRHVlNtJsr4jcyfNhAeLM2ML8kvNU=; h=Date:Subject:To:References:From:In-Reply-To; b=FNLg14CVUyVY2JUQm5e7uIYShM0rbFmc/2N+jrAqXOExMakuC3isv4YhY8dIekIS1 oRYnV8n16+ld5+pcLajCQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1655984173; bh=6kSc7P6PxBClsdMRHVlNtJsr4jcyfNhAeLM2ML8kvNU=; h=Date:To:References:From:In-Reply-To; b=C2b9m06kpUHBlEgOtdFZjGgLn97ypTc+1Ci6tbYu/JmNxOgdd0flF2mibf1uYnffi qG5Pm9EOhqgAaSivFZmlRi7vmImkMfZ5yB2jnsXEP93hbJVu5/6LxKwlzMX9RsHMXy GJAQySEvXPWgE4Rd/u6GCge5SmSP256tKs6IAiAOFZd7gRVc3+w3635gAwGs6
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.0000000062B4502C.000056E7; Thu, 23 Jun 2022 13:36:12 +0200
Message-ID: <e705aa1a-4f45-5fef-12e3-59b9d5f2dd0a@tana.it>
Date: Thu, 23 Jun 2022 13:36:12 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.0
Content-Language: en-US
To: dmarc@ietf.org
References: <19483ccf-54a4-f25e-fabf-9c836152165c@tana.it> <2597405.nbnHmP34a0@zini-1880> <75bf730504c4bc6d7f6bb5a2f6489f3fad85c961.camel@16bits.net>
Authentication-Results: tana.it; auth=pass (details omitted)
From: Alessandro Vesely <vesely@tana.it>
In-Reply-To: <75bf730504c4bc6d7f6bb5a2f6489f3fad85c961.camel@16bits.net>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/YW6IYj1b194uouyDVh65ZTmeEv0>
Subject: Re: [dmarc-ietf] A few old nits
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: Thu, 23 Jun 2022 11:36:28 -0000

On Thu 23/Jun/2022 03:50:29 +0200 Ángel wrote:
> On 2022-06-22 at 08:39 -0400, Scott Kitterman wrote:
>> I agree.  How about changing "Instead, some domains will inherit their DMARC 
>> policy records from parent domains one level or more above them in the DNS 
>> hierarchy" to "Instead, domains which have a DMARC record will use that as the 
>> DMARC policy record even in cases where the Organizational Domain is a parent 
>> domains one level or more above them in the DNS hierarchy"?  There's no case 
>> where there's a policy for a domain, that's the org domain and then a higher 
>> level domain in the tree is used for policy.  I think this more correctly 
>> describes the distinction.
> 
> I don't think that Instead to be appropriate in the new phrase. Also, b
> eware of the plural: "Is a parent domains".
> 
> What about:
>     The relevant DMARC record for these purposes is not necessarily the
>     DMARC policy record found in DNS at the same level as the name label
>     for the domain in question. Domains which have a DMARC record
>     will use that as the DMARC policy, but in other cases they will
>     inherit their DMARC policy records from parent domains one level
>     or more above them in the DNS hierarchy.


It still has the confusing "policy record found at the same level"...  I'd opt 
for a plain sentence like so, for example:

     DMARC provides for looking for a policy record in the parent
     domain(s) if none is found at the same level as the name label
     for the domain in question.


Best
Ale
--