[Moq] Re: Draftification
Cullen Fluffy Jennings <fluffy@iii.ca> Mon, 12 October 2026 18:51 UTC
Received: from fhigh-a8-smtp.messagingengine.com (fhigh-a8-smtp.messagingengine.com [103.168.172.159]) (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 E789646 for <moq@ietf.org>; Mon, 12 Oct 2026 18:51:52 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=pass header.d=iii.ca header.s=fm1 header.b=MeDbZWSD; dkim=pass header.d=messagingengine.com header.s=fm2 header.b="A mwBTmq"; spf=pass (mx.ietf.org: domain of fluffy@iii.ca designates 103.168.172.159 as permitted sender) smtp.mailfrom=fluffy@iii.ca; dmarc=pass (policy=none) header.from=iii.ca
Received: from phl-compute-05.internal (phl-compute-05.internal [10.202.2.45]) by mailfhigh.phl.internal (Postfix) with ESMTP id 03ED0140004D for <moq@ietf.org>; Mon, 12 Oct 2026 14:51:46 -0400 (EDT)
Received: from phl-frontend-04 ([10.202.2.163]) by phl-compute-05.internal (MEProxy); Mon, 12 Oct 2026 14:51:46 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iii.ca; h=cc:cc :content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm1; t=1791831105; x=1791917505; bh=TyqPxcaUddU+v7zw1czRK0nvysXQpZf+qWIIB+GNBOI=; b= MeDbZWSDvzAI6l19eGyj6kD90gaM4gi3GaJzNi5V00oyYpJM+s0oqCGnXxwn7Qrv fkD7H3v60nQym3d8d3gFutBw4uTZaq1ugKuyrfM/OzQ3LhoRGkjc3zmR67ibbVCR WRvyQw0kzrA//kyf1mrp8X1hWjNRiAEYQciSy6rebTcy9DLwu6+OMZP30vTfd/LH 684LQcKXS4zYszO/hmaa/+tFRL+3TNLuA4gaygh/ELIyMnL5QnQTYybs47g2AzXI /q+4r0wLntCyq5D+iGjB79bhF5IYtpy+I37bJlUFStKcHAWuDRWsRWVm2wD70BsM ux65rFgYPblXT3vE/+wWVQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1791831105; x= 1791917505; bh=TyqPxcaUddU+v7zw1czRK0nvysXQpZf+qWIIB+GNBOI=; b=A mwBTmqbsNjdRk7mWZ8AowZjl+aAw5Fz8Fcx3O8KfyyCgDZqZNr99qNPC7AXrBpZu Dyhj5NQetZXT7BJIuuCNVoJpa/zfZoj5MrHuASyF2S3ar/K5zSB4Rl+n4E1AeTA0 4eE7F1iOyATqGccaFbNFtMy55ehT7rnknaTgz0/sccOCo74Yb3wKMj2pLQfAPnnY 0QPfjwDcqY2zXrTzzQS9R6iqjjZtR0USJIXyM0/OvzmfjRq9Sv7JwbeajJZJnSnP aXTswjs7JpwUdX3ANI/BGZ/M70zrCvG/GLnOijlV0jbHFE/7YSadrnGhkD6Gt71m pwQw7nZxz/OkLuzcRbHBA==
X-DKIM2-Info: draft=ietf-dkim-dkim2-spec-06; repo=github.com/dkim2wg/interop; date=2026-10-04; sw=lmtpprox; action=sign d=iii.ca a=rsa-sha256;
DKIM2-Signature: i=1; m=1; t=1791831105; d=iii.ca; mf=PGZsdWZmeUBpaWkuY2E+; rt=PG1vcUBpZXRmLm9yZz4=; s=fm1:rsa-sha256:ZQ57RPRIw11sKLkbkcJ14Zg8mZs11unrLzrqAGcjVQra/rd xTnljlT71pbIZMJNo3fXiykgY4f3bApJmT9lVTs+LIH3kWX9HBX124WLEx0Sy0zt A68twoyd2M/f0VG8HKcixjmEfNuGmXLZk4P+QWb58+9dE85wjdxB1Cdi5c6RSXvN N1F/JtWmZTLGpaFMwP6rroDENtYtT7cJA0XPJ40kGJJLJDVQfTz0lTFswOns1asy kvItgqSIcUjMreZg/NNvnuerMXeAVrUj9g323aCGb3X/y64Dfvqd/cvOv1A50gVc 8wMXO/p9HPibTwt0CNK/1nlPsUGZmCH3DcM/u5Q==;
X-DKIM2-Info: draft=ietf-dkim-dkim2-spec-06; repo=github.com/dkim2wg/interop; date=2026-10-04; sw=lmtpprox; action=mi-m=1; hc=12; hn=cc,content-transfer-encoding,content-type,date,feedback-id, from,in-reply-to,message-id,mime-version,references,subject,to;
Message-Instance: m=1; h=sha256:aViO02B+PLiBz02uWl7zN5Ri3HQ2XTgiV8GuHZ4MCaY=:yVtDJma/AZ4WP2SIKY/45s0+IIii/jgyL+4Kos4KuxU=;
X-ME-Sender: <xms:QSzNalPoETJ13S9RKUKNk9kGe2-BbCXuLcYrDg2qJ9wdJi-t4Rg80g> <xme:QSzNahkwc2qEZIiy9GjzaWkz_daM7eBlPueKyFTeTIK39O6qm1pjekEW-PlM1DzCa 42F6r8MrcPExtg3jN8aSugcmoAMQykHgDFWkELGEnbW7dkm5U56BcLVVQ>
X-ME-Received: <xmr:QSzNakToH4exgr8BrHzycTyvbtHOdj_vgf-hr_Co95jeENBFc8aHvlf_royWB_k8_qqkaQsMmH-MIDgE9cE5VfuTFDGc_mUPbFEvMxY>
X-ME-Proxy-Cause: dmFkZTFLgM9nzgHC+VKRXZLQYt1l2fdL8eUuzs4nlKGbBJgwwoyU3WsO35jUsCpCJNpAu5 8aSKO+cD0orBUBol5ITji8KNz6x36H7yc41q0z+g8m+mmrQmPoCPounjbTwE1CJLMtAHJc xeBALtLbKQU/W1wBc9c1lLESshYVMYgdjfE/svt70CP+QD/UOWFDzbSpbTn0RiYJE50gwp 5w3Brq3itAIFmQqDfhooqNd1bSajMGE0kb/XEfg8B9z0HBTF9WIkne1tdp2GNGzpvIdiSA oef3FM51w1ue9TmUe20mOQfNlUmGePsA8I90nXrzM8KjXYzDEnWF8wTN9DJjvvRQ8qpAaW A7cJwSQFUVkacZjZA5OVLsOd5dQykmK+BXwRx4S5ccAEU/qWNxHRDElTObXDwTG7tg6Jht 3P6pSlZ8dRklgS6bIuTL9QMfxyJikhcFExJMdXS9+oRvVXj3KHQSHklPnEpcnwX2n6XXQy CW4Q8GapUKTVflB7QIamPh8OSl8wG47tCYaXg9glpdzNtVsH4UxeB5kACpSDankFb+t1FK 7oOBdbeaxNGMz1IZjUoBpq2Si2jhLWWAhDQIJLuR1SLKuwgeym78vqb63iyoMRHcXeH6f3 ZFLmWieGebky6D00zWOVQrPlxSF3M6Bg1ehk8PmP/v/NLl3qMOeK7QdrSMMg
X-ME-Proxy: <xmx:QSzNalAFcX6duDE3-rGxlapMp0hq36OPMaSgemRk-3DgaywLsPnDSg> <xmx:QSzNarSmb4_oKP7N2d3KyK9jPV7in0GOdyOHHZ1mcFPmO1FnNrFUpw> <xmx:QSzNajouoZIjswTn64wACSal-dj7QIWfkTl5dcNrO6xdjdv6DvF9fg> <xmx:QSzNatxLMjIdBzNYYzTpZPzIZVtoVgxgbS2dMyuK018lyMuoZeDShg> <xmx:QSzNakrmu0ljs9qUAOmQdlVefBrLb4c9NIeb-gXJevX9SRb0yMQHUHuH>
Feedback-ID: icafe48a4:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 12 Oct 2026 14:51:45 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.700.51.1.3\))
From: Cullen Fluffy Jennings <fluffy@iii.ca>
In-Reply-To: <CAM4esxSJakJ06X80D_-keweXCKM6DTCUvuVZsAyxet98eF6dGQ@mail.gmail.com>
Date: Mon, 12 Oct 2026 12:51:44 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <47F74391-1984-4F61-A131-80A339269379@iii.ca>
References: <CAM4esxSJakJ06X80D_-keweXCKM6DTCUvuVZsAyxet98eF6dGQ@mail.gmail.com>
To: MOQ Mailing List <moq@ietf.org>
X-Mailer: Apple Mail (2.3864.700.51.1.3)
X-Spamd-Bar: ---------------------------
Message-ID-Hash: V5XHGZFYKLYHH6MFBDJDNUDS2PU4H3GW
X-Message-ID-Hash: V5XHGZFYKLYHH6MFBDJDNUDS2PU4H3GW
X-MailFrom: fluffy@iii.ca
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: Martin Duke <martin.h.duke@gmail.com>
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/C2AepB0G2GL6hdhb_dXKbH-eZa4>
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>
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
- [Moq] Draftification Martin Duke
- [Moq] Re: Draftification Mo Zanaty (mzanaty)
- [Moq] Re: Draftification Mo Zanaty (mzanaty)
- [Moq] Re: Draftification Magnus Westerlund
- [Moq] Re: Draftification Cullen Fluffy Jennings
- [Moq] Re: Draftification Martin Duke
- [Moq] Re: Draftification Suhas Nandakumar
- [Moq] Re: Draftification Michal Hošna
- [Moq] Re: Draftification Ali C. Begen
- [Moq] Re: Draftification Mo Zanaty (mzanaty)
- [Moq] Re: Draftification Alan Frindell
- [Moq] Re: Draftification Ian Swett
- [Moq] Re: Draftification Suhas Nandakumar
- [Moq] Re: Draftification Luke Curley
- [Moq] Re: Draftification Gwendal Simon
- [Moq] Re: Draftification Victor Vasiliev
- [Moq] Re: Draftification Suhas Nandakumar