Re: [dmarc-ietf] Bridging the gap

Scott Kitterman <sklist@kitterman.com> Sat, 18 June 2022 00:40 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 83C62C159486 for <dmarc@ietfa.amsl.com>; Fri, 17 Jun 2022 17:40:57 -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=5SIuJPI2; dkim=pass (2048-bit key) header.d=kitterman.com header.b=qpcQHWeM
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 bXZmc15c841Z for <dmarc@ietfa.amsl.com>; Fri, 17 Jun 2022 17:40:53 -0700 (PDT)
Received: from interserver.kitterman.com (interserver.kitterman.com [IPv6:2604:a00:6:1039:225:90ff:feaa:b169]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B4E5C157B43 for <dmarc@ietf.org>; Fri, 17 Jun 2022 17:40:53 -0700 (PDT)
Received: from interserver.kitterman.com (interserver.kitterman.com [64.20.48.66]) by interserver.kitterman.com (Postfix) with ESMTPS id 09438F8023F for <dmarc@ietf.org>; Fri, 17 Jun 2022 20:40:50 -0400 (EDT)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903e; t=1655512849; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=8FVfXsdnfOgP24pQKJ30x0NYhdTLzDlj70ktl3Q141o=; b=5SIuJPI2Kz0hjysLcLEzD+99wG8beV/I6mIIy09kkfNNmjfeKb78Cgg/OcYvtVANCCNrR D2S7p1Wmw7qy5obCQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1655512849; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=8FVfXsdnfOgP24pQKJ30x0NYhdTLzDlj70ktl3Q141o=; b=qpcQHWeMXt1m0KCA8C18y79OQzxh44FK8Y6N9Y6fWKn7t1j51S79EIKERgy20qDjamaMt lMIsPbtovdi+vQsYpoL7FXkWrhP6T1GcijMEoZgaX+2ICYJSOP3tWEvPZJGifSzmRzTbbbv KWwmggjD6QXuYKrEYKboaI487asrvsm6rDibUypc1FazaSBsc0eB4dVM9AgKTectUUL7bsd UecbnYadx+Tk2g9XibbV4BwklCUPVt5I1jufTQinDmHhqBNuqhvM3wVJYKCp5skH/IGdRgv ZrcyE5d1kUm11qiQrf26IlDdlWZwM6jN+6iEtjdVqv/6kyst0etgDHj1Jp0g==
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 C6A29F80232 for <dmarc@ietf.org>; Fri, 17 Jun 2022 20:40:49 -0400 (EDT)
From: Scott Kitterman <sklist@kitterman.com>
To: dmarc@ietf.org
Date: Fri, 17 Jun 2022 20:40:49 -0400
Message-ID: <2556752.voWYGx1xz9@zini-1880>
In-Reply-To: <edde1042-3ac8-6538-816a-411800c709ff@tana.it>
References: <20220615174742.BBCE443B1333@ary.local> <edde1042-3ac8-6538-816a-411800c709ff@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/ogzepkmOrUY26xpmIJNTl41AR2k>
Subject: Re: [dmarc-ietf] Bridging the gap
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: Sat, 18 Jun 2022 00:40:57 -0000

On Thursday, June 16, 2022 11:57:08 AM EDT Alessandro Vesely wrote:
> On Wed 15/Jun/2022 19:47:42 +0200 John Levine wrote:
> > It appears that Alessandro Vesely  <vesely@tana.it> said:
> >>I think we found the few critical domains which need a flag.
> >>
> > We may have found some domains that need a psd flag, but it's silly to
> > assert we have found all or even most of them.
> > 
> > The PSL has 9300 entries and there are surely far more places in the DNS
> > than that where you want sibling domains to be separate.
> 
> Is there someone who is going to contact, on behalf of the WG, the domains
> that were found in order to have their owners publish psd= flags before the
> RFC is published?

It is a project I intend to work on once the psd= tag has been assigned.  
Until the working group has settled on it more definitively than "it's in the 
current draft" I think it would be premature to bother them.

>From your list further down the thread, why do you think having a psd=y tag on 
gov.uk, police.uk, and mil will have?  While it would be more descriptively 
correct, I don't think there's any operational difference if it's there or not 
since sub-domains of those PSDs are controlled by one organization.

If us.com had a DMARC record, that would be worth a discussion, but they 
don't.  It's not even the ~500 domains on the PSL that have DMARC records 
published that we need to concern ourselves with, it's a small subset of them.

Scott K