[dmarc-ietf] Re: Mohamed Boucadair's No Objection on charter-ietf-dmarc-02-00: (with COMMENT)

"Murray S. Kucherawy" <superuser@gmail.com> Fri, 02 May 2025 17:00 UTC

Return-Path: <superuser@gmail.com>
X-Original-To: dmarc@mail2.ietf.org
Delivered-To: dmarc@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 813C1242E332; Fri, 2 May 2025 10:00:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1IYduIyUA0nc; Fri, 2 May 2025 10:00:51 -0700 (PDT)
Received: from mail-ej1-x632.google.com (mail-ej1-x632.google.com [IPv6:2a00:1450:4864:20::632]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 18ACD242E32B; Fri, 2 May 2025 10:00:51 -0700 (PDT)
Received: by mail-ej1-x632.google.com with SMTP id a640c23a62f3a-ac2ab99e16eso471052566b.0; Fri, 02 May 2025 10:00:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1746205250; x=1746810050; 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=LqZdwqVtatyEmM6CkjoiAt4G0KvmPO5MY6V/LOU1GfI=; b=V5iRvzX+zpz/aUw7LuS1ct5/RGd8f7uWY7mtNBXlpbE/XnvySMr2HbsiI0FIChBJh7 kJl2Cygslnxh8aWR0btsVbtmIFHAJ25V2BIyqTu8PzBlqXUOMYHXJq8CMcfvvpvEcU7W jHXPtsH+l6PXBz5gcEAOJj7qX2kxwnnpDemjPnMa4pjKdUYLQnpanNU6+UEZLjAdzTBZ LGMK0FxhZja16VdmjDKhEUEvy6GQ4dVYUcxzL6VC0b3fbjyD71I9JT4vYiJ+6QEZCAVv jP9ZRwA+MoSp3x5GgmE/saVTaUknZRVKOKzU5DqBAMwZhLoQhOxrDw8TT37so+tnwxGh jeCw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1746205250; x=1746810050; 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=LqZdwqVtatyEmM6CkjoiAt4G0KvmPO5MY6V/LOU1GfI=; b=faNOWRDk/yZoCCBzIvreX/n2YLI7pMVXUKPK6U0GKFvALZ+rtTOYQpSdY03oA/a10y zFFoPSqG+1XR56dhIxgaqN5nORj1wGLNjAjb4bchffqqBCYq8L/NmJchpOQs1wAaF0vM 7Bv6HzDxOBuu3ZMLah3xoqrKoFM4rkHMGT6hB3gWO8L6XhCMRZ4OCMaTczcuRpCPCcsB sQjKHngNVdJA3NpRe/EQTH656lqONi+7OiHhw4xPOkcQmc88HVE4eX88skQcP8O153Zl kQdN6Sf13tlbVI1FEKzrNmUnGReoBlI2zmIRMFnTooMGGpbmMnNstFfj/mWdCWXgR/Pt 7CwQ==
X-Forwarded-Encrypted: i=1; AJvYcCUi5MoiRGKS2qUVFV394X/4gmzYe+O2KAoWHKe9E75b5z7oOFOSlG4NmISsqeqMNm4AvQ5l2g86ttPtFyI=@ietf.org, AJvYcCX6zUzUpNBXTkMqW8ysV4uchQDhYR4eOG3kj3TBhjL3ymdi2Hk5iC76EfFY2r85e75Uq2lXfDY=@ietf.org
X-Gm-Message-State: AOJu0YyEiN9dPQGd3ax2g0GC3WOVga2y5YVVTGfIb3Ls0s4NPSZGpbnM uPJhXf+mVEzrT+Bi4gQ+ruvkYXViGrLtGigc4UCgbRw/2pwD/BL5fJinVveqAFTby+XqWXs44xr t5nBXFNAcwz08c3H9pCOMzIkYnWQIaQBV
X-Gm-Gg: ASbGncuZrVrXweeXFH3w2ZswsIkA0vWpnU2gUMvqnaViJbQJDGFFNrazpUHt6u21r6q Vxi/IUdPtIVfC2cHgWRIWGGkFxQ24uGyRQ/bYYcLh0p2LNBSjSe2cB6i2o5ulq3t7BxoFc8P2DU 27KR5X8OYLZn2NZ8cpEjYh9ymoHJZwo9oV
X-Google-Smtp-Source: AGHT+IG2Ao00o2DxGYCUmh9J4TIhGPQ06gZnv/+qKpM8NwBCfhJrxh2W5LuASvE98QTR8qWjPBpuuYTKuyKP811ys58=
X-Received: by 2002:a17:907:97c2:b0:acb:85da:8e09 with SMTP id a640c23a62f3a-ad17ad9cdb7mr355719166b.21.1746205249728; Fri, 02 May 2025 10:00:49 -0700 (PDT)
MIME-Version: 1.0
References: <174591740375.303.3626591694847489@dt-datatracker-9c7687889-5mqnr>
In-Reply-To: <174591740375.303.3626591694847489@dt-datatracker-9c7687889-5mqnr>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Fri, 02 May 2025 10:00:37 -0700
X-Gm-Features: ATxdqUEzl5ME7sqrON4KMnSeq4wXLge2VSpwsz0oLqiAgIxDaR5-Nc0_cBYInBg
Message-ID: <CAL0qLwb_W0d6_63rRcJrdZhkZfNAHmCRiRa+CMGONXYnoT6EQQ@mail.gmail.com>
To: Mohamed Boucadair <mohamed.boucadair@orange.com>
Content-Type: multipart/alternative; boundary="0000000000009d776f06342a1799"
Message-ID-Hash: KF6NULV5YFES7TJQKW6XJIBBNRMBZZLK
X-Message-ID-Hash: KF6NULV5YFES7TJQKW6XJIBBNRMBZZLK
X-MailFrom: superuser@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-dmarc.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: The IESG <iesg@ietf.org>, dmarc-chairs@ietf.org, IETF DMARC WG <dmarc@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [dmarc-ietf] Re: Mohamed Boucadair's No Objection on charter-ietf-dmarc-02-00: (with COMMENT)
List-Id: "Domain-based Message Authentication, Reporting, and Compliance (DMARC)" <dmarc.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/3WkYaP8fRIsUYtmoFVsN7epD3G8>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Owner: <mailto:dmarc-owner@ietf.org>
List-Post: <mailto:dmarc@ietf.org>
List-Subscribe: <mailto:dmarc-join@ietf.org>
List-Unsubscribe: <mailto:dmarc-leave@ietf.org>

Howdy.

On Tue, Apr 29, 2025 at 2:03 AM Mohamed Boucadair via Datatracker <
noreply@ietf.org> wrote:

> # I guess this will be deleted from the version to be sent for external
> review:
>
> CURRENT:
>   DMARC Charter [DRAFT]
>

I mean, it is still a draft during the review. :-)


> # Not sure which "consensus" we are talking about here. I think that we can
> simply delete this sentence:
>
> CURRENT:
>    There now appears to be consensus to recharter
>    in order to “un-abandon” the dangling document and complete the work.
>

I was referring to the consensus of the DMARC WG (which doesn't actually
exist, but it's still possible to take a read of that community, and that's
where the discussion happened).


> # An instance of a WG: what does that mean?
>
> CURRENT:
>   This instance of the DMARC working group
>

The first instance was the chartering in 2014 and termination in 2025.  On
completion of this chartering, the WG would be in its second instance.

DKIM, for example, is presently on its third instance.


> # Business as usual
>
> CURRENT:
>   The responsible Area
>   Director will have discretion regarding whether a full Last Call and
>   IESG loop is needed to review those limited modifications.
>
> Not sure we need to have in this in the charter. "normal" process will be
> followed for these matters, IMO.
>

You're right that this is business-as-usual, but for people not fully
versed in this sort of esoterica, I thought it would be helpful to include.


> # Should we include a formal milestone for this check?
>
> CURRENT:
>   If it fails to meet this deadline or reaches consensus to cease work
>   on the document, it will abandon that objective and instead begin the
>   work of removing all references from the base document to the failure
>   reporting document, and the latter will be permanently abandoned.
>

A "decide" milestone?  I guess we could.  Usually milestones are used to
indicate a specific bit of document progress, but there's no rule saying we
can't have one that says "if we get here and we're stuck, we will then
follow this specific path".

-MSK