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

Scott Kitterman <sklist@kitterman.com> Tue, 05 April 2022 22:56 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 8F5AF3A14AE for <dmarc@ietfa.amsl.com>; Tue, 5 Apr 2022 15:56:03 -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=xuGIg7Ly; dkim=pass (2048-bit key) header.d=kitterman.com header.b=WcJ040SV
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 WEGPC9Ht3HOz for <dmarc@ietfa.amsl.com>; Tue, 5 Apr 2022 15:55:58 -0700 (PDT)
Received: from interserver.kitterman.com (interserver.kitterman.com [IPv6:2604:a00:6:1039:225:90ff:feaa:b169]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E4A63A14EC for <dmarc@ietf.org>; Tue, 5 Apr 2022 15:55:54 -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 2B289F80260 for <dmarc@ietf.org>; Tue, 5 Apr 2022 18:55: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=1649199351; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=T7FrtDvoDcoG6MC7FXAM/NNeHGRmcq6Xx4PolF69t28=; b=xuGIg7LytCFAekSu0l+QnmXp4xbB1BfSN1PCIoMKZiuv/vr5ZZII9dudFsH/WYDi/sVJi gV1PwvRzrQN48GDDw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1649199351; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=T7FrtDvoDcoG6MC7FXAM/NNeHGRmcq6Xx4PolF69t28=; b=WcJ040SV+8qovvHd7VZeIqXtFTEnVGwca8kLHhdGsQKKyY+s2nuDKwoJd8haYzPEVOECR XlgADgJ2HX2G/FWU7zqgthCcjx0JcGNDOa9Gz72RlH8rja8lRlqcRxc4lCoNST/zG/Tvr1n 8laFSdK8wgOupkptS5ZPX0dfxTMTD88y31FJg0jVgTLlOhEsDUF4jJVQWLcPJAZmul8z9vr u04aDpE5MdSoFCOs+NbgrEtX7vQp/ANH7sHxyMg15ndyCTX8DoNaPl2AqUIGjIPQ9oJGglG t6S1UhTtPXs7RZ8s+geQ3FBoV3E9N/o/RgFtwM3tqins2opJOR1Zusa6M3Fw==
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 0D6DFF8014F for <dmarc@ietf.org>; Tue, 5 Apr 2022 18:55:51 -0400 (EDT)
From: Scott Kitterman <sklist@kitterman.com>
To: dmarc@ietf.org
Date: Tue, 05 Apr 2022 18:55:50 -0400
Message-ID: <1782962.OBcs8SkWkA@zini-1880>
In-Reply-To: <362b2316-53fc-59bc-ba71-d9fe4b184c8a@tana.it>
References: <20220403024904.479EA3A462E4@ary.qy> <0c06b5b0-a298-479d-90b5-a17cfaa4e672@taugh.com> <362b2316-53fc-59bc-ba71-d9fe4b184c8a@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/kGyLoDvFpuueDAx9tMi7_gfzRBo>
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: Tue, 05 Apr 2022 22:56:04 -0000

On Tuesday, April 5, 2022 3:57:30 AM EDT Alessandro Vesely wrote:
> On Mon 04/Apr/2022 19:31:36 +0200 John R Levine wrote:
> >>> If it's the original domain, yes.
> >> 
> >> We know that co.uk is not an Organizational Domain.  Asking what is the
> >> Organizational Domain of co.uk is an ill-posed question.
> > 
> > These are all in the PSL.  What are their organizational domains?
> 
> Scott took the time to define PSDs and PSOs in RFC 9091, restated in
> Sections 3.2.8 and 3.2.9 of the current draft.  Since the definitions of
> Organizational Domain (both the current 3.2.7 an my proposed change)
> require PSD + 1, a PSD has to be a proper subdomain of another PSD in order
> to admin an Organizational Domain itself.
> 
> > _dmarc.wa.gov.au TXT "v=DMARC1; p=none; fo=1:d;
> > rua=mailto:dmarc_rua@emaildefense.proofpoint.com,mailto:dmarc_records@wa.
> > gov.au;ruf=mailto:dmarc_rua@emaildefense.proofpoint.com,mailto:dmarc_recor
> > ds@wa.gov.au" wa.gov.au mail is handled by 10
> > inbound-smtp.us-west-2.amazonaws.com. wa.gov.au TXT "v=spf1
> > include:amazonses.com ~all"
> > 
> > _dmarc.gov.az TXT "v=DMARC1; p=reject; pct=100; fo=1; adkim=s; aspf=s;
> > rua=mailto:dmarcrep@gov.az" gov.az mail is handled by 0 sea1.mail.gov.az.
> > gov.az mail is handled by 10 sea2.mail.gov.az.
> > gov.az TXT "v=spf1 redirect=_spfx.mail.gov.az"
> > 
> > _dmarc.gov.in TXT "v=DMARC1; p=quarantine; sp=none;
> > fo=1;rua=mailto:pmaster-wlist@gov.in;ruf=mailto:pmaster-wlist@gov.in"
> > gov.in mail is handled by 5 mailgwgov.nic.in.
> > gov.in TXT "v=spf1 mx ip4:164.100.14.0/24 ip4:164.100.2.0/24
> > ip4:164.100.10.0/24 ip4:164.100.15.0/24 ip4:164.100.13.0/24 -all"
> > 
> > _dmarc.edu.kz TXT "v=DMARC1; p=none; rua=mailto:abuse@edu.kz"
> > edu.kz mail is handled by 10 post.mail.kz.
> > edu.kz TXT "v=spf1 a mx ip4:88.204.157.164 ~all"
> > 
> > _dmarc.ac.me TXT "v=DMARC1; p=quarantine; adkim=r; aspf=r; fo=0; pct=100;
> > rua=mailto:dmarc@ac.me" ac.me mail is handled by 10 mail.ac.me.
> > ac.me TXT "v=spf1 mx ip4:89.188.43.10 ip6:2a02:4280:0:200:89:188:43:10
> > -all"
> > 
> > _dmarc.nhs.uk TXT "v=DMARC1; p=reject; sp=none;adkim=s;aspf=s;fo=1;
> > rua=mailto:A-NE.postmaster@nhs.net,mailto:dmarc-rua@dmarc.service.gov.uk"
> > nhs.uk mail is handled by 50 mail.nhs.uk.
> > nhs.uk TXT "v=spf1 ip4:213.161.89.71 ip4:213.161.89.72 ip4:213.161.89.73
> > ip4:213.161.89.103 ip4:213.161.89.104 ip4:213.161.89.105 -all"
> > 
> > _dmarc.police.uk TXT
> > "v=DMARC1;p=none;sp=none;adkim=s;aspf=s;fo=1;rua=mailto:dmarc-rua@dmarc.s
> > ervice.gov.uk;ruf=mailto:dmarc-ruf@dmarc.service.gov.uk" police.uk has no
> > MX record
> > police.uk TXT "v=spf1 -all"
> > 
> > _dmarc.k12.dc.us TXT "v=DMARC1; p=none;
> > rua=mailto:a6p7qzhr@ag.dmarcian.com;" k12.dc.us mail is handled by 10
> > dck12.mail.protection.outlook.com.
> All of the above admit no org domain.  I'd amend step 2 like so:
> 
> OLD
>     2.  If a valid DMARC record contains the psd= tag set to 'y' (psd=y),
>         the Organizational Domain is the domain one label below this one
>         in the DNS hierarchy, and the selection process is complete.
> 
> NEW
>     2.  If a valid DMARC record contains the psd= tag set to 'y' (psd=y),
>         the Organizational Domain is the previous domain of those selected,
>         if any.  In any case the selection process is complete.
> 
> 
> I note that only police.uk is registered at psddmarc.org.  It is also the
> only "pure" PSD, in the sense that they don't send mail themselves.
> 
> Scott, is that the reason why the others are not registered?
> 
> All them should amend their DMARC records adding psd=y.

The entities listed on the psddmarc.org registry requested to be there.  I 
think that once we've settled the questions around the psd tag the WG should 
ask for an early registration for the new tag.  I think that's the point where 
these entities should update their records.

Generally speaking, I think that a PSD can send mail and it should be covered 
by DMARC, so I disagree with the idea that a PSD can never also be an Org.

Scott K