Re: [dmarc-ietf] PSD flag vs Version bump

John R Levine <johnl@taugh.com> Sat, 10 June 2023 21:20 UTC

Return-Path: <johnl@taugh.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 C592CC17B345 for <dmarc@ietfa.amsl.com>; Sat, 10 Jun 2023 14:20:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b="znEkeOj5"; dkim=pass (2048-bit key) header.d=taugh.com header.b="qMQVkRMa"
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 u9jlJEV5CtV3 for <dmarc@ietfa.amsl.com>; Sat, 10 Jun 2023 14:20:10 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A7207C17B342 for <dmarc@ietf.org>; Sat, 10 Jun 2023 14:20:10 -0700 (PDT)
Received: (qmail 38928 invoked from network); 10 Jun 2023 21:20:09 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:content-transfer-encoding; s=980e.6484e909.k2306; bh=YuWo1NFROPXwJa2d9pG4462RFHbsUybDPCUvNQbHMa8=; b=znEkeOj54Ry4AamerJVTFRcKVJYl2PAuG6cgR64fPTuk8E+sFZbaKxDeV/M+R41ix5ERusylZxgGcdGaD9FeRY9M4z7sgj5cPcyZ6+ZPyFmOsWzyxgSC52WJTeU8NgHqVZzAK6Cr/EZ3peyFEL5BdYl22PePCl+d+R9UlovKqCnw1UIeyECW0aBU96KYIEJUttgeYfbGo9TY39JbMloGAGFIW57pIFPvizTjhVPTnETmDJ/74C/KqpvaA8J8v/pGWpzQTnRwz9uNtd85lQCbyCOzhYrnNFIyqeS68nXpcrB2er540VHyCW/EK4x2D1kT9Qg5RXgOwrDmMZNCNibvDA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:content-transfer-encoding; s=980e.6484e909.k2306; bh=YuWo1NFROPXwJa2d9pG4462RFHbsUybDPCUvNQbHMa8=; b=qMQVkRMaWOvwR5MV6Qkd/4zeoA/2q7e66fwJR9y+8OxYlOMjTgHCRCs0peOAw3ZKMHiQCc5ha238CVTChblHI7Csre6BpT4QcCH+8msGP+JqHRtH1F7JQMr1LKcYqMg9UYweikx4IhmVaK07aQwcCRFmGmU6CuNK8IAhgKXPMiBVSpwXmzhpyRDM993dcWPEizFSkn1JwqdibZyhS7qduz1XyMLjOx/BBIJe0CIpkrLg7BW86JejsssNc/qODou+78tgzVY/kuWrHsEwJinTwhLtwhhlVFS4gICdQ9AuPOKoNjCMEprf5gVaTYjC1UcwChqga7+zzFgyXlJ4EEBZ1A==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.3 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 10 Jun 2023 21:20:08 -0000
Received: by ary.qy (Postfix, from userid 501) id 10E2CE92690B; Sat, 10 Jun 2023 17:20:07 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id B1C43E9268EA; Sat, 10 Jun 2023 17:20:07 -0400 (EDT)
Date: Sat, 10 Jun 2023 17:20:07 -0400
Message-ID: <03462d8f-57cb-b09e-e381-7f19a19b2e0f@taugh.com>
From: John R Levine <johnl@taugh.com>
To: Barry Leiba <barryleiba@computer.org>
Cc: dmarc@ietf.org, Scott Kitterman <sklist@kitterman.com>
X-X-Sender: johnl@ary.qy
In-Reply-To: <CALaySJJt4TpjoSoX7-s4oPH33ZaTqRMM_i0-TMTBOBDm0h-DiQ@mail.gmail.com>
References: <502ADE6F-E01E-4DF0-BF79-6A5E810A3F96@kitterman.com> <20230610210457.B4C22E924922@ary.qy> <CALaySJJt4TpjoSoX7-s4oPH33ZaTqRMM_i0-TMTBOBDm0h-DiQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/MAYCLguQ6q8wgDUuUh5wrU7kRq8>
Subject: Re: [dmarc-ietf] PSD flag vs Version bump
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, 10 Jun 2023 21:20:15 -0000

> Why not say "SHOULD use tree walk", and then document, as explanation
> for "SHOULD" instead of "MUST", non-normative reasons why you might
> not?

I don't think that will fly with the VLMPs.  The mandatory PSD seems 
relatively easy to implement, just add it to the template you use for 
everything.

R's,
John

> On Sat, Jun 10, 2023 at 5:05 PM John Levine <johnl@taugh.com> wrote:
>>
>> It appears that Scott Kitterman  <sklist@kitterman.com> said:
>>>
>>> What's the incentive that any existing DMARC users (senders or receivers) would have to invest additional resources in another email
>>> authentication protocol?
>>
>> We have two of the largest mail operators in the world saying that if
>> they can't tell which org domain scheme domain expects, they won't
>> implement the tree walk. We have to do something or we are wasting our
>> time.
>>
>> So how about this: in the tree walk, you look for DMARC records that
>> have an explicit psd=y/n/u tag. If you find at least one record with a
>> tag, you use the new scheme. If you find no records with a tag, you
>> fall back to the old scheme. I think this will let people do
>> everything they can do with the current tree walk, while being
>> backward compatible. If you want a domain to be an org domain you put
>> psd=n, if you want the tree walk to skip it and keep looking, you put
>> psd=u, and if it's one of the 0.001% of domains that actually is a
>> PSD, you put psd=y.
>>
>> We already added DiscoveryType to the aggregate report schema so we
>> are OK there.
>>
>> R's,
>> John
>>
>> PS: Whether we say people SHOULD NOT use SPF is a separate issue.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly