Re: [dmarc-ietf] WGLC review of draft-ietf-dmarc-dmarcbis-30

Scott Kitterman <sklist@kitterman.com> Sun, 31 March 2024 16:48 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 C34E7C14F5FD for <dmarc@ietfa.amsl.com>; Sun, 31 Mar 2024 09:48:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.098
X-Spam-Level:
X-Spam-Status: No, score=-7.098 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-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=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=kitterman.com header.b="aOmD94Y7"; dkim=pass (2048-bit key) header.d=kitterman.com header.b="OIJ8FyLy"
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 ijlzcV-45_vi for <dmarc@ietfa.amsl.com>; Sun, 31 Mar 2024 09:48:26 -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) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9F107C14F5E4 for <dmarc@ietf.org>; Sun, 31 Mar 2024 09:48:26 -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 CEBD5F80275; Sun, 31 Mar 2024 12:48:13 -0400 (EDT)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903e; t=1711903681; h=date : from : to : subject : in-reply-to : references : message-id : mime-version : content-type : content-transfer-encoding : from; bh=xK6XL0pHSRsHEYY79cYA6KGBSdubjwDENwvo4ink8sU=; b=aOmD94Y7XvG4YRdtefibrNFnJm/7HQs1iOJjEAObzXgV3NpuPyVVWOQU7lLuAsalt3cVc FVVlov3uXSASIMeBg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1711903680; h=date : from : to : subject : in-reply-to : references : message-id : mime-version : content-type : content-transfer-encoding : from; bh=xK6XL0pHSRsHEYY79cYA6KGBSdubjwDENwvo4ink8sU=; b=OIJ8FyLyKQXCo3NGXlPOO0j0Q/OfM8t9CC9EK5YMCNPNxJQKBFvzuoM4Ac//kOGMYonXY 43vCF/XK/970QzyeYr4/oXV5odXe8bWw7X4ErUpqClksfAA1ZVvR3r5U0nwNwRRkhP0gHFw iYRXMdyvmnxHsMXS4pkSNepzeRmGwF2B0KhCYVs1eejv4z6e03MfL7RFc7otXgM2V/OdSh7 z5ee9Uki81+ENCH7Sz9+3UjaSG7617maeeDH1f9QdOevrUerX0ZtqIfrzHYyd4Mw0FkIxOu bWVfCHTMNP47Il2ABJPj8cZz91t1G725XOSnH5c+fdK6Lgp9jE+oF77nFJRQ==
Received: from [127.0.0.1] (unknown [50.186.163.153]) by interserver.kitterman.com (Postfix) with ESMTPSA id D1378F80156; Sun, 31 Mar 2024 12:47:57 -0400 (EDT)
Date: Sun, 31 Mar 2024 16:47:48 +0000
From: Scott Kitterman <sklist@kitterman.com>
To: dmarc@ietf.org
In-Reply-To: <CAL0qLwb9Wnv5Wv5U88S6Mu3Zod9RHx1u-0pihQ_vFE38=7jqPA@mail.gmail.com>
References: <F5158C76-BD86-4540-965D-F0D8664B6CD9@bluepopcorn.net> <85761761-ad6a-2a19-da82-344ed52c2391@iecc.com> <B4365E6E-00DF-425E-9974-6EE1DE057319@bluepopcorn.net> <CAL0qLwb9Wnv5Wv5U88S6Mu3Zod9RHx1u-0pihQ_vFE38=7jqPA@mail.gmail.com>
Message-ID: <D7DB8871-C708-44AE-97B9-BE5A2A9EA5F3@kitterman.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/We-AUblFG71yiEDZdIbkE-X-1E4>
Subject: Re: [dmarc-ietf] WGLC review of draft-ietf-dmarc-dmarcbis-30
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: Sun, 31 Mar 2024 16:48:30 -0000


On March 30, 2024 11:27:42 PM UTC, "Murray S. Kucherawy" <superuser@gmail.com> wrote:
>On only the charter point:
>
>On Sat, Mar 30, 2024 at 2:27 PM Jim Fenton <fenton@bluepopcorn.net> wrote:
>
>>
>> >> ??? Not Found
>> >> -------------
>> >>
>> >> I expected to find some text at least recommending a rewriting strategy
>> for From addresses to be used by mailing lists and the like.
>> >
>> > That would be extremely out of scope, not to mention something likely to
>> get the IESG to kick it back to us.
>>
>> The WG charter lists as the phase 1 work item for this WG, “Draft
>> description of interoperability issues for indirect mail flows and
>> plausible methods for reducing them.” This was published as RFC 7950
>> (informational). On the contrary, I would expect IESG to kick it back for
>> not even informatively referencing that work here.
>>
>
>I concur with Jim that rewriting strategies are in scope for the WG
>according to its charter, especially if we have something to recommend
>going forward.  RFC 7950 is informational and while it does discuss the
>issues in significant detail, it also falls short of making a specific
>recommendation.
>
>What's probably debatable here is whether the WG wants to include such a
>recommendation as part of the Proposed Standard it's aiming to put
>forward.  And keep in mind that the IETF still gets its Last Call to review
>the proposed document before the IESG gets it; the absence (or, indeed, the
>presence) of such advice might be significant then.

I think that we concluded that we didn't.  I don't think there's anything new here to debate.  I don't know what the IETF consensus will be, but I believe the WG concluded that standardizing such a thing would be inappropriate.

People implement horrible hacks all the time to get things to work.  It doesn't follow that they are worth documenting as correct.

Scott K