Re: [dmarc-ietf] 5.5.4. Publish a DMARC Policy for the Author Domain - dmarcbis-06

Alessandro Vesely <vesely@tana.it> Sun, 03 April 2022 11:21 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 5366D3A1BA5 for <dmarc@ietfa.amsl.com>; Sun, 3 Apr 2022 04:21:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.108 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.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, 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=BPD7FsTS; dkim=pass (1152-bit key) header.d=tana.it header.b=AHFV3HLy
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 xxFgI4Z7YQpl for <dmarc@ietfa.amsl.com>; Sun, 3 Apr 2022 04:21:10 -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 74F2E3A08B8 for <dmarc@ietf.org>; Sun, 3 Apr 2022 04:21:07 -0700 (PDT)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=tana.it; s=epsilon; t=1648984861; bh=uNnbEjhLOlSSpNce8al4kzGRrGZcY5ZOx3dBY/DMMic=; h=Date:Subject:To:References:From:In-Reply-To; b=BPD7FsTS2l6J84/J5AuVLaI2UES09wydNtKjc1iaJBsOJ1xVsM8A1f5RP5Z9q9Xrc PPOf6Xegnq7EjChUXuLCQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1648984861; bh=uNnbEjhLOlSSpNce8al4kzGRrGZcY5ZOx3dBY/DMMic=; h=Date:To:References:From:In-Reply-To; b=AHFV3HLyRteomT8G1Eax6tjB3ewBRsE5dsYRQMrwLSkoB3iRpq44+BBiiswT3xe86 svpDVKh3/oQvKmLphVTvI4ZAh56j8HNklDGzMgaf625xovMgObbnozwf8dL28qKiZo I/yICVLhNpOtXsmQLiEY/ZzOHztylAwMkctYGrWeO05r4rJFSdtmjlMic23+d
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 00000000005DC0D6.000000006249831D.00005D40; Sun, 03 Apr 2022 13:21:01 +0200
Message-ID: <45a019b3-3f97-6c56-409b-5a3f9f2d06ba@tana.it>
Date: Sun, 3 Apr 2022 13:21:00 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.6.2
Content-Language: en-US
To: John Levine <johnl@taugh.com>, dmarc@ietf.org
References: <20220403024904.479EA3A462E4@ary.qy>
Authentication-Results: tana.it; auth=pass (details omitted)
From: Alessandro Vesely <vesely@tana.it>
In-Reply-To: <20220403024904.479EA3A462E4@ary.qy>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/u75VfkmPlrNE812RfEDvxVIXmBA>
Subject: Re: [dmarc-ietf] 5.5.4. Publish a DMARC Policy for the Author Domain - dmarcbis-06
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: Sun, 03 Apr 2022 11:21:19 -0000

On Sun 03/Apr/2022 04:49:03 +0200 John Levine wrote:
> It appears that Scott Kitterman  <sklist@kitterman.com> said:
> 
>>2.  In the policy discovery section I added a few sentences on which policy to 
>>use once the policy record is identified.  This doesn't change anything 
>>relative to what's currently defined, but it seems to me that if we are going 
>>to have a discussion of policy discovery we should take it all the way to 
>>determining the poilcy and not stop at the determination of the record to use 
>>to determine the policy.
> 
> It still gets the wrong answer for psd=n above psd=y.


Why?


> I think it needs to say you walk up. At each step if you find psd=n,
> that is the org domain and you stop.


Right, that's step 1 of 4.8.


> If you find psd=y, that is the PSD, the org is the name beneath it, and you
> stop.

Yup, unless that's the From: domain (the sending PSO case).


> (If the one beneath it has no DMARC record, is it still the org domain? I
> think it is.)

This seems to be inconsistent with the sentence that follows.  Would the 
landscape change if .com suddenly publishes psd=y?


> If you get to the top and there was no record with psd=y or psd=n, the
> org is the highest DMARC record you found.



Best
Ale
--