[Moq] Re: Draftification

Luke Curley <kixelated@gmail.com> Fri, 16 October 2026 03:58 UTC

Received: from mail-lf1-x12a.google.com (mail-lf1-x12a.google.com [IPv6:2a00:1450:4864:20::12a]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by mx.ietf.org (Postfix) with ESMTPS id 96AE946 for <moq@ietf.org>; Fri, 16 Oct 2026 03:58:05 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=pass header.d=gmail.com header.s=20251104 header.b=K10tRYXE; arc=pass ("google.com:s=arc-20260327:i=1"); spf=pass (mx.ietf.org: domain of kixelated@gmail.com designates 2a00:1450:4864:20::12a as permitted sender) smtp.mailfrom=kixelated@gmail.com; dmarc=pass (policy=none) header.from=gmail.com
Received: by mail-lf1-x12a.google.com with SMTP id 2adb3069b0e04-5bcb1f1358aso4167891e87.1 for <moq@ietf.org>; Thu, 15 Oct 2026 20:58:05 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1792123084; cv=none; d=google.com; s=arc-20260327; b=qsJ0uIhgYmmfHAePPMrHlCMwHVKcyvUjdH6u5IxeLuILyJME63qJcjCAVtB3yvW3Gs QbrDDSaDalHo3Wrrk+O8ZH40DZw+fP0X/Rb42sOVqoKQ0oqb47wNfXYYVeqAIvFKJ1k8 2MA9uf+KmwRrURIc1cpQdCoqX1XA1rLb9pqJ5RAe5JrPXc1rNflNGlgxwdaqGoebqhAX XfWU/e669UuNcDd8W45qenAOiMmmK5ytRZtqOf8MMeZN4CqmrM0HND943BDs8KFDmBX8 x4KqihTnLjYH20IAVclo5Mp9ZvsS6pmV5oYmGMpPyG1LiqvmVSoPWyYFqIqznObHmEH/ vI/w==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20260327; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:dkim-signature; bh=KeH9gwI0gog9ku2TUEjc5XXwWU1C8ue+RSLWfHWuj00=; fh=+C5Db+j9U66aqAj6mbj8szYOwwJKNyd6kd9PYVByptk=; b=iWa7KGifJ9P3vfoyOCChpzvgal6CzZFBOQDa5R3AQ2k07ndw1WwvAqmsqHOGciQ2hv CJhsa3JrE3/MlHn7Tjao81MXLEuegNIgrJsW0wWNXIHYQz9alCtDMvEzZPbhrzVfMCsn /EeHxb1hLiVtAfDPxjxyEQg0PFpGnjfNHt/nhLNz/zpQqID1MecmTnSKtiHxwvIVbYV0 WFvko8c84Ole1+fQzYWG/jlSUeL6JG4NqtX/UHGaLbsPjwbrAoDc/N5IvH9beuTXPdsh yYz3MUrs8tncpEZM6KoMSlTTNRjSjeXwSe+uZB7ucGqaDpIsoIEv9r4eTNpo3ILu2+ui 35tw==; darn=ietf.org
ARC-Authentication-Results: i=1; mx.google.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1792123084; x=1792727884; darn=ietf.org; h=content-type:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:from:to:cc:subject:date:message-id:reply-to :content-type; bh=KeH9gwI0gog9ku2TUEjc5XXwWU1C8ue+RSLWfHWuj00=; b=K10tRYXEIjyQG7Ef7a4EUFCcrMKZRkmh3U5kPfdVF5nmaio4MOWMZu33Wr3YW6LBfK qxcxONusH2VY9xtGjBHDP9oNvxBCH/u8vmzJIPHSg3tjT51zj0UWe0CJ/nM/rb0qDANC FtH9D5yqmqxBpBExGqIjfQkY5UaepmHikZeshVTcGsIE2IjILpFGp3xXWJYTT05XmumJ FoP4MStWGSlBVHXKzoblo1oEHfHPfPbnY1Zhgd4fkJonuT4nnAGcgpKbmP2c2vjci0/h cY7mbrkrf5dSeDaDDzyoo3Nd2JQIq+YAQtQwNhMrNhQNefsPtfy0mcG23iFQsP3xHXLf BWUg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20260707; t=1792123084; x=1792727884; h=content-type:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:x-gm-gg:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to:content-type; bh=KeH9gwI0gog9ku2TUEjc5XXwWU1C8ue+RSLWfHWuj00=; b=GWbWETDPvkjlCOKNxRMdVYzpkmJRireccd1llLTIh1IodC4x75S7f33DLFTEflbQ3W QooQw4NLXTCTHMq3DJbWzCy2Myvm//cu1nOGA0b1FMQRw8h/o2VdxLk3K050+U/NDJxK laxyCisNPFGJUM4yAp0FZVvu6vjWDxb6O6diKWT47lB73ty0LHAulpe1tAwCzEMNDm9l Z2qcKNO8ykSlRoGapYsEuW/g6L6RuYLK/mgkiIGgrROnWRx2fm1B0/V3ELO8twKx9q9V Z0VtpMnZiJ6o4+6kCTfqnslcfluRpMqftBdkE2q8RLetweueR9Atl7wTJwaHeiNx5m9g 2JeQ==
X-Gm-Message-State: AFq9FYLq+naZtJw3X3iD0Jj6j2IlxKRoa8IK4UAH2CFt3e8QNDqLNhme 4it5nSJsKE/IljutT0dsTB7rjBTEYk8fVVTxrTC7HIz0rOcPJYeJ0Q1Z+fjYh0wz4VB09x6jQ2a IPFsiCNX22iWrKa3lpVT7sOkOIzs4m3s=
X-Gm-Gg: AYBFou1Mc3Z1amf5jzG3nD4V4R2OQ/8qyP2Zg/uVk7nbVhBHhW/qmYDM8/Mor6+GOcL Kk+eb9c3N8xorhCkGtKeHTnSDKL90hLzfBXiVaRBjU7NatgMLRRjPSGn0bshPAYv0y9eaYNwi2P kwRMaHhdyUDEXSk2vqIEkOC5X11jCIG9XFBvSi56iyGOzpIHEnyItMdErsXmAmxWKhgFnr2efTb jWCKuSihiX81QfIhKaPjGD3/Da3SwQV6e6IaJ03EMMQHQY5QYxEhJnpBXbYfTDxjAxzQknbxpEK RShCw9SghH/1ATfjDz0LB13DVdDcAL5dLae3an7NKwSLTjAJi8yj9rzb1Ji3fYkKwvC8luU7kaR RsBp/VebH6Rr2vDjC7o3+ni8=
X-Received: by 2002:a05:6512:33ca:b0:5b8:fa70:741c with SMTP id 2adb3069b0e04-5bcde35804bmr7570115e87.4.1792123083826; Thu, 15 Oct 2026 20:58:03 -0700 (PDT)
MIME-Version: 1.0
References: <CAM4esxSJakJ06X80D_-keweXCKM6DTCUvuVZsAyxet98eF6dGQ@mail.gmail.com>
In-Reply-To: <CAM4esxSJakJ06X80D_-keweXCKM6DTCUvuVZsAyxet98eF6dGQ@mail.gmail.com>
From: Luke Curley <kixelated@gmail.com>
Date: Thu, 15 Oct 2026 20:57:51 -0700
X-Gm-Features: AclHuK-lk2GxCh9wLE9n9oA8yxqM8lf8gJwDXw1mASo-qSss0QPjmtNPIIJtRKk
Message-ID: <CAHVo=ZkibqCc45LA6yjTLC3WLiKDwcvCBJkShqoT0jDkh1s1Hg@mail.gmail.com>
To: Martin Duke <martin.h.duke@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000ce2930065ded2b9a"
X-Spamd-Bar: -----------------------------
Message-ID-Hash: I3SW2RW54ZGJUJKI4OZES5WOUF5NB2YC
X-Message-ID-Hash: I3SW2RW54ZGJUJKI4OZES5WOUF5NB2YC
X-MailFrom: kixelated@gmail.com
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: MOQ Mailing List <moq@ietf.org>
X-Mailman-Version: 3.3.10
Precedence: list
Subject: [Moq] Re: Draftification
List-Id: Media over QUIC <moq.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/moq/v94QTWyryebR_WUQQPrbiNQ0yjI>
List-Archive: <https://mailarchive.ietf.org/arch/browse/moq>
List-Help: <mailto:moq-request@ietf.org?subject=help>
List-Owner: <mailto:moq-owner@ietf.org>
List-Post: <mailto:moq@ietf.org>
List-Subscribe: <mailto:moq-join@ietf.org>
List-Unsubscribe: <mailto:moq-leave@ietf.org>

Both Top-N and SSTS should be separate RFCs.

Please stop holding the base draft hostage for optional features that NEED
production validation. If moq-transport is not extensible enough, this is a
perfect time for some dog fooding.

IMO the only reason to put these *optional* features in the base draft is
political. An extension functions the exact same way (SETUP parameter) and
is easier to read as a separate document, but it lacks clout.

Look, I understand that optional features in the base draft get more
adoption than extensions. And that's important for *reasons*. But please I
just want moq-transport version 1, warts and all.

We need to ship it. Experiment in production instead of having the same
arguments over and over and over again.

On Mon, Sep 28, 2026 at 9:26 AM Martin Duke <martin.h.duke@gmail.com> wrote:

> The chairs are going to initiate a consensus call about the status of
> various proposed MOQT features – should they be in a separate expansion
> draft, or should they be in the core MOQT draft? We would like to avoid
> using meeting time on this discussion, to the maximum extent possible.
>
> The features are top-N: https://github.com/moq-wg/moq-transport/pull/1830
>
> and SSTS: https://github.com/wilaw/moqt-ssts
>
> We strongly encourage you to read the proposals before participating.
>
> There are multiple possibilities for the trajectory that these proposals
> will take, so it is unlikely that any single trajectory is likely to
> achieve rough consensus. However, the working group already has rough
> consensus that it will complete the work in some form.
>
> Furthermore, we believe that everyone agrees that both features are, in
> principle, optional to implement because they are controlled by a Setup
> option that can be set to zero.
>
> For the first phase of the discussion, we would like to set aside
> short-term document processing, issue management questions, and delivery
> timelines, and think about these standards far into the future. Would
> this be better as one RFC or as multiple RFCs? Here are some
> considerations that the chairs believe you should consider:
>
>
>    -
>
>    Does inclusion in the core draft increase the probability a feature is
>    implemented, and does that matter?
>    -
>
>    Is the feature (and core MOQT) easier or harder to understand with
>    separate RFCs? Within the working group, people have asserted both
>    viewpoints.
>    -
>
>    Will the IETF have to revise the feature in the future? If the design
>    relies on some assumptions that turn out to be false, it would be easier to
>    revise the feature if it’s specified in a smaller RFC, rather than having
>    to reopen the entire MOQT RFC.
>
>
> This email does not begin any consensus call, but you are invited to read
> the proposals, file issues, and start thinking and debating these concerns.
> It would be great if people read the proposals, thought about the issues,
> and discussed their concerns on the list by the 13th of October (Tuesday of
> the Seattle meeting). In fact, interop time would be a lovely time to have
> high-bandwidth discussions. The chairs will initiate a consensus call soon
> afterwards, assuming there is adequate discussion on the list.
>
>
> Regards,
>
> Magnus and Martin
>
> _______________________________________________
> Moq mailing list -- moq@ietf.org
> To unsubscribe send an email to moq-leave@ietf.org
>