[Moq] Re: Draftification

Martin Duke <martin.h.duke@gmail.com> Mon, 12 October 2026 23:48 UTC

Received: from mail-dl1-x1229.google.com (mail-dl1-x1229.google.com [IPv6:2607:f8b0:4864:20::1229]) (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 3549246 for <moq@ietf.org>; Mon, 12 Oct 2026 23:48:09 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=pass header.d=gmail.com header.s=20251104 header.b=OkOd4n3X; arc=pass ("google.com:s=arc-20260327:i=1"); spf=pass (mx.ietf.org: domain of martin.h.duke@gmail.com designates 2607:f8b0:4864:20::1229 as permitted sender) smtp.mailfrom=martin.h.duke@gmail.com; dmarc=pass (policy=none) header.from=gmail.com
Received: by mail-dl1-x1229.google.com with SMTP id a92af1059eb24-141395927feso4255421c88.0 for <moq@ietf.org>; Mon, 12 Oct 2026 16:48:09 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1791848882; cv=none; d=google.com; s=arc-20260327; b=CaLtWES/6tT3Nhu8YEbQYKRKAQ/XbAtDWsOIhCbJYRcLzYdYTvXZyqBdEWYfS9+0Sf f7TXLayjfENTpNfX3K7wyznuLTm7sb0TdYD2FJb1I6edkYl66/RQqa2NQ3Zj5PMFVsro ugG5oVBgASAtpXnRyEWRVMm98Q+u/KoGNz3zrPKDBAtJprBE2Ii4546laIjdOJ/FOzY6 aWbU6yfY8R+SeO5Pd28b8wfQssHs5hi6NEdnWk39DmGWCj/pvB0/nEsC+HCdGKzvI1o1 Uh8xzVn8e+Cs6Q0WDbswd2TuyLSbCrWQv7AGwnTrQPM7Qj2XxqIX8ORIOinXV/TxhJaV 3hmg==
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=xFZwkxK7fMgg3ALObfAWyEop6ljeK/g1D3Rn8kB2e5A=; fh=O7FHekVWbm+p1BTgemBIsNU2wj9zrV/QYc3Tp1yj5Co=; b=dKOAs8RfpARa43fNBibmTb+G5m4Y2VpHgfHmLlGREQjI7CMXyWhhJxKdi4OYPAEHme 3Cbs+1ctmqXaikhGsl3Ruij1Vcyi1Mg1MlHeSnh++Xgu2duV3a6eHDnNlkQAkq66uspb yvKjL1cd/FAg0sVqFVFR+LZsg+hzlhVV4AmagaAUVp1AtOmHA9itip543/hl/JpqRJLL Jc3KOZ8IQp106u6Ms0l21sYktsndrhVwbK2J+SshdxOT/W22t+w8ZCuXs9CWp6TGmhlh Ni5vpJ4aCmDet4xEwzbdedpCfgbF0rQUvmwc0Mt4/X17iIXTsIbj849zfkpopVPWEPHm VGXw==; 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=1791848882; x=1792453682; 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=xFZwkxK7fMgg3ALObfAWyEop6ljeK/g1D3Rn8kB2e5A=; b=OkOd4n3XVWbsa8BI64cHeRkaPVg4QGTQC9Va5KSZjDHQ1nL2q9jSvXX5SSy9hhKMF/ aK1zriw2VKXaw2y4hKI90Kq+2hbAZggvXZEXx2kn8rC0nt3K5Y86mzF2MBjW4qRBvKHu EoaUak40SQ0iN/h5QkNImFdUqjOLsnNI/LxSCPDwqcTpduqyCLs3ZGSor2EDpRkSEyT2 Z6G0/UjdMMIftN4wYTG9GHMrfMEB0xJ2kdKfT8oSYGkE0zkdjTADysVHvxFFe6ldlc8g Ks4XuAbPLkn5PRrobcQnAlZskj4y0v5uQjycvgyLTMIn+780GxZu2aqKKEzKUa7tGrR0 tR9g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20260707; t=1791848882; x=1792453682; 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=xFZwkxK7fMgg3ALObfAWyEop6ljeK/g1D3Rn8kB2e5A=; b=CWQggLopy2CjM/u2UV6N6ToiSLqHHXRiSNhJCyRMXdd5Om7C7/bsYFH8FVbc60/FhL k7vIngJr+VgvEeXE68A8rQ5g1cAAJZcY5mFeiZu/Q6B9d4++Slz7yvegaNgqOKHl3Eoh YJoyAOOFSFPW13aRv+MfvPESgQ321HtUnmjHrtv6bOQmHmRyE9MU75zrdfodHPYk4JCP 4nC/WK4fYG0KNpqfFghvTORLOAJtNmV76Py88uyd7tYupLQdeTbA6+WdRzHGiHozw2Q9 OwEc5rsybi6wBD6wi3fxy0j2yQdZON/COuNxoUdqggGuvJZunjqsjmut7OPmSEgh5c2n xf5Q==
X-Gm-Message-State: AFq9FYLxjruiH+Gtlvg51YBBEILZTwsy33zwJzDip6KM2eLW+GsZ7uzW KltISWGPCAKRF1e3es7hKkM64gpMIyCYLzpU2emByrCLEtb07DU1mc1mkJ1IUN6qQXA/3aMdPbq vrXJx7VYD3+M2587OtV5Fm6soE7ZZmog=
X-Gm-Gg: AYBFou0xRjauK/drDtrCH87QZ00ZpK79os6IReQ9M7GF2iJ7eUwYZHQu7kLzPEFQuPJ +pL1NgAfSjhj3sD6ROb9dNORGrVPp/t0AwL/dcitme7MFiAV8hmgPot2IlBDEU+n9GlIDPA0gyz zuN1ciFZ1msBW1m/ftXDAoVNzMXSOFNBg+0Vu+yCfMCsPtHcYmYkFYPMF2UEm7C8AVY210cqb0G +LRffru7k3TJNcSIvZe/zIoubRAu76qX4FCg9qMgstAOXIVAunxYMMoxHeaB5x/ptp3X9fSXZtL SbIWkTvtTlR1J8lgtmwsmdDi0h9Kg19StIvKWiHetRtBQnX19lqOqimtF8Xr8LmhAK7zpfpU/nO dl4yRTrfDbmU=
X-Received: by 2002:a05:7022:1715:b0:14f:ee48:f26a with SMTP id a92af1059eb24-16a603445c6mr15232704c88.30.1791848881863; Mon, 12 Oct 2026 16:48:01 -0700 (PDT)
MIME-Version: 1.0
References: <CAM4esxSJakJ06X80D_-keweXCKM6DTCUvuVZsAyxet98eF6dGQ@mail.gmail.com> <47F74391-1984-4F61-A131-80A339269379@iii.ca>
In-Reply-To: <47F74391-1984-4F61-A131-80A339269379@iii.ca>
From: Martin Duke <martin.h.duke@gmail.com>
Date: Mon, 12 Oct 2026 16:47:50 -0700
X-Gm-Features: AclHuK_wzaKDSbe2hpB8UJItYr_RHvnl5WLpMd6ebMfpmrMv9vlP1t5xclWCyjc
Message-ID: <CAM4esxTtPYRH8A0qMN+AAXjxU-v_K90MesgXqAZGDoNSQiLmRg@mail.gmail.com>
To: Cullen Fluffy Jennings <fluffy@iii.ca>
Content-Type: multipart/alternative; boundary="000000000000184401065dad5452"
X-Spamd-Bar: ---------------------
Message-ID-Hash: CC4FOMZCCDC7EZFN7BATF5TAQZ5ZSNCY
X-Message-ID-Hash: CC4FOMZCCDC7EZFN7BATF5TAQZ5ZSNCY
X-MailFrom: martin.h.duke@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/vfEJs2SmC4AqPLZMubJ318pFscM>
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>

Hi Cullen,

Thanks for the submission. It's a bit late for people to digest this much
text, but we'll at the very least put it in As Time Permits.

Does this really affect SWITCH_FROM, given that that is in the core draft,
not an extension? That is Alan's highest priority for this week and if it
impacts SWITCH_FROM, that's something we'll have to talk about.

On Mon, Oct 12, 2026 at 11:51 AM Cullen Fluffy Jennings <fluffy@iii.ca>
wrote:

>
> In the past I have said we would need some changes made to the current
> base transport draft to allow features like TopN and SSTS and similar to be
> expressed as extensions.
>
> To facilitate the discussion of who we should do these in the base draft,
> I had put together a PR for a framework in the base draft to support
> extensions like this. PR is at
>
> https://github.com/moq-wg/moq-transport/pull/1982/
>
> and some slides that help explain it at
>
> https://cisco.app.box.com/s/q48fxo9zeibkvonlf42uncc16m9z891j
>
> The basic idea is that the the relay would keep track of “selection sets”
> which are sets of tracks, then a subscriptions would have list of policy of
> what extensible algorithm run against the selection set to decide which
> tracks are selected or not. As tracks are selected or unselected, it
> changes if they are forwarded or not and the timing of that is unified with
> the switch from so that it do things like happen immediately or support
> thinks like the switch being aligned with group boundaries.
>
> This PR does not change how Top-N, SSTS, or Switch From work but it
> refactors them into something that fits into a common base framework that
> in the base draft that allows these to be expressed as extensions.
>
> To be clear, I think the fastest thing to do is just include Top-N, SSTS,
> or Switch From in the base framework but I think the better longer term
> solution is the refactoring of them along the lines in the above PR.
> Clearly this PR would need a bit of work to tweak some of the details but
> it is more than complete enough to fully see the shape of the solution and
> the big picture of how it works.
>
> I would like to ask for 45 minutes of agenda time on Wednesday to explain
> this and another 45 minutes to discuss the above PR and slides. I think
> resolving this issue has remained our top point of contention for many
> months now.
>
>
>
>
> > On Sep 28, 2026, at 10:25 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
>
>