[Moq] Re: Simplifying the Object ID Model and caching

Ian Swett <ianswett@google.com> Thu, 22 October 2026 19:52 UTC

Received: from mail-ua1-x933.google.com (mail-ua1-x933.google.com [IPv6:2607:f8b0:4864:20::933]) (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 31ACD47 for <moq@ietf.org>; Thu, 22 Oct 2026 19:52:51 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=pass header.d=google.com header.s=20251104 header.b=MySiZgnk; spf=pass (mx.ietf.org: domain of ianswett@google.com designates 2607:f8b0:4864:20::933 as permitted sender) smtp.mailfrom=ianswett@google.com; dmarc=pass (policy=reject) header.from=google.com; arc=pass ("google.com:s=arc-20260327:i=1")
Received: by mail-ua1-x933.google.com with SMTP id a1e0cc1a2514c-99061e2171cso88057241.2 for <moq@ietf.org>; Thu, 22 Oct 2026 12:52:51 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1792698765; cv=none; d=google.com; s=arc-20260327; b=CW7rYp1h8dvN46ut+KYhUYlmPQHfXbwZFt+jQ30YR+NTdzUD4Q9R60CSl0zNT4yYhF SBb+W+Vog/eEeJt3NY0EWADbgHGIlt+o3dPrlIqlpmDyNanCmvRTppSR+hPLbovuYb3E pvIkDop0ApiVWTen2eGmSRJI2YtfMs2uEn78AfokfrnA7GqKnWZY0fuJ4bmDS/EEOSqq oxDIzy2a5HIOtoRZdKbmWU4Etw0L6vIxCjWGhmzJYpI1XaflVprxg1+wsG4Gk6ayFxdO yn/T00e2/m4nOo+LiYOnSjEvs65PuDbyjW1XhhTVo/yPPZ5zuxImh3F7Um9I2EN/BJVH ZcVQ==
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=tgZ0NuvKcXxB/NimD2grJdiyeUQ0rTG9OmmBH/MDGmw=; fh=ODKyVsJyLFofbsdMigehqRUW6dCLwz5KtK20U1t2CLA=; b=jc9zqSe+7GaX/cXqTwU7A7nSAt8fjKOdvIOTioTyD8LvWqDJvCcoKwk/Wq7fJSB1sl VRwcyl/NgQZEwRuVkDnGoFxYtIteg8q8ZtUjtaDii8taPN0HoETejMDDWhTV41OvmYIw gN97Kjk7GuTJmSTPxipz6Ctp67NEjVSR1qawJ/LCOZxD8QiYDVvSOAULABIbAB9EvR9f rLqlXDp9ohhHXgGym62mvVBuMuGB3lZ4tSuHsjj6elaA5e2GGuf+5AAMd72GU3gDFAPI SA3k5n008dNtmlQrciJnEvXC21hugbUEaNtXdILh3XV9GZnE2LEUm9tzOt2+mQGq4y5O aCpQ==; darn=ietf.org
ARC-Authentication-Results: i=1; mx.google.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20251104; t=1792698765; x=1793303565; 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=tgZ0NuvKcXxB/NimD2grJdiyeUQ0rTG9OmmBH/MDGmw=; b=MySiZgnkwNkLM20xp/IW2sDsbt6/MhRLyNPfjBiSsBWk6IXEq1+VAE+7q5HUjZarqd IgSbBrae3WdnmanFt8F/Y0d8l7A1gs/r4hAkh5ExH3efITJvesKqtjkC1Qdt4V5U+Vo+ rlCdn4DvsaCNZykfn+VxDNzk9wPVKNpoRVUC2JwvVPGzHgYTrXVLI/D+5FqFADCeTLii 6WQgICG9dTQ1bZFvS63uxs7R8JYCu14c/ugilXghfUMDkRfLN4jrzM7lpMJCrTO+pyuR tu7mMb2F3Q+6Wfpu3DZA303RBgh38B3F/gbWxuZHHTMLorik39quFmG2qEjN5l1tFy7O gvXA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20260707; t=1792698765; x=1793303565; 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=tgZ0NuvKcXxB/NimD2grJdiyeUQ0rTG9OmmBH/MDGmw=; b=W/QL/gfVT0a8nH9254RklANafvY54DIYwb5O2dZcCgS9Al80k4YKUnZGVJTKC2NIHG 51DdJduR9Tz+XM1yudxojlTjDTuzYpXwfP+/3YYkg+tZCuLG4WwC3woce80scUYx+jgg wtYm+JiwwIA9h7uxgZZOCNKlbTbT8hOyeD1DDQnQ3pVdTk3H45BUcdWYcIpfDGgp8s+d BwlPzyky0X7/IkMuhGA6pYLnFN89Z0Je0S0isUcUZDyOCFNOQ3E4Bw9C+iJqp/1MTMkf MAzEuolaJtHvoPkRiTO9L56M4gz77bo/5cKXnKUlnniYVjjzY6e7g69RbFbjod62NXpj WGmg==
X-Forwarded-Encrypted: i=1; AKwUvBxnKCxsN9bzpyCE/drFLsez2YHO2/sbH4oalotRPVI1WUrsnDptWnOjNWPhynBkLuH2eFc=@ietf.org
X-Gm-Message-State: AFq9FYKxVnKeZCCdRwIIZLM/XFOGRj+XbiDA3mlnOFdh8MJ6xcs+T354 2DSCcUJoieJJvbvvzMp3dQ2lf27CpKpDrVN7O4pCalR2K1ZKkgtfz42I8D4Ah0AlUyl22mvDRP7 uPs0Dc5uSECj11nqUzjH01+VErl7qXLFuRFcmftH9
X-Gm-Gg: AYBFou12yoOECLquR3oglAc5zDtjGqORNK5mxUijW2X7y8u+U5xtJx8Q/khL6iBvNco 4jXMIGRRN0SuD8Ffbr12IykUpFnuiwndAW3M/X1auXnKFslW5inff27KgdtluakprgT/KWur7v+ W/CCHxuqN9jm+OR3iO/l2fB1nB0BV2aPV+h1Shq0e/IXtR7JRKSDJnZQt9GV+tjwTujVKjZvfF3 DZUPCcp5OCyZ+rW6Yq9rXFXqGyfKNYy7/4nGaKy/Tq3zpdwbTrCHzM2vBH3ExwHzix3nYyiS61s eEh/Vvn8Cv7RsFVmvD1SB1Y7piMBGLYpC46NkFxJp/MaM7vuS0KgphFj+df4PmnyVhKv7OID6tf oJYOzKYn49h4hO90ZIVNtZgzDaeSty6kBcMmSkzSPp+g3ryES7IS/MDHlrgHuZLF3Z3ybPmurnS BKuA9FS6Lt+fAGcgsOSuitC8WoVELihkdzeK+lJ19Fyn1n1LRabdM=
X-Received: by 2002:a05:6102:c49:b0:7c8:18a2:f769 with SMTP id ada2fe7eead31-7ccc2d88b8amr212149137.0.1792698764297; Thu, 22 Oct 2026 12:52:44 -0700 (PDT)
MIME-Version: 1.0
References: <CAKcm_gPVnSLx=3eTzqU6mkCHTTMZx3Px_RyKB+RgqdZ5oRyMEg@mail.gmail.com> <CAKXiRhMg5PG1Ac-LCfCA+LadiRbUtKEMsrssKQudA_KkeN1WLg@mail.gmail.com> <a521293c-9454-4023-bb24-c6bf98c263b5@huitema.net> <CAKXiRhPv3irQ5HtpngVnBYXLtu3eKbC_NZ7de9uk5AGBDEm8DQ@mail.gmail.com> <DS0PR11MB81817F1DC0672BAA9326CA5AB4652@DS0PR11MB8181.namprd11.prod.outlook.com>
In-Reply-To: <DS0PR11MB81817F1DC0672BAA9326CA5AB4652@DS0PR11MB8181.namprd11.prod.outlook.com>
From: Ian Swett <ianswett@google.com>
Date: Thu, 22 Oct 2026 15:52:33 -0400
X-Gm-Features: AclHuK96Oza5UH1hJOhOv4oXeEeH5S8MnRzRAlfbez3V2yeM1u1VD6QVVsJ5gf0
Message-ID: <CAKcm_gOJeQRH3P7gQ0qJ=234AitKC-iX48s1QgfwXo3Xf=k_iQ@mail.gmail.com>
To: "Mo Zanaty (mzanaty)" <mzanaty@cisco.com>
Content-Type: multipart/alternative; boundary="0000000000000af434065e73351c"
X-Spamd-Bar: ----------------------------
Message-ID-Hash: HZA6SLR6YLFXRDLMJGZZTDLQS53LJQR7
X-Message-ID-Hash: HZA6SLR6YLFXRDLMJGZZTDLQS53LJQR7
X-MailFrom: ianswett@google.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: Aman Sharma <amsharma@meta.com>, Christian Huitema <huitema@huitema.net>, MOQ Mailing List <moq@ietf.org>
X-Mailman-Version: 3.3.10
Precedence: list
Subject: [Moq] Re: Simplifying the Object ID Model and caching
List-Id: Media over QUIC <moq.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/moq/AGzAAMVtzxjaRJsiCCtbAZhfH2k>
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>

Yes, Prior Object ID Gap can help, though I'm unsure how to make it
required in practice?  I guess a Subscriber to an OP could declare a Track
Malformed if it didn't include the Prior Object ID gaps?

Unless we did something like what Luke suggested, the cache will have gaps
and Relays will have to deal with that, but sequential IDs (or required
Prior Object ID Gaps) do make the problem easier.

Ian

On Thu, Oct 22, 2026 at 9:03 AM Mo Zanaty (mzanaty) <mzanaty@cisco.com>
wrote:

> Prior Object ID Gap already handles the case where the original publisher
> made gaps. Maybe just make it required? But I don’t see how eliminating OP
> gaps helps relays or end subscribers, since they must still deal with
> non-OP gaps in subscribe and fetch, which seems like the dominant case.
>
> If the problem is excessive relay upstream actions on a fragmented cache,
> can we just punt this downstream? If a fetch spans cached and unknown
> objects, deliver the cached and mark the rest unknown in the response. If
> it only spans unknown, only then request upstream.
>
> Cheers,
> Mo
>
>
> ------------------------------
> *From:* Aman Sharma <amsharma=40meta.com@dmarc.ietf.org>
> *Sent:* Wednesday, 21 October 2026 23:02:02
> *To:* Christian Huitema <huitema@huitema.net>
> *Cc:* Ian Swett <ianswett@google.com>; MOQ Mailing List <moq@ietf.org>
> *Subject:* [Moq] Re: Simplifying the Object ID Model and caching
>
> I think Ian’s proposal eliminates fetches needed merely to resolve
> intentionally unused ID slots, but you're right that fetches may still be
> needed to recover material omitted because of congestion (e.g. timeout
> cancellation, datagram dropping, etc).
>
> On Wed, Oct 21, 2026 at 7:41 PM Christian Huitema <huitema@huitema.net>
> wrote:
>
>
>
> What happens if a relay is skipping some subsets as a response to
> congestion?
>
> On 10/21/2026 7:36 PM, Aman Sharma wrote:
> >
> > I agree that this would be a simplification, and would allow us to
> > remove the Prior Object ID Gap property. Any implementation relying on
> > non-contiguous object IDs could trivially define its own parameter to
> > convey the information previously conveyed through object IDs.
> >
> >
> >
> > On Wed, Oct 21, 2026 at 7:00 PM Ian Swett
> > <ianswett=40google.com@dmarc.ietf.org> wrote:
> >
> >     I believe all members of this WG can agree that the MoQ Object
> >     Model is too complex. In the past, we've been unable to simplify
> >     it, but I believe there is a simplification that improves caching
> >     and is acceptable. That's sequentially
> >     I believe all members of this WG can agree that the MoQ Object
> >     Model is too complex. In the past, we've been unable to simplify
> >     it, but I believe there is a simplification that improves caching
> >     and is acceptable.
> >
> >     That's sequentially increasing Object IDs beginning at 0 (ie: 0,
> >     1, 2, 3, etc).  This makes it trivial to know when all the Objects
> >     in a Group have been received once the End of Group is received,
> >     and it avoids unnecessary Fetches upstream when a Track is
> >     initially Subscribe-delivered and then cached.
> >
> >     I realize there is an attraction to ascribing a meaning to the
> >     Object ID (e.g., using it for the timestamp), but the byte savings
> >     are minimal at best and this makes MoQ much more brittle. Don't
> >     think I haven't tried.
> >
> >     Are there people for whom this would break their usecase and can
> >     they explain why?
> >
> >     Ian
> >     _______________________________________________
> >     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
>
>