[Masque] draft-ietf-masque-connect-udp-listen-10 early Httpdir review

Mark Nottingham via Datatracker <noreply@ietf.org> Mon, 20 October 2025 05:48 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: masque@ietf.org
Delivered-To: masque@mail2.ietf.org
Received: from [10.244.8.144] (unknown [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id 6FA66776C029; Sun, 19 Oct 2025 22:48:04 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Mark Nottingham via Datatracker <noreply@ietf.org>
To: ietf-http-wg@w3.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <176093928437.2017292.2722308511968925364@dt-datatracker-84f8f646b-tg6mn>
Date: Sun, 19 Oct 2025 22:48:04 -0700
Message-ID-Hash: G53R5IY2VFPUECEVH6WH3RBEJIEAMHST
X-Message-ID-Hash: G53R5IY2VFPUECEVH6WH3RBEJIEAMHST
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-masque-connect-udp-listen.all@ietf.org, masque@ietf.org
X-Mailman-Version: 3.3.9rc6
Reply-To: Mark Nottingham <mnot@mnot.net>
Subject: [Masque] draft-ietf-masque-connect-udp-listen-10 early Httpdir review
List-Id: Multiplexed Application Substrate over QUIC Encryption <masque.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/masque/_rULocg9koaeHmCi9CwHsz2cZts>
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>

Document: draft-ietf-masque-connect-udp-listen
Title: Proxying Bound UDP in HTTP
Reviewer: Mark Nottingham
Review result: Ready with Nits

Nits:

* Introduction: "Combined with the HTTP CONNECT method (see Section 9.3.6 of
[HTTP]), it allows proxying the majority of a Web Browser's HTTP traffic." This
is slightly confusing to readers who aren't familiar with context; suggest:
"... allows proxying HTTP/1 and HTTP/2 (which are TCP-based) and HTTP/3 (which
is UDP-based).

* Throughout, 'header' should be 'header field'