[Moq] Re: User case or question to Joining Fetch

"Law, Will" <wilaw@akamai.com> Wed, 13 May 2026 18:40 UTC

Return-Path: <wilaw@akamai.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 3BE82EDE866C; Wed, 13 May 2026 11:40:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1778697645; bh=f8N/33qfaWkd8kiYM+MGS3cer34RdftFV0PtBUKf988=; h=From:To:CC:Subject:Date:References:In-Reply-To; b=I1lX/QruIVN+uNNx1KFRbO9uSuu0SASUElSUi6Vv9Jqh4yA5R5MmSmkIBwYqS0+gV DtzX7qP7BqN+Szv29mbqBK5J6ENzMMt1IH6kWzPcYHpuFsgSMOswzIU4b0AuHC/n09 3IjVXc7ZiTSQH3YXnG8AIdhCvWyW+7gXEpXOKp8o=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.794
X-Spam-Level:
X-Spam-Status: No, score=-2.794 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_LOW=-0.7, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=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=akamai.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 fKDaXCVvSWG6; Wed, 13 May 2026 11:40:41 -0700 (PDT)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [67.231.157.127]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 2DB13EDE8609; Wed, 13 May 2026 11:40:13 -0700 (PDT)
Received: from pps.filterd (m0409410.ppops.net [127.0.0.1]) by m0409410.ppops.net-00190b01. (8.18.1.11/8.18.1.11) with ESMTP id 64DFgJN72498196; Wed, 13 May 2026 19:40:13 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=cc :content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to; s=apr2026.eng; bh=f8N/33qfaWkd8kiYM+MGS3 cer34RdftFV0PtBUKf988=; b=OPSuYsw/mZC+OhoezP9PMKcPcFn7HVyFHW6vaz t8rkH+yp/WnNVq0F2CM6o00x7oR9hJucRgWPfB/sg3qMX5tdaQHuYUur0LLvDepY l9Kw8B0CI58TNp70ZoQKgUwffei6RPd6owOIR3+h7BLDlB4M8V/nhS5bhlxas0le kDndaP2V+aSLTdInnfKzFcjuz657PBML+/7cSslQ71QBGqEC54MhAVHUBrcCzgNh yAcFvOnkIv+TW+a1MV9UJlNBQ8rwa85LOt+xe3SzsVSbQkFZuxgri0eiNkJiZCle eAsXWDw6uzcVQdaNLONCIF6rrJlVRFr1jVgiNmG40hOSdvCA==
Received: from prod-mail-ppoint1 (prod-mail-ppoint1.akamai.com [184.51.33.18]) by m0409410.ppops.net-00190b01. (PPS) with ESMTPS id 4e2fu6tgy3-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 13 May 2026 19:40:13 +0100 (BST)
Received: from pps.filterd (prod-mail-ppoint1.akamai.com [127.0.0.1]) by prod-mail-ppoint1.akamai.com (8.18.1.7/8.18.1.7) with ESMTP id 64DIc4u4008490; Wed, 13 May 2026 14:40:12 -0400
Received: from email.msg.corp.akamai.com ([172.27.91.40]) by prod-mail-ppoint1.akamai.com (PPS) with ESMTPS id 4e3nepdwks-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 13 May 2026 14:40:12 -0400 (EDT)
Received: from usma1ex-exedge1.msg.corp.akamai.com (172.27.91.34) by usma1ex-dag5mb1.msg.corp.akamai.com (172.27.91.40) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.2562.37; Wed, 13 May 2026 11:40:11 -0700
Received: from BN1PR07CU003.outbound.protection.outlook.com (184.51.33.212) by usma1ex-exedge1.msg.corp.akamai.com (172.27.91.34) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.2562.37 via Frontend Transport; Wed, 13 May 2026 14:40:11 -0400
Received: from SA1PR17MB5154.namprd17.prod.outlook.com (2603:10b6:806:1c1::15) by SJ0PR17MB5111.namprd17.prod.outlook.com (2603:10b6:a03:399::21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.9913.11; Wed, 13 May 2026 18:40:09 +0000
Received: from SA1PR17MB5154.namprd17.prod.outlook.com ([fe80::b160:84f4:21e9:bf72]) by SA1PR17MB5154.namprd17.prod.outlook.com ([fe80::b160:84f4:21e9:bf72%4]) with mapi id 15.20.9913.009; Wed, 13 May 2026 18:40:09 +0000
From: "Law, Will" <wilaw@akamai.com>
To: Zafer Gurel <zafer.gurel@ozu.edu.tr>
Thread-Topic: [Moq] Re: User case or question to Joining Fetch
Thread-Index: AQHc4q15+xPwZJGB8U+Nu7y9Nq1jJbYLtqapgABAQICAAAdt5YAASzt5
Date: Wed, 13 May 2026 18:40:09 +0000
Message-ID: <SA1PR17MB5154A7CC62CB1EE43CCC05F8DF062@SA1PR17MB5154.namprd17.prod.outlook.com>
References: <OSKPR07MB10446C0EA1AA5C358409DE87F96062@OSKPR07MB10446.eurprd07.prod.outlook.com> <SA1PR17MB5154DA663EBDB0C9A9090FD5DF062@SA1PR17MB5154.namprd17.prod.outlook.com> <CAPguchnFehGECBPk5RsfTrf2+kwZJDHvwN=xXqGz18GrSjvnOA@mail.gmail.com> <DS0PR11MB8181E06A56C046F16C9852CDB4062@DS0PR11MB8181.namprd11.prod.outlook.com>
In-Reply-To: <DS0PR11MB8181E06A56C046F16C9852CDB4062@DS0PR11MB8181.namprd11.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-reactions: allow
x-ms-publictraffictype: Email
x-ms-traffictypediagnostic: SA1PR17MB5154:EE_|SJ0PR17MB5111:EE_
x-ms-office365-filtering-correlation-id: a62d2a22-4631-4f90-89d0-08deb11f0f45
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;ARA:13230040|366016|4022899009|1800799024|376014|38070700021|8096899003|4143699003|18002099003|22082099003|56012099003;
x-microsoft-antispam-message-info: r1Wm24TtiQrwLeui1cIdP7WvOHe9m0Ya95A1ibrbAu25hKcikckDV2kB8oeOq5Qf1xucFReUMWAnVj3p6OTds9hzQ5g6iaFgVll1CkASMLfnyT2ylVtnm2rbKExO+0ZST+FmJhO94VW7BfUg3HaRqH5+Jsu3upge92fywnRxf21ptqlBTq7MD2ap9nHtzVZE+ScG9pC+tG13zhOdzJsG/YVZz4c2F6VL1JVGravBL87edXwOrqX03dKEDgXK7KeHCYUga4zj0sbg2EIGIhIL+hIt4gsdlhs2LXkmkQnGZCXW/pI6arSer5X+MParz03Q0OBrMXvYIEJjXIANfKhM2oNnqu3ZPkQHRP8U8zPaMVwuyVL4gbBcm3CYj1D6sao02knGPFVGBorYvwkxEaitrCSVOJADvn57SaZKOJ+fJCSL5Uva6c4lo1kC+yvstS1POXKyG1HvzUSICHtmrg/mwTuKVoi5MOv63jAy7WDO+Vu10narhdkPIQ3yu5OtIs0vLSvErRL1jkgwkbVusm3FgWNW8O/Oi6DbyoqRcqbUMInToTbYq5mHFs5j2BjAh6tktT9d4QbcBa5pZNZIR5WtnOhr2/B8hC9p78Sqb0YIPQ7sJHfH1HMI/xXrR0pvDuGgHstcFThvdRrjwYHGeIjJh6WYwar3ZmsxrMeQ9uFX2Qt3iWZimv736G4NEYZrTFzze3aSMukMz1uUgyK+uSZFyzaDvC8UtvQAmS4ibivwwaF2qaBP2ECIrcW6eUde+AjQ
x-forefront-antispam-report: CIP:255.255.255.255;CTRY:;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:SA1PR17MB5154.namprd17.prod.outlook.com;PTR:;CAT:NONE;SFS:(13230040)(366016)(4022899009)(1800799024)(376014)(38070700021)(8096899003)(4143699003)(18002099003)(22082099003)(56012099003);DIR:OUT;SFP:1102;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: AwrAOSEX3/Y67hc4pq6R0wAyvlXiO1juU+JDxwG4EvRuKfHIHkOx+lD+yF14MWzbkO+F1B1mAJxuxA6gSDqCze6z3HLBqFfDk4382eqRFDwvqF3rp1QTyP1gfgG9vviaxDnZ5VtlIe8BGJKts3Vy/d3veBgMcYyuXCTGagZLfLkcPn0aoH/5Z9JUfswBj2AjZferPDkHDnlaC5KwLAEzXUWfDi3Y9ndFAzoEwp/ThCObWf/192Hvqtcij2LJCE7dBBAOj8hh2K1UjPoC44vyKT7l/x0P7F0q1+SMFGdXDRHeabfCGhLgeWDWOopKXFaFqozc0Ih/W4B71L4hOzk/iZzMVOP/iN0PuM4mk3iWrNhYSb4CoYnWcuDFrxqb1uC3HigTjFwm0T+dSR/R/qowHcy2o2VQlO8YAFH2P51+kC6UVK9Jqlk0LVFHZ/s+A9MceKJP4yXF+O+BOhzyjzl31DiBKaUYAGUA3t0g7ODfedhpIPTlzNpoDQOuw/cam0CqnG4xaZLu2q6IRYtD7IrRyHl9QbfDGxd9wmH0+PEZqs8VC4JivbXje9kQwDryIJ3Luh1xxrIDNPmVyz8rwgB0wvspKTCUug8FvBl4VYJfmk0RySRxROoFKWL7T3IY/U8WfLKuvR7TFGG7Y7rqkkV0oLcBeTxBh5GK7s202enqCgGh++FX7CRqyzORfA1tjJWBuZir/U4fjlvUB/ag7pkU/mY3gZcSD1Dmjihg4PZl8ARvgCaQbl6iztNAJ91qUESyQUT34kfho61jpa2Zt96Kg3RMl9TjAhZ4076xMKiBRX+F5lU/8SGJB4+BU+lKfH5xHFXq4uUPz1KTXCFm+Aiqv5xKpK9kFD7b1bfpABEMN0BJhZOhwpx6KcvclrJe0uavrbhbv7BTiPIki/1VKG2yiiZ94zrivSj5vJjg1ILY5cH/J16hgZB9EiNwyczjPVDg16TTFCWjHvO4RvYzWj0IRypdFzIHQSg36tiR+hAkozgK8HWC7B7jOgfc3JIPQfWzLosRM3DDm/1AdSd8QMtaoDFHVyVpWAQyKhxNJaPng8g/HJ0WSDSQHbsichq9KDY3Gm5aKIsjXqhI4GqPNlj+m27utw+3NM4SAAPMOjUIZ9vuTe+2no9WUFhZzQHnC3diMilH7OBFYuxFxBoKRan3E4+qQn8ypssSQ7KgS7OfeEpsZsvv8gGo1AYdsM5mAMvlCjPySs/e7LzOmwggp1j9SNqRuIbmySYXy8VwC6BRPNHdVoBEM47BzdqdS7UymnQhCMgRtLU/eJJdgslhj6d9j6EDK34AK1kjEOGi2DRuxdDVeA9kGjg8736ZfNHpvPzFBDCzbNozgG8HZZrEYYgUrK+yvFnn55bQdSru63PawMT7TdsQv54bP4ZDdW+2fTFlu5hrYbs8exY5x6dlT3ng9dfFeLK2pjQdrX7YWQwr6HLDqbt4dKQmpz6zrFqYJFSNKWPKhH0qQjrn8duulSWiZeoNgsYlK81uX5hpi5Va8Cn3SCYOH7CJUkVgfvZcte1KlRt32nxtoVaa4/9d89CDddQ1jeRN071V3uRKnR3T2LZ6tWKBEfT21QZESp/rQajzhxCjB/W0UZYcGfAnYwFgMMc5BiDerOGKaQzMMiEgNYqPo6fZovvBGVAm0SC07XLjLoamtJWnGIdxGHUmVxgCeqigMld4iswROYYKxcqextuT2IN4Q36y5OrSAKmap29o/xNxQEoNQJ9BC/x6gNEWqQ==
arc-seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=mjaCF8ODbeTT6Uhk7LzObqMKBDbhjQBO7fzdbk5BgoyQ/VrGrjaDNcylToFM7goLdjlzqkW/hJK06HO2IETL4Q02+DxBAYiLRBCvUAkF2H1PmbfiNq1f1Ro1Jvxbj1Rwu+7gGHIgNlxm027QSR1gJ89/gDRpeYjsyoh/0x9+MVgY0+BSXY7y1YCWwgezRyqaezT72qpvdAgZnq+SyDH7QpD1WU43srTLlXZaSwe5Aa5jdu9kySFxkiEkhnwRBn+/MOFPZbvPqadJhWhdSIUWYntsNXznFK2bu5H7GwR4BkuoAr0QIYM7tlGVGo+3R5EZ9PvrGltOslr5FTOkAVSGew==
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=7ojUrQNiu9n/pHIE4WjwGFfkSmqOwTtiRCztjxRBZEs=; b=UnE6cRm+Y/yo2iIqrZ9y4wER4YIODOW+kiorogRh8Uth8jG9+2nfZEmJ2E3nC7PMU/zpC5zm56U2OgCcAkZeRGpvqVffEETlChm4Q+GDQHQ+wJxznHpCJb/jjBrJbbjLmllJghxXbV0R/fEoZUVKRBiW681saXj2yCkpZOUtecKTxfMFFw6XgyB4OQmgaExthdq6mXJNAYzmu5C0Qn5lpdn7V7HQKjrKSgr00CN5IQWcUDDMzLdorX4hVcm1rGsrc0Jf+OrV7mguLsBnaFjkFoWNiJbFYyk8fMejBhRkf3XqTm+SkvW7iJBVzZcsvn/vs88HAH6qSHdHQN06y6S6yg==
arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=akamai.com; dmarc=pass action=none header.from=akamai.com; dkim=pass header.d=akamai.com; arc=none
x-exchange-routingpolicychecked: Yc8fkDdm5C3XhGsn//rM87N4h36WL/1tYVs8DNoI2srW3qxcIGTjVbOotPTVIIpdYa7wS5u7YIfKrMuc83q6vJWMY/m0G//O74zWQp4tFDQvrdMG7jjmh5wLEVDjN/ir/8dQOcfwLm6dV5ZCYrDBFCir+vAnG9QQwPQs1c2hwNsMuewsx3/Q7SylqRsioxZKnKlYr9k7PKcSzIMvsCTMcM+Tb6W1d52a5ZkcQoNqA0mF12vqM+8pdinXzlqBcJW4mzpMXxbDokoJePULLW2J1B57X/J5ZaxSGIUVpzRS36KJDDnWi+8AbQEeMLexSnmer9IsWoGi7uEMSSYrdRZ+7Q==
x-ms-exchange-crosstenant-authas: Internal
x-ms-exchange-crosstenant-authsource: SA1PR17MB5154.namprd17.prod.outlook.com
x-ms-exchange-crosstenant-network-message-id: a62d2a22-4631-4f90-89d0-08deb11f0f45
x-ms-exchange-crosstenant-originalarrivaltime: 13 May 2026 18:40:09.1003 (UTC)
x-ms-exchange-crosstenant-fromentityheader: Hosted
x-ms-exchange-crosstenant-id: 514876bd-5965-4b40-b0c8-e336cf72c743
x-ms-exchange-crosstenant-mailboxtype: HOSTED
x-ms-exchange-crosstenant-userprincipalname: Yijw2nrWiIPbxInD6c06C9svsrwN/Deue7yHXAY8ZwtYngQXXuNa8mNc0HOP+kBl2gIuss28ScWZa67MafbtRg==
x-ms-exchange-transport-crosstenantheadersstamped: SJ0PR17MB5111
x-originatororg: akamai.com
Content-Type: multipart/alternative; boundary="_000_SA1PR17MB5154A7CC62CB1EE43CCC05F8DF062SA1PR17MB5154namp_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1143,Hydra:6.1.51,FMLib:17.12.100.49 definitions=2026-05-13_02,2026-05-13_01,2025-10-01_01
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 lowpriorityscore=0 malwarescore=0 mlxscore=0 adultscore=0 bulkscore=0 mlxlogscore=999 phishscore=0 spamscore=0 suspectscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.19.0-2605050000 definitions=main-2605130184
X-Proofpoint-GUID: n33hc_kPfne4pKZWH_6XPuPHH0hjCwGe
X-Authority-Analysis: v=2.4 cv=aqaCzyZV c=1 sm=1 tr=0 ts=6a04c58d cx=c_pps a=StLZT/nZ0R8Xs+spdojYmg==:117 a=StLZT/nZ0R8Xs+spdojYmg==:17 a=lCpzRmAYbLLaTzLvsPZ7Mbvzbb8=:19 a=xqWC_Br6kY4A:10 a=NGcC8JguVDcA:10 a=VkNPw1HP01LnGYTKEx00:22 a=Ifg-1AOnLHOf1gn6spyb:22 a=KDzEjHMMTas96-nIEKpj:22 a=NEAV23lmAAAA:8 a=48vgC7mUAAAA:8 a=X7Ea-ya5AAAA:8 a=9qxNCY_qAAAA:8 a=XBiue53CNqVYatJKMvsA:9 a=lqcHg5cX4UMA:10 a=QEXdDO2ut3YA:10 a=tqdMzFhGG8mD8GCBlf4leDhY3gs=:19 a=WHqFPFZ7wym6-z2G:21 a=_W_S_7VecoQA:10
X-Proofpoint-ORIG-GUID: n33hc_kPfne4pKZWH_6XPuPHH0hjCwGe
X-Proofpoint-Spam-Details-Enc: AW1haW4tMjYwNTEzMDE4NSBTYWx0ZWRfXwu9M3ndjx1uK VeC9BTxWov7mXDMjPJRmBysYTlcKzDuLOmb5HAzm7cM2KYX6sFB2PpEd9lBAzq6wDZ0wnh0sbrO vRakvZBmkBBGUeVZ6IkTGK/W3RzunE5Jedzbyis8msRPNxJR8f6o2mb3N/jI+LVyX3nf/qQZCAT rOwInJLcP9oKe/rZuOR6iHeZqGicmvcOtoKmB6HzRvCqKdVkLngyZb523FeXRg4CEHIE3UuaGQh cn+hp9xFabhGhs+9qNJslfPNCdRMUsrxjFR+wXRK4SCvC0BM+gr+J0mk+i58xDw/dGw0TGSq+qw 8UE8qqhvksAj8hkeUHgSNitjRYA5soj5vcWCH3PYJWCcLKnfG1Mg/BJk6COT3Sv03NPwj7edlUs xLxTp3rYj/IIiU9XWBW92n7zeYZloIs5twTn1lKYuqBRyutYHEtKKzbENpa5yK6LyQnRmsLEZ4u UPFKPK+35fm7AuMah4Q==
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1143,Hydra:6.1.51,FMLib:17.12.100.49 definitions=2026-05-13_02,2026-05-13_01,2025-10-01_01
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 clxscore=1011 malwarescore=0 phishscore=0 lowpriorityscore=0 adultscore=0 impostorscore=0 spamscore=0 bulkscore=0 priorityscore=1501 suspectscore=0 classifier=typeunknown authscore=0 authtc= authcc= route=outbound adjust=0 reason=mlx scancount=1 engine=8.22.0-2605050000 definitions=main-2605130185
Message-ID-Hash: NJJHSN4FSYDCX7THYZFGGVTIM67RO7CH
X-Message-ID-Hash: NJJHSN4FSYDCX7THYZFGGVTIM67RO7CH
X-MailFrom: wilaw@akamai.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
CC: "Yu You (Nokia)" <yu.you@nokia.com>, "moq@ietf.org" <moq@ietf.org>, "Mo Zanaty (mzanaty)" <mzanaty=40cisco.com@dmarc.ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Moq] Re: User case or question to Joining Fetch
List-Id: Media over QUIC <moq.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/moq/iSSdAC0ltsshC5Ax9ZfSGDcgfoE>
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>

@Zafer - "Using milliseconds didn't help, sometimes the group IDs collided (when a join message is received by the participants in the room, they send a join message at the same time which results in group ID collision)” - but if each participant sends their data on a different Object ID as I proposed, then there would be no collisions. The cached entities are Objects, not groups. The tuple of (NS, N, G-ID, O-ID) would be unique for each user.

-Will


---------------------------------------------------------
Chief Architect - Cloud Technology Group
Akamai Technologies
Switzerland
Mobile +41 79 535 07 94

From: Mo Zanaty (mzanaty) <mzanaty=40cisco.com@dmarc.ietf.org>
Date: Wednesday, 13 May 2026 at 19:02
To: Zafer Gurel <zafer.gurel@ozu.edu.tr>; Law, Will <wilaw@akamai.com>
Cc: Yu You (Nokia) <yu.you@nokia.com>; moq@ietf.org <moq@ietf.org>
Subject: Re: [Moq] Re: User case or question to Joining Fetch

This Message Is From an External Sender
This message came from outside your organization.

Hi Yu, we built something similar using the anti-pattern Zafer described. It's an anti-pattern because MOQT says such tracks SHOULD NOT use group range filters at all (in any fetch or subscribe). See section 2.3.1. So there is little to no chance joining fetch will evolve to make this work well.

The n^2 problem you describe is inherent in all full mesh designs. The overall state required dwarfs joining location, so that is not really the bottleneck. Alternative designs often add hierarchy to avoid a flat full mesh.

Regards,
Mo

________________________________
From: Zafer Gurel
Hi Yu You,
That's an interesting problem which I also encountered while developing the Meet application<https://urldefense.com/v3/__https://github.com/moqtail/moqtail/tree/main/apps/meet__;!!GjvTz_vk!V2MZ-NZlwq45uDing-dR4eMyQfhK9AY7DiCv6D3ivD4ARq_-6Rj7JVyGPw5Ad1loB4XZxbCQrwnUxxM8apNAQ2PX61kA$> within MOQtail.
But instead of a shared chat track, I used a shared signalling track to distribute messages such as join, welcome, etc. among the participants.
Using milliseconds didn't help, sometimes the group IDs collided (when a join message is received by the participants in the room, they send a join message at the same time which results in group ID collision). So, I ended up using a random base group ID to start the group ID counter for each participant, which solved my problem. But this is an anti-pattern because you don't get monotonically increasing group IDs.
Best,
Zafer

On Wed, May 13, 2026 at 1:06 PM Law, Will <wilaw=40akamai.com@dmarc.ietf.org<mailto:40akamai.com@dmarc.ietf.org>> wrote:
HI Yu You

Interesting problem that you surface.

The shared chat track seems intuitively more useful, as all subscribers essentially want the same merged chats, sequenced by time, not for each to have to merge 100 different chats from 100 different participants.

Solutions:

  1.
You could deploy the equivalent of a Multipoint Control Unit (MCU) , that subscribes to each of the end-users published chats and then produces a single merged track to which all participants subscribe.
  2.
Or you could have each participant directly publish into a shared track which all participants subscribe to.
     *
How to avoid LOCATION conflicts?
        *
GROUP ID is wall clock millisecond. Object id is a participant ID that is allocated each user when they join the chat. The Group ID orders the chats and the Object ID prevents collisions if two users publish a chat message in the same millisecond. This scheme assumes that an individual user will not publish faster than once per millisecond, but that can be enforced by your client app.
     *
How to do a JOINING FETCH to start?
        *
Since the GroupIDs are wall-clock time, if the client wants the last N minutes of chat, it  does an absolute JOINING FETCH, which starts at NOW - N*60000 and adds a  SUBSCRIBE for future objects.

Cheers
Will


---------------------------------------------------------
Chief Architect - Cloud Technology Group
Akamai Technologies
Switzerland
Mobile +41 79 535 07 94

From: Yu You (Nokia) <yu.you=40nokia.com@dmarc.ietf.org<mailto:40nokia.com@dmarc.ietf.org>>
Date: Wednesday, 13 May 2026 at 10:21
To: moq@ietf.org<mailto:moq@ietf.org> <moq@ietf.org<mailto:moq@ietf.org>>
Subject: [Moq] User case or question to Joining Fetch

This Message Is From an External Sender
This message came from outside your organization.

Hi,

While implementing a conferencing PoC over MOQT, we identified a use case and would appreciate feedback and guidance from the MOQT community on how to implement this in a MOQT‑compliant way.

# User use

The use case concerns multi‑participant text chat and fetching message history. In a per‑participant design, each participant could have an individual media track (e.g., video) and a chat track for messages.

Participants would subscribe to each other’s tracks under a shared namespace (e.g., room1). New track information could be discovered via SUBSCRIBE_NAMESPACE.

The media track is live, so new participants likely do not need to fetch past video objects. For chat messages, however, it would be useful to fetch past messages before receiving live ones, in order to understand the discussion context.

# Problems?

Joining Fetch is designed to do the job. However, it appears tedious for subscribers. More importantly, the relay must track starting locations for n participants across (n-1) chat tracks. Because this state must be tracked on a strictly per-subscription basis, a relay hosting a chat room with n participants who are each fully subscribed to m distinct chat tracks must independently manage n×(n-1) downstream subscriptions. Consequently, the relay is forced to track and save n×(n-1) unique Joining Locations in its memory to properly compute fetch ranges for all participants across all tracks.

# Alternative hack

Alternatively, we anticipated a design with a single shared “chat” track to which all participants could publish objects. However, this approach introduces the risk of GroupID/ObjectID collisions. In addition, the relay would need to deduplicate objects before forwarding them.

Even if the collision issue were resolved through ad hoc mechanisms, it remains unclear how Joining Fetch would operate with multiple publishers on the same track. Would a default Starting Location of (0,0) be sufficient in this case, or is a different mechanism expected?

Thanks.

Yu

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