[dmarc-ietf] Éric Vyncke's Block on charter-ietf-dmarc-02-00: (with BLOCK and COMMENT)
Éric Vyncke via Datatracker <noreply@ietf.org> Thu, 08 May 2025 06:14 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: dmarc@ietf.org
Delivered-To: dmarc@mail2.ietf.org
Received: from [10.244.8.181] (unknown [104.131.183.230]) by mail2.ietf.org (Postfix) with ESMTP id 0CC372639202; Wed, 7 May 2025 23:14:05 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Éric Vyncke via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 12.39.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <174668484483.1129817.13193584174823323206@dt-datatracker-58d4498dbd-6gzjf>
Date: Wed, 07 May 2025 23:14:04 -0700
Message-ID-Hash: 4YXVGREZYBRBPK44JWCNIBULMDWFLBMA
X-Message-ID-Hash: 4YXVGREZYBRBPK44JWCNIBULMDWFLBMA
X-MailFrom: noreply@ietf.org
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: dmarc-chairs@ietf.org, dmarc@ietf.org
X-Mailman-Version: 3.3.9rc6
Reply-To: Éric Vyncke <evyncke@cisco.com>
Subject: [dmarc-ietf] Éric Vyncke's Block on charter-ietf-dmarc-02-00: (with BLOCK and COMMENT)
List-Id: "Domain-based Message Authentication, Reporting, and Compliance (DMARC)" <dmarc.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/IFf1F3f5w4tFdwDJqgquWUfmCeI>
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>
Éric Vyncke has entered the following ballot position for charter-ietf-dmarc-02-00: Block When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/charter-ietf-dmarc/ ---------------------------------------------------------------------- BLOCK: ---------------------------------------------------------------------- While I can only support the goal of this draft charter, I find it too vague on some topics. 1) please provide references to `The revision to the original document, along with one of two reporting documents` 2) please also provide reference to `This closure left behind a second reporting document` (even if expired) About the reclaiming of the I-D from RFC editor, I am afraid that this will be done for something more than fixing typos, i.e., it should be sent back to the to-be-created WG with the full process of WGLC, IETF LC, IESG evaluation. Else, why re-charter this WG ? ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- I am puzzled by `base document produced by the working group includes normative references to this document`, if I understand the sentence correctly (the use of `this` is a little ambiguous), then a RFC was published with a draft as a normative reference ? Or is the 'original document' not yet published hence this WG (see my BLOCK points as it is really unclear). Also suggest to request the RFC Editor & the AD to remove the `base document` from the RFC editor queue and send it back to the WG as soon as this WG is chartered.
- [dmarc-ietf] Re: Éric Vyncke's Block on charter-i… Murray S. Kucherawy
- [dmarc-ietf] Éric Vyncke's Block on charter-ietf-… Éric Vyncke via Datatracker
- [dmarc-ietf] Re: Éric Vyncke's Block on charter-i… Eric Vyncke (evyncke)