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>

--000000000000ce2930065ded2b9a
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

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=E2=80=AFAM Martin Duke <martin.h.duke@gmail.co=
m> wrote:

> The chairs are going to initiate a consensus call about the status of
> various proposed MOQT features =E2=80=93 should they be in a separate exp=
ansion
> 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 easi=
er to
>    revise the feature if it=E2=80=99s 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 concern=
s.
> 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 hav=
e
> high-bandwidth discussions. The chairs will initiate a consensus call soo=
n
> 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
>

--000000000000ce2930065ded2b9a
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Both Top-N and SSTS should be separate=C2=A0RFCs.<div><br>=
</div><div>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.</div><div><br></div><div>IMO=
 the only reason to put these <b>optional</b> 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.=C2=A0</div><=
div><br></div><div>Look, I understand that optional features in the base dr=
aft get more adoption than extensions. And that&#39;s important for <i>reas=
ons</i>.=C2=A0<span style=3D"background-color:transparent">But p</span><spa=
n style=3D"background-color:transparent">lease I just want moq-transport ve=
rsion 1, warts and all.=C2=A0</span></div><div><span style=3D"background-co=
lor:transparent"><br></span></div><div><span style=3D"background-color:tran=
sparent">We need to ship it. Experiment in production instead of having the=
 same arguments over and over and over again.</span></div></div><br><div cl=
ass=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Sep 28, 2=
026 at 9:26=E2=80=AFAM Martin Duke &lt;<a href=3D"mailto:martin.h.duke@gmai=
l.com" target=3D"_blank">martin.h.duke@gmail.com</a>&gt; wrote:<br></div><b=
lockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-le=
ft:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><span id=
=3D"m_-8543071524978851542m_4707918181686145004gmail-docs-internal-guid-962=
afc92-7fff-6e47-75d9-a71241401b11"><p dir=3D"ltr" style=3D"line-height:1.38=
;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-famil=
y:Arial,sans-serif;color:rgb(0,0,0);background-color:transparent;font-varia=
nt:normal;vertical-align:baseline;white-space:pre-wrap">The chairs are goin=
g to initiate a consensus call about the status of various proposed MOQT fe=
atures =E2=80=93 should they be in a separate expansion draft, or should th=
ey be in the core MOQT draft? We would like to avoid using meeting time on =
this discussion, to the maximum extent possible.</span></p><br><p dir=3D"lt=
r" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style=
=3D"font-size:11pt;font-family:Arial,sans-serif;color:rgb(0,0,0);background=
-color:transparent;font-variant:normal;vertical-align:baseline;white-space:=
pre-wrap">The features are top-N: </span><a href=3D"https://github.com/moq-=
wg/moq-transport/pull/1830" style=3D"text-decoration:none" target=3D"_blank=
"><span style=3D"font-size:11pt;font-family:Arial,sans-serif;background-col=
or:transparent;font-variant:normal;text-decoration:underline;vertical-align=
:baseline;white-space:pre-wrap">https://github.com/moq-wg/moq-transport/pul=
l/1830</span></a></p><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0p=
t;margin-bottom:0pt"><span style=3D"font-size:11pt;font-family:Arial,sans-s=
erif;color:rgb(0,0,0);background-color:transparent;font-variant:normal;vert=
ical-align:baseline;white-space:pre-wrap">and SSTS: </span><a href=3D"https=
://github.com/wilaw/moqt-ssts" style=3D"text-decoration:none" target=3D"_bl=
ank"><span style=3D"font-size:11pt;font-family:Arial,sans-serif;background-=
color:transparent;font-variant:normal;text-decoration:underline;vertical-al=
ign:baseline;white-space:pre-wrap">https://github.com/wilaw/moqt-ssts</span=
></a></p><br><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin=
-bottom:0pt"><span style=3D"font-size:11pt;font-family:Arial,sans-serif;col=
or:rgb(0,0,0);background-color:transparent;font-variant:normal;vertical-ali=
gn:baseline;white-space:pre-wrap">We strongly encourage you to read the pro=
posals before participating.</span></p><br><p dir=3D"ltr" style=3D"line-hei=
ght:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;fo=
nt-family:Arial,sans-serif;color:rgb(0,0,0);background-color:transparent;fo=
nt-variant:normal;vertical-align:baseline;white-space:pre-wrap">There are m=
ultiple possibilities for the trajectory that these proposals will take, so=
 it is unlikely that any single trajectory is likely to achieve rough conse=
nsus. However, </span><span style=3D"font-size:11pt;font-family:Arial,sans-=
serif;color:rgb(0,0,0);background-color:transparent;font-weight:700;font-va=
riant:normal;vertical-align:baseline;white-space:pre-wrap">the working grou=
p already has rough consensus that it will complete the work in some form.<=
/span></p><br><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margi=
n-bottom:0pt"><span style=3D"font-size:11pt;font-family:Arial,sans-serif;co=
lor:rgb(0,0,0);background-color:transparent;font-variant:normal;vertical-al=
ign:baseline;white-space:pre-wrap">Furthermore, we believe that everyone ag=
rees that both features are, in principle, optional to implement because th=
ey are controlled by a Setup option that can be set to zero.</span></p><br>=
<p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">=
<span style=3D"font-size:11pt;font-family:Arial,sans-serif;color:rgb(0,0,0)=
;background-color:transparent;font-variant:normal;vertical-align:baseline;w=
hite-space:pre-wrap">For the first phase of the discussion, we would like t=
o set aside short-term document processing, issue management questions, and=
 delivery timelines, and think about these standards far into the future. <=
/span><span style=3D"font-size:11pt;font-family:Arial,sans-serif;color:rgb(=
0,0,0);background-color:transparent;font-weight:700;font-variant:normal;ver=
tical-align:baseline;white-space:pre-wrap">Would this be better as one RFC =
or as multiple RFCs?</span><span style=3D"font-size:11pt;font-family:Arial,=
sans-serif;color:rgb(0,0,0);background-color:transparent;font-variant:norma=
l;vertical-align:baseline;white-space:pre-wrap"> Here are some consideratio=
ns that the chairs believe you should consider:</span></p><br><ul style=3D"=
margin-top:0px;margin-bottom:0px"><li dir=3D"ltr" style=3D"list-style-type:=
disc;font-size:11pt;font-family:Arial,sans-serif;color:rgb(0,0,0);backgroun=
d-color:transparent;font-variant:normal;vertical-align:baseline;white-space=
:pre-wrap"><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-b=
ottom:0pt" role=3D"presentation"><span style=3D"font-size:11pt;background-c=
olor:transparent;font-variant:normal;vertical-align:baseline;white-space:pr=
e-wrap">Does inclusion in the core draft increase the probability a feature=
 is implemented, and does that matter?</span></p></li><li dir=3D"ltr" style=
=3D"list-style-type:disc;font-size:11pt;font-family:Arial,sans-serif;color:=
rgb(0,0,0);background-color:transparent;font-variant:normal;vertical-align:=
baseline;white-space:pre-wrap"><p dir=3D"ltr" style=3D"line-height:1.38;mar=
gin-top:0pt;margin-bottom:0pt" role=3D"presentation"><span style=3D"font-si=
ze:11pt;background-color:transparent;font-variant:normal;vertical-align:bas=
eline;white-space:pre-wrap">Is the feature (and core MOQT) easier or harder=
 to understand with separate RFCs? Within the working group, people have as=
serted both viewpoints.</span></p></li><li dir=3D"ltr" style=3D"list-style-=
type:disc;font-size:11pt;font-family:Arial,sans-serif;color:rgb(0,0,0);back=
ground-color:transparent;font-variant:normal;vertical-align:baseline;white-=
space:pre-wrap"><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;mar=
gin-bottom:0pt" role=3D"presentation"><span style=3D"font-size:11pt;backgro=
und-color:transparent;font-variant:normal;vertical-align:baseline;white-spa=
ce:pre-wrap">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 e=
asier to revise the feature if it=E2=80=99s specified in a smaller RFC, rat=
her than having to reopen the entire MOQT RFC.</span></p></li></ul><br><p d=
ir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><spa=
n style=3D"font-size:11pt;font-family:Arial,sans-serif;color:rgb(0,0,0);bac=
kground-color:transparent;font-variant:normal;vertical-align:baseline;white=
-space:pre-wrap">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 ab=
out the issues, and discussed their concerns on the list by the 13th of Oct=
ober (Tuesday of the Seattle meeting). In fact, interop time would be a lov=
ely time to have high-bandwidth discussions. The chairs will initiate a con=
sensus call soon afterwards, assuming there is adequate discussion on the l=
ist.</span></p><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;marg=
in-bottom:0pt"><span style=3D"font-size:11pt;font-family:Arial,sans-serif;c=
olor:rgb(0,0,0);background-color:transparent;font-variant:normal;vertical-a=
lign:baseline;white-space:pre-wrap"><br></span></p><p style=3D"line-height:=
1.38;margin-top:0pt;margin-bottom:0pt"><font color=3D"#000000" face=3D"Aria=
l, sans-serif"><span style=3D"font-size:14.6667px">Regards,</span></font></=
p><p style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font colo=
r=3D"#000000" face=3D"Arial, sans-serif"><span style=3D"font-size:14.6667px=
">Magnus and Martin</span></font></p></span><br></div>
_______________________________________________<br>
Moq mailing list -- <a href=3D"mailto:moq@ietf.org" target=3D"_blank">moq@i=
etf.org</a><br>
To unsubscribe send an email to <a href=3D"mailto:moq-leave@ietf.org" targe=
t=3D"_blank">moq-leave@ietf.org</a><br>
</blockquote></div>

--000000000000ce2930065ded2b9a--
