[Moq] Re: Request Synchronization Use Case

Magnus Westerlund <magnus.westerlund@ericsson.com> Mon, 04 May 2026 10:15 UTC

Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: moq@mail2.ietf.org
Delivered-To: moq@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 4A8FEE8A2080 for <moq@mail2.ietf.org>; Mon, 4 May 2026 03:15:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1777889742; bh=mru1CDnIN/2Kxs29ZvTDs0ypJvD1N6JuaqznRxS1v6E=; h=From:To:Subject:Date:References:In-Reply-To; b=KggXcQ/b0wZvM8sy18AvAddjdk5TuiqI7Wc2jcdcM3IB8bTZFoCPnZLfHryOoTq33 hFC2x4GxmevJ5DCD7/agcWOY2nX/wBLGwIXCx3fLjQDXYN0Q2UQUi69L/PKSvl+z/K 8i73ZH0mxFIXCnS2cRv8mTC4rxIWx1FmwQe3TXms=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=ericsson.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ot40U3xMChw1 for <moq@mail2.ietf.org>; Mon, 4 May 2026 03:15:41 -0700 (PDT)
Received: from GVXPR05CU001.outbound.protection.outlook.com (mail-swedencentralazon11013005.outbound.protection.outlook.com [52.101.83.5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 6E82FE8A2039 for <moq@ietf.org>; Mon, 4 May 2026 03:15:27 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=CvOP1QCbgVH2dLs71L9DlEFD6Q31pC4XMFda7jmjg3HT932hsiLB5sBlTvdY+R9T7tsifbnvXMMBOKuzakjoYPLVeQ+WdDu7Fek///kE1vEjpGj1/B2Isy2AYRZu99l3o6FX08/ffd51a0zQ8oD22yYSa94y4vLEvXTg1C3RMklVWoo6PfNHTphlHoCLcAMSRSOuD+wc45GRaBdkfd3h9JZSMKqqOb/NloKwMDQ0x0RxVVg1+grG+YtTgktZlUY41aJRjQsFKJIv3VZdy/irpQNtMp211YC0DAqqbV1rrco7Hhb8fWfQ1QKOAKBvKVVYYGvjvGT/K7DT1Llpbt/dIg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=YlDSuCrn3jXtnHQ3SVKBg/M6DI1K9xWJUBEK/Fi36ZA=; b=XC7PH8OKfvCWqQQY33ETJVTCJGsOtcapa+HnhPRfuGqLzQM0q/vCpgnqP32YFc3C3w0HV1AOatzyvuwdWC4A8o8oAPa8KT4zK5vlT9gfGP+Fqf4zajInoxYOSy3sFdmdNar9mDMHerD/PH8y2ue8UGl4975h5BiY5MAOWIGc6u9gQIZfDVjelxwDLaWtRhgLZ+etB/wk1NPI11kqKS8OZ5ECIqyCgZT8UQqJWGZV+7BvaH93k5wn6ZIQ+GtVisKKtwNc2C3HiqLshY6iAhaUlBA8NprR2a1ZJ/hv5ElJ6WqD9JYfIVXxit34/KMK3jKM5cK/VqYw8p1stX3EB8uzKQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=YlDSuCrn3jXtnHQ3SVKBg/M6DI1K9xWJUBEK/Fi36ZA=; b=WutTxTfooOQmxy4Iz4MkD5ARxNePgsIrdPSeQ8okt4Yt26iddRI023YwKPEOKMRCsXj3OUw8sKMMwmmcYYtE9FwWhygniUOKYVpFC7hXcTgK67CxEV4bGp2xCK58UEEaEMbnAG3/MZTsQ+h09iDD8SCCv2e5LQBFgxdqdoj8P0a8Q9BiL8VO0srOv+b84gGOKtQDcQNnKCwO8t695pqaSXlrra5i0/R+ZSIhNOFYSGV+ajz33uKh5pPouYHR1trlmjVNsDoUGxPEPSgulu9+TFNQi+kV8RmX0CpZe9STFKool62DMV23EWBcWs16SrzvmjI05mOicoBHfI11vCRpnQ==
Received: from FRWPR07MB10624.eurprd07.prod.outlook.com (2603:10a6:d10:182::14) by MRWPR07MB11818.eurprd07.prod.outlook.com (2603:10a6:501:8a::9) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.9870.25; Mon, 4 May 2026 10:15:17 +0000
Received: from FRWPR07MB10624.eurprd07.prod.outlook.com ([fe80::4775:555b:372c:764e]) by FRWPR07MB10624.eurprd07.prod.outlook.com ([fe80::4775:555b:372c:764e%6]) with mapi id 15.20.9870.023; Mon, 4 May 2026 10:15:17 +0000
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
To: Cullen Fluffy Jennings <fluffy@iii.ca>, MOQ Mailing List <moq@ietf.org>
Thread-Topic: [Moq] Request Synchronization Use Case
Thread-Index: AQHc2bdyT6wZa4SzKUKx1h8+caeQh7X9oiKX
Date: Mon, 04 May 2026 10:15:17 +0000
Message-ID: <FRWPR07MB10624BD298CE4967DD5D2216E95312@FRWPR07MB10624.eurprd07.prod.outlook.com>
References: <E4E2EA18-6FA9-48C6-82DB-6F6D59F9F22E@iii.ca>
In-Reply-To: <E4E2EA18-6FA9-48C6-82DB-6F6D59F9F22E@iii.ca>
Accept-Language: en-US, sv-SE
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-reactions: allow
authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=ericsson.com;
x-ms-publictraffictype: Email
x-ms-traffictypediagnostic: FRWPR07MB10624:EE_|MRWPR07MB11818:EE_
x-ms-office365-filtering-correlation-id: 7eaa6697-338f-499d-b6a7-08dea9c60a5d
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;ARA:13230040|4022899009|366016|1800799024|376014|38070700021|18002099003|22082099003|8096899003|56012099003;
x-microsoft-antispam-message-info: HXnN7xIxXj+Z6mk/7rmdKDItCA15LhEPyMlby4cnSEO+PCgEpwtvlfe/zGk1/yko5Ps1TP3nMwN7j1oTPmeMS04T0/5r/ffWD6HG+k/2aGYOJ5vjWVNys3liIMExmGZTKXmKDFfuob18ypMezJt+2D/HmK1oy3PI8fI0o4j8pQKe0cA7t0VbF7AvrWs86nqbndZtqILMB/GshK0pD0n6DQl0HaO+M0n4QAhj7eRkYcQH7KTpP3O5LCp8BjRtZm4L34Gz9SF8z1gqIzhwl5y3EMeF+ljgXI1HBGi6Jdwkqg50kMscHVbZrTtUu68W/zs5LfUwIRc6fuVQaVDZfnCnEkC4VKVVdZDk2Yowmgs+zIYiYXdDtSOVuDuAZaSgYji1x/wEHms4ILvx1qsN04EimOGouxmhHAzNuwICy+B1pdslyS9gOrS0QgZe6V1KS2Ah4re+Jk50dwvyYgnMQwJOVhP1UF5MeMEEvMo68i1wMi2B+RFxlpQST/k7RKSPPqJQoWiTWgqt80XKRb74tFVvKON34f79oLV6x+im04HvRDaMosUBnvbRVyCR3bXMSJDaIdS4SPOD7SmW5gBbtOQJ99qmEFjoPBXikifMZ743eRdQ2zzEnHJxXhqC0pMOoftaZrbCmjQNILtsI8k+bxjjkEb64hO7lWnBdhO+b5J3sJw3/nTrZEJRZdR8rplJWxh7GZU2EL95Nm7ytsolOoc+Uh1YLsviltBzfOdUN0isoQzfrG5XUeMKVFhDXsW1hMuv
x-forefront-antispam-report: CIP:255.255.255.255;CTRY:;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:FRWPR07MB10624.eurprd07.prod.outlook.com;PTR:;CAT:NONE;SFS:(13230040)(4022899009)(366016)(1800799024)(376014)(38070700021)(18002099003)(22082099003)(8096899003)(56012099003);DIR:OUT;SFP:1101;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: qAmPpJmqokplzhn7dF9yveoF/ljhqabo4TAOsEBs8TDutaR2/lpx60nxEmfr2PFrY9kKjLlLHGAgBm8MKXBozm2uQUKaM6wdVZGXxp3RG0YPJYM5uMww2yfNuPe3Mec+IgahqiNNc0hfAWOFAxo5KGBUKmramGHMt12JaJsHux7/1IfwnLWuKBNKFhuAVHt42bsoTt1hjW9Oa4HIm2zFkgkLSCw73XijaORx37sAhlv6FeZXRItadzdIrCFBrho7w9nUZ6QKXlVNmeFRKHRAtAK+e5CuQCs52HUyeK7kfzHyZaUVSQpnqQnb/5zNjR51HXaa9NyiRr3qkpKcX8JNeclDLccBUIL53ZfUxPYxEbdK4miMwLuk8IRjyf2ZHGDB7IQo0aXzON7lZ0Vhgxx0y72OG99e+lrXOc+p3cyh354qfgTZHMOANKjfWLXICS5W5AvSoi1xHdbpZAr/2pDuIger9H57KgwefayYPrXmgAKb2/+F9iNrzXxIb7TyPBT7TrHfGWsuPpd0mdcJ2ligr9xUVi3D9F1dNNa1ynIoKRlPMQDvJyQxrbxsyOnvPUSO2uHwbmz/EMeqdaUUSCCu6/KBvGyh4t93wk+6gHAOFmePohsCb6oZlYS91qI4Kv5gsNYfcPDn2WHi292Q/ad/qLa4NGcj4wclyaPrfnAWdRwuJmaMRmwJVaDrB6aeVYKzyFGnf5n6DEfTabZuneCO9SR5AjcNUGMYNM572pqR4TmhmdScWFfaK5Jk0o0n3NWC1eTuiCMdpXLobCm2WZpEckswD6IOIzbEURIRfXrvM4Qe1Kpf90PTX9LqVOp53UUy8VGoMXsz139YjHe85miWLrvwrxcnMsS89Var/MKMmVCKOdEBOrn1G3Agrw14l1HIBtrLwUjaPi7r/v1V7GePqyd5mfSjXKwFt9GgSqvdC3PgZTQZOJ1plZ6XRRMcJmiQjRwRejfQvOcE0r//K2nSkabNO3xxCbjij7zixsbj3YgDTnZno+eCN7ufPS0gFIA6ibOU57sWN9FgHJnaSOLDwjmntcwtHaJW9LHfBzX5BLt6y5HNbRG2GsJPcdpvW4n4llA7DSfXoRJU6ypPm5ImOtVIdV4F9qw0s4MvGuAgiLQ2K6MJRefVlPe7BryLJgMyBOHjWR2D/lbV0eY2SbXUbZW7Gp4oIY7Tx49VwjfvhGuRzOLVPd5vPF2nsXhsQbglIFcdZ3l6NDB9o8W9exyaNhfou0wuvdFmXIPoWy8ZeSzXdLGjII937kzucn7MKkIjPOrZ9QnqMbQiSv9qY8AXWFQpfLufSvfeBnLpwM9hvIlg0bhIXsF/uy0EQRKnVPzKVu0Q/Pcp81shClW+EVX/ed3XdBuSgqM/8aQKVPfm7lLvJh4b/QsAlv3Bn8nfsq7tWSlaClPu3CjOEVwH+NgdUKt/k5QNFrngcYP0oI//41xVzRqT1tjr26vd06tglGSm9pPF6/fcwCh2qRdVKInvk0KF3KbGfl9ZPoNLUiiCO/Z1QtWQ+CZxAuU22ou9CFuLZMeGo+URx/beVZs6+3PtcH2T7b1paESi8yTj8R23F1pMvB8zxGSfXGEgt/Sc4+GvulK1rCfpJN9VWKDyOkqy29rC+4I79XLKGisN+5vMBtPd7EgN5yurvU8jWprmNG16GspWoHiPTYUFpHeUgtgMN8XlLD5ctbET6xozEk592gywQU86F+Lu9Z5wrfXDFXe3XNSrMzk41L6CkfQ9oaEyVXz46U/SoZ+ssRMnjq/mbIQDIKKjsIo21e/PXveHEJZy
Content-Type: multipart/alternative; boundary="_000_FRWPR07MB10624BD298CE4967DD5D2216E95312FRWPR07MB10624eu_"
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: FRWPR07MB10624.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 7eaa6697-338f-499d-b6a7-08dea9c60a5d
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 May 2026 10:15:17.5099 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: Pok8JUWFmMybm51LYyiEXihsXKNH7qXmGP9rf1dz+Vc/Z8o6HuzatYuJW5bN5BbF9e437aFCAVzhXay7zoDO/Zx11CQnU5n5jvd7JGdRmBw=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MRWPR07MB11818
Message-ID-Hash: 4LS7NGHFL3VY6KQIBJY43VWWH46CHX55
X-Message-ID-Hash: 4LS7NGHFL3VY6KQIBJY43VWWH46CHX55
X-MailFrom: magnus.westerlund@ericsson.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Moq] Re: Request Synchronization Use Case
List-Id: Media over QUIC <moq.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/moq/UoDRMucPSFVAKzwJPeKVex1f0Io>
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,

This email is a to discuss and clarify the mentioned use cases. See other email related to consensus and removal of the functionality.


  1.
Swap Tracks: When you say pause here, are you using REQUEST_UPDATE to switch the forward flag on these two existing subscriptions, or are you referring to new subscribes and termination of the old one?
  2.
Client Side ABR: Is this accomplished using new subscribe and termination of the old, changing forward flag, or assuming SWITCH?
  3.
PAUSE, Unpause: Also, here I would like to have some clarification on the mechanism used. Because I don’t think you can get request reorder with REQUEST_UPDATE as they are sent inline on the same stream for each track. Thus, eventually all the sent requests will be delivered and processed in the order transmited assuming the QUIC connection doesn’t time out.

Please clarify these use cases so that we can have an informed discussion.

/Magnus


From: Cullen Fluffy Jennings <fluffy@iii.ca>
Date: Saturday, 2 May 2026 at 00:11
To: MOQ Mailing List <moq@ietf.org>
Subject: [Moq] Request Synchronization Use Case


I don’t think it is worth trying to repeat all of them here as people can feel free to find them in the previous meetings but let me mention a few

1) Swap tracks. In a video conference, a subscriber is subscribe to track for Alice and Bob’s video and is watching Alice with Bob paused, but wants to pause Alice and unpause the track with Bob. It’s pretty common to want to ensure to pause the current one before unpausing the new track to not have congestion.

2) client side ABR

3) a stream being paused and unpaused in rapid succession and requests reorders on the wire resulting in the opposite of the desired state.

I understand the spec never required the relay to strictly enforce order of operations but that was discussed as “quality of implementation” issue and the time that a relay is likely to get them out of sync was always pretty low ignoring upstream request delay which the use cases can avoid. Most high performance implications are likely to local all the traffic on that quic connection to s single set of processing thread anyways further reducing reorder likelihood.

I’m a bit concerned with how the chairs are positioning this, at the time of the call it was just a poll about did we need to get this sorted out in -18. I don’t think anyone cared about that as there is already too much in -18.  Martin clarified as the poll was about punting this to London at which point the objects on the poll were removed. I’m fine with punting this to London.

But after the call I realized what was happening here was the chairs are going to treat this as we no longer have the consensus we had on drafts up to -17 where there was a way to indicate ordering of requests to the proxy. We had no objections to this in last call of -17. We are trying to get to done and reopening base issues about what the requirements are is not helpful.

I want to be very clear I would have objected to bidi if it did not have a way synchronize - this is a fundamental part of bidi. I did not think the poll on the call was that we going to remove the consensus we had around -17.  I hope we are are going into London with are assumption about synchronization being we do need a way to indicate desired sequencing of requests to the relay and we are sorting out the details of how to do that without introducing dos problems.




--
Moq mailing list -- moq@ietf.org
To unsubscribe send an email to moq-leave@ietf.org