[dispatch] Re: IETF WG state changed for draft-ietf-dispatch-mime-protobuf

"Murray S. Kucherawy" <superuser@gmail.com> Tue, 08 July 2025 14:58 UTC

Return-Path: <superuser@gmail.com>
X-Original-To: dispatch@mail2.ietf.org
Delivered-To: dispatch@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id CE812415F21D for <dispatch@mail2.ietf.org>; Tue, 8 Jul 2025 07:58:11 -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 Yh9CpLkfW0re for <dispatch@mail2.ietf.org>; Tue, 8 Jul 2025 07:58:11 -0700 (PDT)
Received: from mail-ej1-x62a.google.com (mail-ej1-x62a.google.com [IPv6:2a00:1450:4864:20::62a]) (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 6948B415F216 for <dispatch@ietf.org>; Tue, 8 Jul 2025 07:58:11 -0700 (PDT)
Received: by mail-ej1-x62a.google.com with SMTP id a640c23a62f3a-ae0a0cd709bso1127155466b.0 for <dispatch@ietf.org>; Tue, 08 Jul 2025 07:58:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1751986690; x=1752591490; 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=6xt+IHHfkKdpyZB5Ret+y7jw0SLdx4IIQpbsSbZWUHw=; b=Mn4n0l1fIW2DDSNPLNmiEm1Rn1V9nQrEchRHLEMlVEcWmolhrdK1xQ+I48mSFxtepR FwMiL7jAIiU5FCukJrlSSgFGSQJSQtUK6uXgShPm8rbRs563aE+Q/MZ9nNFBrGoE4NLk S3lJAVl9YmY2IDM58HxTu0uc8ZUcDBGSu+CNQaIbHPPbRWJ54aDMNPQoIps8D7ZsFzAL Vl8B0Php+RHYQqm9h8ep4yl9Kv/k2gfkVRlIW+eda4vspifIau7yhB/bWhdQ65oL5i+R 7ZF2CemAUK43oW+c1BbGK04Oo4jfnziRTlyOunAHedjnEoHiYS80H4rBHZ6K9h0JHDrf yFdQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1751986690; x=1752591490; 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=6xt+IHHfkKdpyZB5Ret+y7jw0SLdx4IIQpbsSbZWUHw=; b=bggaLkh0l5mC36Y3TVjk4BVcyCgWnCkZ5B1lHBs2lZsBTMwJc8ivLXVZdVQqIS3ftG HJ3EhFD6O80dXSvvKK3iA8Ry2w1eYKGyYsQi/Cr1A4QgJjf4tApETDIfkmteT282RpD+ /0vGWKAYtnqlF7cTmyfwkeTyJzJnarRXmEyf0IPgDd1ftzJRYE5rF1gw3aUfNNHEszf/ rEdlRqIeFcAg6p0/1sVuOHXu/VaXAsmT0RsMFgarp8S2RqgTqXXqQy1cljEJdIKt2gQR McAQwOhaO8mV5NZCaddtjClnbMcU8LhG7xBK4JYb8T2Y5U5THlU1APencld0XYVirW31 ULpQ==
X-Forwarded-Encrypted: i=1; AJvYcCUyr8pLuKN3NZxf29qOK1XKIXDsqA1MrGpFKrl/IntHayGMgrG2OxVkSfnXHqquozZDFyB7GOo+uQ==@ietf.org
X-Gm-Message-State: AOJu0Yxtfd/eNpdE3bzjplxoCl9kMeUxxYmltm/mJ9hoZZ/mxVr2uvkl eMbos0N/YoEDNfVzMmP4yw8V4k52wi+z+RIIBD2lkj8pAOPmFgSxsS8gEQBFNuEnZdiFB3DSyet LaB533HOEvJRVK5RpwOvLv3WzQdE2S8tW3g==
X-Gm-Gg: ASbGnctLiDTH4YnG+qU2GakNYCv40GhvYvd8/PpV7muntltVEytUhR7EseVeLWaDjSg 7ntb0T3TTBRkMZQA8t3rDnDjmeYC5bbF3ufCKIY/ECJsCr42/y2Z5R3BLwhm6YdeXOiSaeYX88q sVjLjXxmampkMuKGqx4P8alRPGifFHlg1Vvt2nZN1V7h8=
X-Google-Smtp-Source: AGHT+IGuC67Ncs3FNw251QdAf14aXI28jheqYBqTIYTOn1MGdxgiNDXID2q1wm7oVXVq7cZNxvonjy49i+zKsKDTXB0=
X-Received: by 2002:a17:907:7e63:b0:ae3:b22c:2ee9 with SMTP id a640c23a62f3a-ae6b2406acbmr321534866b.12.1751986690258; Tue, 08 Jul 2025 07:58:10 -0700 (PDT)
MIME-Version: 1.0
References: <F9C3585F-AF98-42E1-A7DA-24B9AC1DA0B1@bluepopcorn.net> <CAHBU6ivs7ucNLqqe5dkNM2J5R11YAV20jYc45fFhFsv4rT6sLw@mail.gmail.com> <2FBD5774EDA06F83FE75AC02@PSB>
In-Reply-To: <2FBD5774EDA06F83FE75AC02@PSB>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Tue, 08 Jul 2025 07:57:58 -0700
X-Gm-Features: Ac12FXz_38AymcF_JMfiesGpTvfxpZMylIRwKkKJidgB1Ez-E0fThrwt-BOAAJg
Message-ID: <CAL0qLwan85quE8nh9ZdG=e=RSZWe-vAeNFYJF-EcAdsE9G4ovw@mail.gmail.com>
To: John C Klensin <john-ietf@jck.com>
Content-Type: multipart/alternative; boundary="00000000000052fdf006396c3099"
Message-ID-Hash: GKFTCYTC2O2FEWZXIPF2MAPGCATJ5A6Y
X-Message-ID-Hash: GKFTCYTC2O2FEWZXIPF2MAPGCATJ5A6Y
X-MailFrom: superuser@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-dispatch.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: dispatch@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [dispatch] Re: IETF WG state changed for draft-ietf-dispatch-mime-protobuf
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/60moE9NYq4ZHArUD43_lhZIgj40>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Owner: <mailto:dispatch-owner@ietf.org>
List-Post: <mailto:dispatch@ietf.org>
List-Subscribe: <mailto:dispatch-join@ietf.org>
List-Unsubscribe: <mailto:dispatch-leave@ietf.org>

On Mon, Jul 7, 2025 at 3:52 PM John C Klensin <john-ietf@jck.com> wrote:

> Agree with Tim.
> [...]
>

I've asked my co-authors to comment on Tim's feedback.


> (1) I can see nothing in the DISPATCH charter, much less its history,
> that allows it to assign a document to itself for processing into an
> RFC.  In this particular case, the Abstract says that the document
> registers media types.   We already have a WG, mediaman, which can
> consider new registration procedures and media types (although the
> latter for specific cases would be marginal given its charter).
> Processing registrations in this fashion by DISPATCH would, in any
> event, be inconsistent with both RFC 6838 and the proposed
> draft-ietf-mediaman-6838bis.  This objection should probably have
> been raised in April on the grounds that Media Type registrations are
> not "simple administrative documents" -- if they were, we would not
> need RFC 6838, much less a WG chartered for the purpose of updating
> it.  Even at this late date, I hope the DISPATCH Chairs will consider
> that issue carefully rather than requiring an appeal.
>

I think that this is exactly the sort of case for which the "simple
administrative documents" wording was added to the charter.  This is simply
an IANA registration action that requires an IETF stream document, and the
ADs weren't up for sponsoring it.  There's no protocol work being developed
here, just the wording for a registration.  It's too small a task to
warrant spinning up a working group.  That charter wording was meant to
catch situations exactly like this.

I'm confused by the claim that this is ripe for handling my MEDIAMAN, which
is tasked with reviewing and updating media type registration procedures,
but is not intended to be a general venue for doing any actual
registrations.  I'm also unclear on how RFC 6838 precludes processing of
registrations in this manner.


> (2) Someone should explain, to the DISPATCH WG and the datatracker,
> the relationship between this document
> (draft-ietf-dispatch-mime-protobuf) and the apparently (at least
> substantially) identical draft-intarea-dispatch-mime-protobuf-00.
> My guess is that draft-intarea-dispatch-mime-protobuf-00 replaced
> draft-murray-dispatch-mime-protobuf and was, in turn, replaced by
> this draft, but that is not what the datatracker pages say.
>

That was simply a submission/naming error.  I'd forgotten that it even
happened.  I'll get an AD to update the metadata.

-MSK