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

Barry Leiba <barryleiba@computer.org> Sat, 10 June 2023 21:13 UTC

Return-Path: <barryleiba@gmail.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 03E6AC15C501 for <dmarc@ietfa.amsl.com>; Sat, 10 Jun 2023 14:13:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.547
X-Spam-Level:
X-Spam-Status: No, score=-6.547 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.096, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=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
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 Tc7g8S9U4kP5 for <dmarc@ietfa.amsl.com>; Sat, 10 Jun 2023 14:13:24 -0700 (PDT)
Received: from mail-ej1-f51.google.com (mail-ej1-f51.google.com [209.85.218.51]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 3CA5AC14CE27 for <dmarc@ietf.org>; Sat, 10 Jun 2023 14:13:24 -0700 (PDT)
Received: by mail-ej1-f51.google.com with SMTP id a640c23a62f3a-9745d99cfccso523201666b.1 for <dmarc@ietf.org>; Sat, 10 Jun 2023 14:13:24 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686431602; x=1689023602; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=NhUTCGitVQziXrsC8Oy5WiFOz2A1r7da2EnE4i6YQ+k=; b=eer3iV59zjC/IuL3vOpzYFAQKBz4Q+NNjtlPpS47G0IzoFsSVYm05HPdy/AJBsb3pz 3kme+q1TH4k0KmK7emgKkEnO7TG+vlcR2nMAJOPLPYkKtDdY0vH3viNOe2TfV0t8S7j8 mBnIs2jcUTUoMgR69JdI1KwQKaiVq80wE8CU3r7FYCv0NLoD33XNI2KatMkhCYE7Jebo wwy9JV1i8+ke2/ufkPmeug2xubwl8AhwEufy7dv/20Lz+hPxwB9Gz5GO0j/5+lPUBoZv dl1af6LjCndL2fZmHwsQpgWKT6iaeyLB4ARTt0+p8eZsw5fwzZ73k4i5A2lQe2c7GLED GgJg==
X-Gm-Message-State: AC+VfDxbxomQ7y7Jbg/OpadfPwGplN6oKVCoRS7q8D2rU9OmS0WKtuut PknFhI6+a3YIHgazJ7ueouLJBcRJOmlhjmJB+dJIlLIL
X-Google-Smtp-Source: ACHHUZ5NnyDejSeuq/LYYy2fZ5+lBysVEZzTy4dyMAaWWT2Dgifp3jYz2ey3FEWLfBjINb9GAjSeOqG9mibDsd7HqBw=
X-Received: by 2002:a17:907:789:b0:974:c32c:b485 with SMTP id xd9-20020a170907078900b00974c32cb485mr5320834ejb.45.1686431602362; Sat, 10 Jun 2023 14:13:22 -0700 (PDT)
MIME-Version: 1.0
References: <502ADE6F-E01E-4DF0-BF79-6A5E810A3F96@kitterman.com> <20230610210457.B4C22E924922@ary.qy>
In-Reply-To: <20230610210457.B4C22E924922@ary.qy>
From: Barry Leiba <barryleiba@computer.org>
Date: Sat, 10 Jun 2023 17:13:08 -0400
Message-ID: <CALaySJJt4TpjoSoX7-s4oPH33ZaTqRMM_i0-TMTBOBDm0h-DiQ@mail.gmail.com>
To: John Levine <johnl@taugh.com>
Cc: dmarc@ietf.org, sklist@kitterman.com
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/qQW6wjxzyDz4XId0Rb1i9nziO2w>
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:13:28 -0000

Hm...

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

Waddyathink?

Barry


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.
>
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc