[DNSOP] Éric Vyncke's Abstain on charter-ietf-dnsop-04-03: (with COMMENT)

Éric Vyncke via Datatracker <noreply@ietf.org> Mon, 21 July 2025 10:14 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: dnsop@ietf.org
Delivered-To: dnsop@mail2.ietf.org
Received: from [10.244.4.63] (unknown [104.131.183.230]) by mail2.ietf.org (Postfix) with ESMTP id 2B78F4746D5B; Mon, 21 Jul 2025 03:14:07 -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.43.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <175309284702.1658500.16442938187879714340@dt-datatracker-7ff4b97469-cdtd8>
Date: Mon, 21 Jul 2025 03:14:07 -0700
Message-ID-Hash: 7D4O5T7LAJCM7OZF5ITJAWQAYWFRVXQG
X-Message-ID-Hash: 7D4O5T7LAJCM7OZF5ITJAWQAYWFRVXQG
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-dnsop.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: dnsop-chairs@ietf.org, dnsop@ietf.org
X-Mailman-Version: 3.3.9rc6
Reply-To: Éric Vyncke <evyncke@cisco.com>
Subject: [DNSOP] Éric Vyncke's Abstain on charter-ietf-dnsop-04-03: (with COMMENT)
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/NEuQ3OlX_nhfItoGhkoAl8TuSl8>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Owner: <mailto:dnsop-owner@ietf.org>
List-Post: <mailto:dnsop@ietf.org>
List-Subscribe: <mailto:dnsop-join@ietf.org>
List-Unsubscribe: <mailto:dnsop-leave@ietf.org>

Éric Vyncke has entered the following ballot position for
charter-ietf-dnsop-04-03: Abstain

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-dnsop/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Changing my ballot from BLOCK to ABSTAIN as I do not want to block the
re-chartering on a small (albeit important) point, see below a non-addressed
BLOCK point. My previous other BLOCK point about the WG scope being vague has
been addressed.

Previous BLOCK point `As a WG charter needs to be well scoped, please add the
intended publication status for all work items, e.g., standard track for
protocol extensions and informational (or BCP) for operational guidance.`