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

"Murray S. Kucherawy" <superuser@gmail.com> Sat, 30 March 2024 23:27 UTC

Return-Path: <superuser@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 BC2B3C14F615 for <dmarc@ietfa.amsl.com>; Sat, 30 Mar 2024 16:27:57 -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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 6xZzhzjqvO3P for <dmarc@ietfa.amsl.com>; Sat, 30 Mar 2024 16:27:57 -0700 (PDT)
Received: from mail-ed1-x532.google.com (mail-ed1-x532.google.com [IPv6:2a00:1450:4864:20::532]) (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 4D438C14F605 for <dmarc@ietf.org>; Sat, 30 Mar 2024 16:27:57 -0700 (PDT)
Received: by mail-ed1-x532.google.com with SMTP id 4fb4d7f45d1cf-56dc3cbe414so191133a12.0 for <dmarc@ietf.org>; Sat, 30 Mar 2024 16:27:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1711841275; x=1712446075; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=a341gihQU/XXrNZitTNtOEkz/btnbcpNxNR+Q07vvOU=; b=OFF61TtOFYUepQ+fE1xbR32l4sU+CkkgsCeCo/JFbULXS+M5Y/8G1dHDUYnByxTgMG 5NhGjsYcoaT/lmkKipQ62QXuBPtdAwIMs2F5uMcVu3ZwpykJsiRzgM5HBHS3Pwlapv6u t7JCI0mkcAvfEQ5pUZTiLXcMEurwzFKdCUdYdJk7Qm8A1Ttzs+HGtDEK5ox1YbXzmdsr c2QzAVgAuageH29otqI85KiL8ye1W3Q4YnCdSLlzweaosEJdm4aUDyh0dBMva6vk3ktK wFXmv0vB/vEjM/791Afjy92ixJKf7gQEqhSmS3VHZkLMQoEZ1eJhwwn4cSNpwI5x5TsT sEuA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1711841275; x=1712446075; h=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=a341gihQU/XXrNZitTNtOEkz/btnbcpNxNR+Q07vvOU=; b=jUOKDS35aA9qKGVnO92P2Vqv1cgGeHLxX9B1uiMScOXjOiw4rSdnXqidgUng1JtW2S swwuAStPzlXsB+IGvTxhkiThjMi5Wbn8dKxodw1xPLmJO5wGuL/35BOiSOiPETdJjS6o eFl007swrhQcnwvx+Ov/dpsAJjRPUUpaUPPMdxPhkFiLHBHijeXNlN6v7Z8gUZs4PDkJ u/BFZiahr4Iw6RGniDCLoqx2CVr7hYT9e8RTNK5+d9mPwkkJIrMAfvsB57BBehSNfo+6 hWyJIhHHDj1OQ50a5TLodf+pBIwoeMiW8tK81hl83KhHmcLBlkxcoB5JYyVkd47G41un cU7w==
X-Forwarded-Encrypted: i=1; AJvYcCWY8AYO0aKWD86WOxmPm3JOmCjZsjzx4Gysf5W8y+/tmfyqjNt5miXNi48u8aEJtBEmubDHBUKR2ojIsqumdQ==
X-Gm-Message-State: AOJu0Yx+QAHGxv4dY7W3q0pDFyjdPFTxhHR+wvsxV3h+wR4KfWbk3GFq xCI0NtEP1I1Rtxv8zZKK9d6gyKBXU/YYnOfEVBSJrFZcRtypj/UrmCor9WtI1AJh9q0D1+XwF5m FnDYhV5EkeCEnkcTG7pNMJds73Fy/KKcXJ6PiHQ==
X-Google-Smtp-Source: AGHT+IHkHS0uBX8eIgzv8yPy1XUhOYlBv87EqvfMS5wDcbsepSKjjn7w1xihl3f6FX09o0Gk/L0JpoHF+wO3fq9sqIw=
X-Received: by 2002:a17:907:6e8a:b0:a46:f9a0:748 with SMTP id sh10-20020a1709076e8a00b00a46f9a00748mr4344551ejc.5.1711841275118; Sat, 30 Mar 2024 16:27:55 -0700 (PDT)
MIME-Version: 1.0
References: <F5158C76-BD86-4540-965D-F0D8664B6CD9@bluepopcorn.net> <85761761-ad6a-2a19-da82-344ed52c2391@iecc.com> <B4365E6E-00DF-425E-9974-6EE1DE057319@bluepopcorn.net>
In-Reply-To: <B4365E6E-00DF-425E-9974-6EE1DE057319@bluepopcorn.net>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Sat, 30 Mar 2024 16:27:42 -0700
Message-ID: <CAL0qLwb9Wnv5Wv5U88S6Mu3Zod9RHx1u-0pihQ_vFE38=7jqPA@mail.gmail.com>
To: Jim Fenton <fenton@bluepopcorn.net>
Cc: "John R. Levine" <johnl@iecc.com>, dmarc@ietf.org
Content-Type: multipart/alternative; boundary="0000000000001d893d0614e91b4c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/8_PYPYeQDezFquFaTbba7Mmd2TY>
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: Sat, 30 Mar 2024 23:27:57 -0000

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.

-MSK, ART AD