[Masque] Charles Eckel's Block on charter-ietf-masque-03-01: (with BLOCK)

Charles Eckel via Datatracker <noreply@ietf.org> Thu, 24 September 2026 13:28 UTC

Received: by mx.ietf.org (Postfix) id 3674530; Thu, 24 Sep 2026 13:28:35 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ietf.org; s=mail; t=1790256515; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=eEt+JU95mUL9dqSfcB2C+47Zv6yXfne90oTzogdYKfc=; b=JWDcnd1gDJ20zh679jbKLleRtlrVDaK7RxMQ71cGaeLTXR6aj86U6bskMCDRKBlA1vQdGe 2roBr+1rknQHZJ4tKKvAmehV303YC4boiAqLfQa4B9QZjxLeY3zcpJ+HUjigMefZVCwmWT fg8VZvP7rfPKK8M1QtxjobiOyugb3+Q=
Authentication-Results: ORIGINATING; auth=pass smtp.auth=mail2@ietf.org smtp.mailfrom=noreply@ietf.org
Received: from [10.244.9.157] (gaia.k8s.ietf.org [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id EC040139C2473; Thu, 24 Sep 2026 06:28:34 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Charles Eckel via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 12.77.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <179025651486.305083.1975598636683585568@dt-datatracker-69f6c78549-jvtvd>
Date: Thu, 24 Sep 2026 06:28:34 -0700
Message-ID-Hash: DLHC5J5XEYJFI2WG5H5O4M4J2AXKNQX5
X-Message-ID-Hash: DLHC5J5XEYJFI2WG5H5O4M4J2AXKNQX5
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: masque-chairs@ietf.org, masque@ietf.org
X-Mailman-Version: 3.3.10
Reply-To: Charles Eckel <eckelcu@cisco.com>
Subject: [Masque] Charles Eckel's Block on charter-ietf-masque-03-01: (with BLOCK)
List-Id: Multiplexed Application Substrate over QUIC Encryption <masque.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/masque/9tn2CbOu1x6pGSs96jf_OieI9J0>
List-Archive: <https://mailarchive.ietf.org/arch/browse/masque>
List-Help: <mailto:masque-request@ietf.org?subject=help>
List-Owner: <mailto:masque-owner@ietf.org>
List-Post: <mailto:masque@ietf.org>
List-Subscribe: <mailto:masque-join@ietf.org>
List-Unsubscribe: <mailto:masque-leave@ietf.org>

Charles Eckel has entered the following ballot position for
charter-ietf-masque-03-01: 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-masque/



----------------------------------------------------------------------
BLOCK:
----------------------------------------------------------------------

I have similar concerns to those raised by Mahesh and Med.

1) The following text does not seem appropriate given what comes after it:

"Having delivered this core functionality, the working group will now complete
its remaining adopted work and close."

2) Next, the proposed text calls for completion of two of the adopted working
group documents, but omits the other two. What happens to
draft-ietf-masque-quic-proxy and draft-ietf-masque-connect-ip-dns?

3) The proposed text then goes on to say the following:

"It may also adopt an informational document describing the MASQUE architecture
and a standards-track document defining qlog events for the MASQUE protocols.
The working group will not adopt any work beyond what is listed."

This contradicts the statement in (1).