[Moq] Re: Draftification
Suhas Nandakumar <suhasietf@gmail.com> Fri, 16 October 2026 15:16 UTC
Received: from mail-oo1-xc30.google.com (mail-oo1-xc30.google.com [IPv6:2607:f8b0:4864:20::c30]) (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 7FC0B46 for <moq@ietf.org>; Fri, 16 Oct 2026 15:16:32 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=pass header.d=gmail.com header.s=20251104 header.b=Y6CLi4gW; arc=pass ("google.com:s=arc-20260327:i=1"); spf=pass (mx.ietf.org: domain of suhasietf@gmail.com designates 2607:f8b0:4864:20::c30 as permitted sender) smtp.mailfrom=suhasietf@gmail.com; dmarc=pass (policy=none) header.from=gmail.com
Received: by mail-oo1-xc30.google.com with SMTP id 006d021491bc7-6cfed5dd083so45804eaf.1 for <moq@ietf.org>; Fri, 16 Oct 2026 08:16:32 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1792163786; cv=none; d=google.com; s=arc-20260327; b=SgCYt2CJes2W+W1ClVCmE1W8K2+Lv59dtUio4D/rtFua1PxBq5j6O9vePombQNhsg1 zle/X8YZhJprdyTreemA+yosYHiCHvWizAJvgyjrtfvGxPlCz9jTw9ayMJksyly8Nzbk 7ZmuIBDH3omJgxuu2XqQ6fdlAqUR2zYwJf2xJ+f2wwOfOb5LruKj5QZI2+sZGVhVAdsA CUCGs+jqn7iDAkOKMnfa05ApZhL49QqPaksMGvtlRZo5dNb/oa8m5Ex+qjPteKFLaUcp 7yFVNKEVSwYAaIXPfRVBCqkip0H9RXj5cDIEOw6GiaS7iK1yYIxY4//tFEZIQTTc9sTL sGhw==
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=JUg5vkv09snfnQgOGM/+e3+HcPIuLcXNmqZpzJLoBDE=; fh=Bh8SLOboMLLYabYfwabrTh1ugU8vrMO/jKMoWTZ7VUI=; b=Ntj0lHj3pcrTqytflmUi0dKABvXpGIchcr87YGjJmZu9KRD8G6iTjdNkiIWojLRNT3 B9+ALy8zcocOCcq1IzgzBBBeSaiC9pJr7GhuRRwdp2JN8U1HlhFCHpp9icDjcdXgOZPU vVYcTZrnuI2fDcJ3Tgsb9xIPgTBMk3sCWl69Yzl8+Zoo1w7q/IOIwJZ0QcguqyWzz2p9 AmyNSli9f0OxZcTc930/S8kDg5dnq10cawtxUeEogeGEru9rL/GsUX4aCLniDRaJifo9 yEvPVOXADG2o+P1xGL/JUYfnFv8Ujc/sDg4MoQx2wRBUhKsQQBsRPoX5iksFduo7w3Cs U/LA==; 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=1792163786; x=1792768586; 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=JUg5vkv09snfnQgOGM/+e3+HcPIuLcXNmqZpzJLoBDE=; b=Y6CLi4gWEAUJJi2VYbe7zmj8XRwuda4vyTCFFUKXGqqeiosnC1a/CAHu2xyL9ly6K/ pGgqjycFQXPST8Dmo3t3GKBIvME9O/BlSMLzkaJ/XgFzdTsXabgpw2SJvFb+Yob1xVml B0Goq/qzVGwkSlW6xqwRa67qDPE3URxVFJxvCcZf+HFo574qb5XTR9KA4L4GlNLpqhO8 b8LVn+8gC0gvcrGBxFcZAWdB4iMGfwV3Hb4l5X0XSc47moch6t6z8VvITqY/YfguMehN eAG7ZJ2S+kCOWoD3c6iFBu1mNNGRETnZLke/thRQ81JOiQ56AHruFVvPQzqPrQH5UmDl X4OQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20260707; t=1792163786; x=1792768586; 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=JUg5vkv09snfnQgOGM/+e3+HcPIuLcXNmqZpzJLoBDE=; b=U0pXkWcjUU7krAKQTS3OLPiXhThVzr+mUATNK0SmMMGtMTdD7l//gT0T0vQbnbWpDr ATPLFhHvYnb//RKZ+gRhs3iWK1S6nT6DMbW6cp8XUd382SlR889NYcRrpz134GEPtMLV EEZAlgL3XogE38lG0rayx5p5to8cWEMUcXP3Y7dUSxAOvNUhfpFELWBW+FWc+D3PtB28 03M8h7rZv12DWFR4FH7dDmnMJO3pDGZf+sJGvGQNL4SMQwT6gfyWvRAb0K4Q5X9jqST3 qve8nIIaS+1SNmI0ogyHfhan/AcH+cKoWj77N8Zl0inzgFtWke3SkkMfEDxwQdDCkHgB TVeA==
X-Forwarded-Encrypted: i=1; AKwUvBxOFgDBAkYCDjX5yUucisvZWAn8QcJvCoKBYdWVKdUQVV3HQNBj5XodJ0d7yIxGGEYMgdk=@ietf.org
X-Gm-Message-State: AFq9FYKFaSByOvc6eHojd2B+1KqBJs0iiB4aHbg5HbYQ4iS0E0VTZhNj YFlL3KqgyTh5jcpRonq/xPPpOw+UvlDqkvqGGcT/6DJYYWITMQkwOCLtX/wevdbqML4Fhur7XIm SPYkfx/rKLYexZElpxQNy276BQfEwToSD/Q==
X-Gm-Gg: AYBFou1kDSPYUHU2L/gUBWTWGHaUdl2II21ifkMCEUsIeEqwi5Hzbf2LYVIYb72Dq9a o36Sk51U7Um6y1yTkNbhlGKvFOsPqtlrA0vrnovYuaS33F4yMdT4ckrIbXXac3FEMiH4oLPUugB 6MGx0GtAaU9EPLSsQvCfQNOojEiYg59xfPgI3oiVXzXB5UEUaZld7/AsPLPmj8kBfqTi7Eqg3sM YR03buBjBzPWVNcFcIFF7QHogAsxNUmVBRgLNgumLRJwKRWPsFhUaTxYksX2OB5ybuOaZunNshN zz8c2LkULr2FUOQrl+wmgymAedW5lOTFbl0oRP0Sa4WI9Xb92VaRnbEP6rKUmsPiA2tpuibKpsP kzKx2vLOicA==
X-Received: by 2002:a05:6820:825:b0:6b7:83c5:fe01 with SMTP id 006d021491bc7-6f6dd1ee722mr12808444eaf.66.1792163785541; Fri, 16 Oct 2026 08:16:25 -0700 (PDT)
MIME-Version: 1.0
References: <CAM4esxSJakJ06X80D_-keweXCKM6DTCUvuVZsAyxet98eF6dGQ@mail.gmail.com> <CANPAELvH7Oqbi64xXx3NAW84H5KXMmLBp_O0Uh269Mm9cq2EHg@mail.gmail.com> <CAKcm_gNttgNXqVfECPtz2XR=5EiM0_c8PJNWBHeYvOBrxwG9QQ@mail.gmail.com>
In-Reply-To: <CAKcm_gNttgNXqVfECPtz2XR=5EiM0_c8PJNWBHeYvOBrxwG9QQ@mail.gmail.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
Date: Fri, 16 Oct 2026 08:16:13 -0700
X-Gm-Features: AclHuK_Q01QQMVIoMGYn4gv29C-6OfoyBbZGATCq2XE_VelRMb2iIu5dJHMWues
Message-ID: <CAMRcRGQxhhGUz34OMQwYBcmC2mxi2CetmfPdzmVtNJVHEdh1kw@mail.gmail.com>
To: Ian Swett <ianswett@google.com>
Content-Type: multipart/alternative; boundary="000000000000d10d1c065df6a5ea"
X-Spamd-Bar: ----------------------------
Message-ID-Hash: BNEGEUGQ7IBAPBDWZNWXQNQLGEXKNE4G
X-Message-ID-Hash: BNEGEUGQ7IBAPBDWZNWXQNQLGEXKNE4G
X-MailFrom: suhasietf@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: Alan Frindell <afrind@meta.com>, Martin Duke <martin.h.duke@gmail.com>, 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/X8LMLpbs8tnrV5B5D_fWcFDLoDg>
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>
On Thu, Oct 15, 2026 at 19:06 Ian Swett <ianswett= 40google.com@dmarc.ietf.org> wrote: > I agree with Alan in general and prefer separate drafts, particularly in > the case of Top-N and SSTS. > > QUIC was 4 RFCs plus 2 for HTTP/3, and there are many HTTP/3 > implementations. I don't believe that people will only read the core draft, > and I don't understand the basis for that claim. > > For Top-N and SSTS, the way they work together is apparently workable, but > I think using a single algorithm to do both would be more optimal. But I > don't have an immediate suggestion. Maybe if we finish MOQT, we'll get > more people working in this space? > > The recent PR#1982 <https://github.com/moq-wg/moq-transport/pull/1982> demonstrates > thinking about Track Selection is evolving and that's an important reason > not to add it to the core draft. It puts us in the situation of either > rushing a feature that isn't as mature as we'd like or greatly delaying > publication of MOQT. > Hi Ian , Your input is important and love to understand further on your feedback. Can you please share technical insights on why do you feel top-n, for example , isn’t mature. IIUC , PR1982 doesn’t redefine any of the algorithms that has been widely discussed with in the WG , rather uses them as-is. Love to explore further on where top-n can be improved There are a number of usecases that have no need for SSTS or Top-N, so > delaying those use cases has cost. > > Clearly MOQT needs to have the extensibility to support these extensions, > but I believe it does. > > >From a practical perspective, PRs that are outstanding for a long time > accumulate large merge conflicts, so unless we have consensus to merge it > into the main draft soon, a PR is unhelpful. Range Filters had issues > filed in a separate repo, which was very helpful for tracking and working > through issues before we merged it. That being said, we're still > resolving editorial issues with Range Filters. When large changes are made > to the draft, it takes a long time for the change to stabilize. > > Ian > > On Wed, Oct 14, 2026 at 7:59 PM Alan Frindell <afrind= > 40meta.com@dmarc.ietf.org> wrote: > >> In general, I prefer more, smaller drafts rather than one mega draft. >> Smaller drafts are easier to understand, review and revise later, and >> spread the editorial and design load. >> >> I think the number of drafts our group produces is not relevant to >> implementation. Implementers will implement the features that the >> marketplace demands, regardless of what draft they appear in. There are >> plenty of protocol extensions that are widely implemented - DATAGRAM is an >> extension to QUIC, Priorities and WebTransport are extensions of HTTP. >> Both features in question already have multiple implementations as well. >> >> No one has articulated a concrete problem with the existing MOQT >> extension model that prevents Top-N or SSTS from being extension drafts. >> SSTS is already written as an extension draft, and Top-N could easily be. >> I’ve said many times that getting extensibility right in the core draft is >> critical: please file issues for specific aspects that need to be >> addressed. As others have said, writing these drafts as extensions is an >> excellent pressure test of the extensibility model. >> >> I want to reiterate that I feel both Top-N and SSTS are valuable pieces >> of the MOQ ecosystem and the working group should deliver standards for >> these features. I think continuing to progress these features in their own >> working-group-adopted drafts makes the most sense for now. I’m also >> comfortable holding parked issues for revisiting the draftification >> decisions at or before WGLC. >> >> The best use of our time now is resolving technical issues in the core >> draft and these proposals, not arguing about which document holds the final >> text. >> >> Thanks >> >> -Alan >> >> >> On Mon, Sep 28, 2026 at 9:33 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 >>> >>> 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 mailing list -- moq@ietf.org >> To unsubscribe send an email to moq-leave@ietf.org >> > _______________________________________________ > 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