[Moq] Re: Way forward for LOCMAF
"Law, Will" <wilaw@akamai.com> Fri, 13 November 2026 17:19 UTC
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [67.231.149.131]) (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 CC7FB46 for <moq@ietf.org>; Fri, 13 Nov 2026 17:19:13 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=pass header.d=akamai.com header.s=apr2026.eng header.b=mC47TVVO; spf=pass (mx.ietf.org: domain of wilaw@akamai.com designates 67.231.149.131 as permitted sender) smtp.mailfrom=wilaw@akamai.com; dmarc=pass (policy=reject) header.from=akamai.com; arc=reject ("signature check failed: fail, {[1] = sig:microsoft.com:reject}")
Received: from pps.filterd (m0409408.ppops.net [127.0.0.1]) by m0409408.ppops.net-00190b01. (8.18.1.11/8.18.1.11) with ESMTP id 6ADCeA7R243785; Fri, 13 Nov 2026 17:19:08 GMT
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=RGKpuPWxrxA8QtgY6APp1F mQ0CZH08ScELcosD+WKxs=; b=mC47TVVOoM0dda1bDzrCMBrwORBMVEJOVDvQI4 TSDLbDgIe0gl6TdjA+0QsbFX+YjzcDAqLQpvQcO2lyzHkOCzZpavITjGq2nCi/s6 +y6tXWuCHpkR3ccQ6QiQwrqydI84YCJ5LztsScPo9D8TQ5UgZpD2VrIEpx8B6fTv iyTFTwLXWAo8c9LUvQLAFtOZJjbYFh0nRz4Pa7cYItlr6EOKQ4F2AI3ET3LF25JI HKzq0QXWAuFpABaMF7Lr49bV7DAxO2yBuxTNtumI3tMh14KsE3ST6hS6npL4Lt9M WhQaBiN4BQV/TvxGhm033PHk7yidsQcjb8yrSb9oXJCXTk7w==
Received: from prod-mail-ppoint7 (a72-247-45-33.deploy.static.akamaitechnologies.com [72.247.45.33] (may be forged)) by m0409408.ppops.net-00190b01. (PPS) with ESMTPS id 4hwhg3dh1h-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 13 Nov 2026 17:19:07 +0000 (GMT)
Received: from pps.filterd (prod-mail-ppoint7.akamai.com [127.0.0.1]) by prod-mail-ppoint7.akamai.com (8.18.1.7/8.18.1.7) with ESMTP id 6ADGpPpn028036; Fri, 13 Nov 2026 12:19:07 -0500
Received: from email.msg.corp.akamai.com ([172.27.50.221]) by prod-mail-ppoint7.akamai.com (PPS) with ESMTPS id 4hurjykqt2-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 13 Nov 2026 12:19:06 -0500 (EST)
Received: from ustx2ex-exedge3.msg.corp.akamai.com (172.27.50.214) by ustx2ex-dag5mb4.msg.corp.akamai.com (172.27.50.221) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.2562.56; Fri, 13 Nov 2026 09:19:06 -0800
Received: from ustx2ex-exedge4.msg.corp.akamai.com (172.27.50.215) by ustx2ex-exedge3.msg.corp.akamai.com (172.27.50.214) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.2562.56; Fri, 13 Nov 2026 11:19:06 -0600
Received: from CH4PR07CU001.outbound.protection.outlook.com (72.247.45.132) by ustx2ex-exedge4.msg.corp.akamai.com (172.27.50.215) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.2562.43 via Frontend Transport; Fri, 13 Nov 2026 09:19:06 -0800
Received: from SA1PR17MB4545.namprd17.prod.outlook.com (2603:10b6:806:1ac::16) by DM4PR17MB6295.namprd17.prod.outlook.com (2603:10b6:8:109::16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.21.615.10; Fri, 13 Nov 2026 17:04:00 +0000
Received: from SA1PR17MB4545.namprd17.prod.outlook.com ([fe80::ef44:377a:d20a:e3a3]) by SA1PR17MB4545.namprd17.prod.outlook.com ([fe80::ef44:377a:d20a:e3a3%5]) with mapi id 15.21.0615.009; Fri, 13 Nov 2026 17:03:59 +0000
From: "Law, Will" <wilaw@akamai.com>
To: Torbjörn Einarsson <torbjorn.einarsson@eyevinn.se>, Magnus Westerlund <magnus.westerlund@ericsson.com>
Thread-Topic: Way forward for LOCMAF
Thread-Index: AQHdcrKbOqJp6xOZuEq6NLCzEjNzIbcsEYy+gAAT1Dk=
Date: Fri, 13 Nov 2026 17:03:59 +0000
Message-ID: <SA1PR17MB45450BC0A690854EFEC75F7EDF7F2@SA1PR17MB4545.namprd17.prod.outlook.com>
References: <AMBPR07MB10639BA287E1635DE9C1F652095702@AMBPR07MB10639.eurprd07.prod.outlook.com> <GVZP280MB608026E804930DA7D07BA5CB8DE87F2@GVZP280MB608026.SWEP280.PROD.OUTLOOK.COM>
In-Reply-To: <GVZP280MB608026E804930DA7D07BA5CB8DE87F2@GVZP280MB608026.SWEP280.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: SA1PR17MB4545:EE_|DM4PR17MB6295:EE_
x-ms-office365-filtering-correlation-id: 55c3118a-bb48-49c2-c273-08df41a81c8e
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;ARA:13230040|376014|23010399003|366016|1800799024|38070700021|10067099003|4143699003|56012099006|261022105027099003|261022075727099003|261026140227099003|261022115727099003|261026121527099003|261021135927099003|261021121427099003|261022113327099003|261028144727099003|261102123227099003|261021123027099003|261009223027099003|18002099003|22082099003|13003099007|8096899003|3023799007;
x-microsoft-antispam-message-info: hdmRA7W8SLELYxKnhMHoGRaEwAjdflSfmFZcKs9YfCRdhjNKTw9HULuEB5Au6I27r/43icyrgCWThcaxaGfEwyufH36UkBlvg0gfH6nhU5d1VibsFiIZgpZdiC5J8yVDbK/p2YX2lNOfHyJt/lKnPocrfDzyIGlXcO8TxfG0lJxPGd7fz61whyS565X4Fpj/ETJIbM2Odj3pT6yrEBQnsolKQ4dnnt0og5ccTxAf/UPSheaVapU8SsHXhP4kFmvjGuHeAp1ju9wwncr1UIi/GcCU6l5tfePrTGUrj2g0PRTHGX95W5du+Ngf5jLMd2g05eRzNNV4GG7ljJbMniBqXgXEYAHoBfoCPkt4Rkegem0IAvrcJbyWZ1rNy2fkxdvqfWLDJ5LjD4NLivrQ5+jfDZL2lE1bZrkjDN/tkgNLVmCh172TyrIqRlfYRNhBjRAojKuV/55hSRBRTWAhHgBNA4UaPmI3az24/4o4rhBdC2PIu+SkFuaWuUh7NRDfGbMjFtGipRgIl+umZ4DrhOFFX63FVpQMljTCCg48qTMA3cKUAu127atIz9d+dEQJCcLSzTKN59F6LA8hof/4lbOGgzdx3FzRg/EaZFQEV7xpq3HKksZG5NrcClPV7jKnXbYQbEPaeDUMLb2iJ6Ghhskr/18x70uaGj45DCZ++y8GL3U=
x-forefront-antispam-report: CIP:255.255.255.255;CTRY:;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:SA1PR17MB4545.namprd17.prod.outlook.com;PTR:;CAT:NONE;SFS:(13230040)(376014)(23010399003)(366016)(1800799024)(38070700021)(10067099003)(4143699003)(56012099006)(261022105027099003)(261022075727099003)(261026140227099003)(261022115727099003)(261026121527099003)(261021135927099003)(261021121427099003)(261022113327099003)(261028144727099003)(261102123227099003)(261021123027099003)(261009223027099003)(18002099003)(22082099003)(13003099007)(8096899003)(3023799007);DIR:OUT;SFP:1101;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: L/Gtzzj39tlzFYzsZ/ApwCmhuBJEoDu0VR+LpP1Au7hiWtDzv1cq7HhoiBy28B6aKeVTtSD/B+uTZiOupKk2Okn8rLF4+jzASOBw+J9LmrRuDQmVI9gqaG6m1ehgxJT99hOB6xXR7xoBBaEZ+RjYWsiRzmzkAZLoVR3PEqTUg8voAeqkLRtYrsP9WAnkUsSWXzaJRaYaX5RnazAluGVm6gZQYR0pNaZvNRrmBhqDihwLoXGz+z3/151PcZdwJ3QDLalcrqUPcuS4gaBebTgNj9HJcT/GNVQKsOCaIQe5h2AYnWIul8w07d9h2o+5DuPicI/+QjQEuK3rCNR8d0mYAyLbOAAXvERC9/GIGB/NhIQg/MRzFn/JBFyOZgBKLX7BS1LgW55/PJLH7Fwz/boq30DBD9g6mXobbua7Pf1KWD1OmNOG4YsryEv8A4EoPy42G+t6SEvvDnweEbpRlFYaRLRFUmvzDXbGgVG02fb1Msh+D7YILLaOo/VelJvuLQpU80Z+lRdTBxCDnSapxRUIj6OKx3lQWOsbJ+G6cLYUBuC3VIscqMzCp7imskiLZ7wNnCRvOyqPpzc7TvAvnfKX4Io8kUHOTb6hzhx4o+8dUQFOCfGa2DejPvREOokrojii1Tw6RqtMkFqc8b/hjQUax/KCjk3i3G0zqFlu0SraPVAYFeMkTwFCXsebWJ6HkemT70KJJXff99dXJWXrxN4qHaXI8k4y252P9fRAeZVKr9boM+AcF3Ztpeq2FT8q7slBbJAS1QM9RZbCMCIkC2hyE6lF3+vWyzCELH6vKUijq9TLc4wDIHTR0wYHtC/M7vSjE5BB4WoqE7eIhkpepYgtHvArL/+ktnsKjZKMj8b0aAMCN2jdpHb7ZdsTMQxmQBb51EcYmfjNVW930GtH8Brl4kkAPP+gM0fjnMv+oVLeuelIigfz102STxwQm0oAOTUJHys6FcLnBrG2InI+5KFjOVkYnbLJdUnycguuVcqniVCgKwAIS9KFtHBxSWXklpVpVHiCALx8rpO1vRM0Pta42OmtUl000gOVkK10XzEsT+l8R39Q7rEbZWdv/sGckNkQ+Mi1Bv/+OTXIqzvA/W9lA+T5v4CfO0PONekEZechuUtfWlnw/d1tZVnrNF2Q42x30MVfASKBomvXRfiNoWvgjD9l06TMi9zCp9hkEpXuybGwS2gqHy6apYp8IsGUF0P8GvjxnmEMYbXOzqMDV4hs9p9svXMzQLLuYVEHs6eVOR7cVkZyJwB05yPDrOJ5Rs0JdUec13gP+MF9WNIxyxp1eEWQrS6h4X+F02vDtyiVP4DcFwyw4Sz1LmVHdfZUNAtav23m0jwNhgNQI/Vai3aqSPErNF4vQ1uq61QAzX4dWS8Q3CLGJmOAhNlJYn8uTZLlChzgpI0fcqQYNo+bffGTS7bYcItuncYAU3XvGSzTIgMC4vXXGQvo92pxhReQDr+fxNmM/6mAuzVICtI7HH623TJJGki4Pt2x8RQClknDUccO2XpPNuYMzaiub435zUco3JFob+uYeJJVMU6OSZMoGcZSAWzlhN3Ae7isjvlmJNbtaK/rWj9vJqlfqlrILX+QyJAEqo+CVMwhhor1cPzGP9iLbe/Uh+imRng2uew6G96xJBkrsmNSM4LTreYH4b7W3fFteOR2pSg7ntpP9nfTq27dAjIJN8YTgwxV7YFHPDjU9lWg2gFMV7cJf3qW0hV6E2hV68FgPV9JoSPP4ZIQUg==
arc-seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=uOm2fhFrSsyVFi60ftHIpSmlBZOoyD4zT4U/1NpkZnZyfhh79rdmp4alRvpDecXwphIZ96Txb0G438vAejB3x/xXutAjdkqYZLpUh8wPWQSgKQvf1ZUm6Md5Lb/J/jtY25X3ag7JebqRhHzAi8N5Ixzkx1j4rkaokGHYTlmcFklgCskg617lsDE44NwXiQgmEyHIay1ecayJ5ry9atgEYfIcY3J02FqoGdCs5CTJz68RMQFM9B39Zo5yirsEl/FyEEZs6OO3gvDZuSSvZ9SMpoLkcEBRLzaBIkKdcoGT3unnvYATL0RIu1qPtzIAy4QpheA4hi2j8V94UMGzMQkD3Q==
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=etCMvZ3W9a+ugx7LXnlyKJGc0j361yj6GWYhAcekytg=; b=LJ9WCqYirecejbuSb1cBcGTg8ngfAUL8miZtNi8vALJL29Eo1KYDXG1jP+5sip/obsBZqauKp8YvgDC1KE+VUaStv/xVx5aZUqkKCTRiQLGpyzxfbm5HaE0u10dR+iSu6z3+HQ5gPMZG4igDTEsYQonB6PMSXjtObsbIUz6GNsaMRgTfqV0opYFwpDkZqNmrm0TKyu/3WytsZEed0wy0rYHMtREwh+IdNOo2A2ocPNVkYkJWTIu8J39qKzhx0DUOx1IdXLMSljIC9cE9yv/qLJzfKwyLgzCXbLwXQuNH4ks2QIMibWZAHOKNed2RUf6O9vTBpEpAjzZIAQ94+Bq2TQ==
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: RwstI0NbbaBrpwNXkuTkv3NHqI0b2ZTx1ljOZ3LIaRme9ZRf25yYJJp4pxT6TM7ZAFSxK/Q45W57vaP0MT/epzPgoBi7Us273vZkntTRy4dmTOg5XxF/M9ucI1j9t234GRro8277kwEc6ppYVukkN9BCCMXEnKew0pIV5tqq74kO5zvMD54MnukdThT0mNleDL1rExr2BAHnxA9fVsU2Ipn0g8kHABQEdT6YX/xXtWVSWdRHLVHR57GkQJNyeSMl8KDxK42alcjMKNL47aQkNStynCBWIRZ7xyK/GEp7yJpJUKlGcD85tot7fhapQmIr0sgbITirVWTpGUuXq0aBzA==
x-ms-exchange-crosstenant-authas: Internal
x-ms-exchange-crosstenant-authsource: SA1PR17MB4545.namprd17.prod.outlook.com
x-ms-exchange-crosstenant-network-message-id: 55c3118a-bb48-49c2-c273-08df41a81c8e
x-ms-exchange-crosstenant-originalarrivaltime: 13 Nov 2026 17:03:59.8933 (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: iw7ofdyXizJ8xOSn5cx/iIqY1ZACw8sSo9T/9CQHRwYDl6SrEuIUje+SCTusEuzlfTm5tcpdNPZuvHz1WXwY7Q==
x-ms-exchange-transport-crosstenantheadersstamped: DM4PR17MB6295
Content-Type: multipart/alternative; boundary="_000_SA1PR17MB45450BC0A690854EFEC75F7EDF7F2SA1PR17MB4545namp_"
MIME-Version: 1.0
X-OriginatorOrg: akamai.com
X-Proofpoint-Virus-Version: vendor=nai engine=6900 definitions=11965 signatures=596817
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 malwarescore=0 bulkscore=0 phishscore=0 suspectscore=0 lowpriorityscore=0 adultscore=0 classifier=typeunknown authscore=0 authtc= authcc= route=outbound adjust=0 reason=mlx scancount=1 engine=8.19.0-2611040000 definitions=main-2611130067
X-Proofpoint-Spam-Info: AW1haW4tMjYxMTEzMDA2OCBTYWx0ZWRfX1bGLF6F7aIyw 0alYoMFbIJg8B1mqnuPgJr3iy4cb+Qtcem3i+DteyHx9r/k7VPBR20RiPZ3jkb8vr7dgKuODUkX 9BFLZTdupgpPXFvknQruSm/oHbCiMMY=
X-Authority-Analysis: v=2.4 cv=Wvy+otfv c=1 sm=1 tr=0 ts=6af7468c cx=c_pps a=3lD5tZmBJQAvN++OlPJl4w==:117 a=3lD5tZmBJQAvN++OlPJl4w==:17 a=lCpzRmAYbLLaTzLvsPZ7Mbvzbb8=:19 a=xqWC_Br6kY4A:10 a=zJRp6_cAMcgA:10 a=VkNPw1HP01LnGYTKEx00:22 a=Ifg-1AOnLHOf1gn6spyb:22 a=BYUV7c42er6_Rx9bq0XK:22 a=48vgC7mUAAAA:8 a=0FD05c-RAAAA:8 a=IlDeifMY1sDacge-8K8A:9 a=pILNOxqGKmIA:10 a=uR4UCgkGsDRazcPe37MA:9 a=tqdMzFhGG8mD8GCBlf4leDhY3gs=:19 a=iz43KoZDErjiRJfS:21 a=_W_S_7VecoQA:10 a=l1rpMCqCXRGZwUSuRcM3:22
X-Proofpoint-ORIG-GUID: FY1cBSAQSS3p8t9ZCOHXrJ4S_wOtAgix
X-Proofpoint-Spam-Details-Enc: AW1haW4tMjYxMTEzMDA2OCBTYWx0ZWRfXzR3/edrZ2enq oBuBD/YO2DsjizYWahztSy6IzpPZxR9zT6po4S0BvhUWbl1k1FURGwR1mYLNDrcJMSHPx1SI8A0 3p0UC9ldfyXvJTD/qTgLrKxBXymfsWDMRobkWLXp4rQkr0Ke4l+Yfigad0eAmwKxl1tPV/Sd0h0 GYHvRZlNq+B0hITlS20XOikhL+kfZJDL8+zI9rs7GDkrfYS1zxQsuIH+A2BbSEi4y1CMKvGa53G zBzE+nwAGvc7kyeBNTxHJjZNT9RyyCLWSaMTIJz8gO1e7Rk2LtGvtKcX495r/Qx02qSTimmFdgi SfiLvfxXZtZTOvhyoxms5J8ZxX90Av5+rnc3TLFTr6bSt70/HsthhQW95GYpQqYdNqxfPzqe3XK AArNZdQ/tHqED13vqLpI4wcNROsnTIz+UEMp9SjgkJFQAVjV7O8Nl6r+iIzppy1iZPYugDVcOZ4 Ta5oGvIGDhdpVSixkKg==
X-Proofpoint-GUID: FY1cBSAQSS3p8t9ZCOHXrJ4S_wOtAgix
X-Proofpoint-Virus-Version: vendor=nai engine=6900 definitions=11965 signatures=596817
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 phishscore=0 lowpriorityscore=0 impostorscore=0 clxscore=1015 bulkscore=0 suspectscore=0 malwarescore=0 spamscore=0 priorityscore=1501 adultscore=0 classifier=typeunknown authscore=0 authtc= authcc= route=outbound adjust=0 reason=mlx scancount=1 engine=8.22.0-2611040001 definitions=main-2611130068
X-Spamd-Bar: -----------------
Message-ID-Hash: 7U5DPNZZPIUDQKUO6TAX6NBAIXFSQEJD
X-Message-ID-Hash: 7U5DPNZZPIUDQKUO6TAX6NBAIXFSQEJD
X-MailFrom: wilaw@akamai.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: Way forward for LOCMAF
List-Id: Media over QUIC <moq.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/moq/FLny0Zcv-rQEaahXp4nTfdZlU60>
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>
I also support the pursuit of LOCMAF within IETF, for the following reasons: 1. I am concerned about the default IP policy of MPEG. The IETF’s default culture favors unencumbered technology, while MPEG’s default policy explicitly allows RAND royalties, so moving the work there adds licensing risk with no technical benefit. 2. A complete specification of LOCMAF exists, with three implementations, including two independent ones. There is no need to spin up the proposed joint Ad hoc Group to do a study to develop it. 3. If CMSF normatively references a MPEG document, then we are dependent on an external MPEG timeline (which we do not manage) to advance CMSF to RFC status. 4. LOCMAF’s normative output is byte-exact CMAF, the compact form exists only on the wire, and CMSF can scope LOCMAF explicitly to transport so it never shows up at the API or file layer. 5. If MPEG chose to produce a future low overhead version of CMAF (without duplicating Torbjörn’s work), then we would welcome that and would introduce it as a new packaging format within CMSF. MSF (which CMSF extends) defines an IANA registry which allows new packaging formats to be added. LOCMAF, as Torbjorn has pointed out in his reply, was developed as a transport optimization for CMSF over MOQT, not a general utility file format improvement. We should continue the work within IETF, which is its intended scope and application. Regards Will --------------------------------------------------------- Chief Architect - Cloud Technology Group Akamai Technologies Switzerland From: Torbjörn Einarsson <torbjorn.einarsson=40eyevinn.se@dmarc.ietf.org> Date: Friday, 13 November 2026 at 15:43 To: Magnus Westerlund <magnus.westerlund@ericsson.com>; MOQ Mailing List <moq@ietf.org> Subject: [Moq] Re: Way forward for LOCMAF This Message Is From an External Sender This message came from outside your organization. Hi all, Here are my thoughts as the author of LOCMAF. LOCMAF was designed as a wire format tuned for MOQT and is reusing its idioms. It is aimed at very low latency with one or a few media frames in a chunk. When there are many samples in a chunk, like a 2s segments with one chunk, standard CMAF is fine. Regarding IETF vs MPEG, I thought that one may draw an analogy with RTP, so one could argue like this: LOCMAF is to CMAF over MOQT what RFC 3640 was to MPEG-4 Systems over RTP: a mapping of an MPEG format onto an IETF transport, written in the transport's idiom. It defines no new boxes and changes no CMAF semantics; the receiver reconstructs byte-exact CMAF. Its efficiency comes from the transport — MOQT group boundaries anchor the delta chain, subgroup ordering keeps it intact, Object IDs reveal loss, and the object length delimits the media — and its syntax is MOQT's (vi64, type-length elements, the LOC parity rule), not ISOBMFF's size+FourCC boxes. ISOBMFF's existing compressed boxes (!mof, 14496-12 clause 8.16) take a ~100-byte moof to ~65–90 bytes, while LOCMAF reaches 2 bytes in the steady state; and since no player handles !mof, both need a decode step anyway. An MPEG-native design would rightly be box-framed, which makes it a different format rather than LOCMAF in another venue. The established split, also used for RTP, is for the IETF to define carriage over its transports and MPEG to define storage, coordinated by liaison. Something which is not compressed in LOCMAF is the CMAF header (init segment/moov box) which is carried in the catalog (or as a track property). There, MPEG provides “!mov” (essentially a header plus a gzipped body) that can be used to reduce the size, but an external gzip does the same. One thing mentioned from the MPEG side is low-overhead HEIF, which is quite different, but shares the idea that there is a canonical unpacking to the normal full boxes. MPEG's own low-overhead HEIF (mini, ISO/IEC 23008-12 Amd 2) follows the same architecture as LOCMAF: a compact form with a normative one-to-one expansion to standard boxes, which readers treat as if the equivalent meta and mdat were present. But it compacts the static description — the counterpart of moov — for one standalone image, as a fixed-layout box, and its expansion is defined up to the decoded image. LOCMAF addresses the per-chunk moof, repeated tens of times per second, compressed as deltas within a MOQT group, and pins its expansion to a byte-identical canonical CMAF form for conformance testing. A compact moov/CMAF Header in the spirit of lo-heif would be a natural MPEG work item that complements LOCMAF rather than replacing it. Then there is the case of CMAF boxes not compressed by LOCMAF. CMAF is quite constrained compared to general MP4 fragmented files, so there are rather few cases. I got feedback on supporting some boxes like uuid for C2PA, so in draft-01, I introduced rawBoxes which makes it possible to send any unusual box or a series of boxes mixed with the LOCMAF-compressed ones. In locmaf draft-02 (to be published), I also allow for sending sequenceNumbers in a delta-step-compressed way since C2PA and others may want them intact over the wire. Of course, by adding an object framing, one may store a LOCMAF sequence as a file. That was also part of draft-01, but I don’t think that should be the focus of the discussion. Regarding working in MPEG and having access to their internal documents, I do have that access, but I’d prefer to work in IETF with its open documents and processes. In summary, I think there is a pretty good case for continuing LOCMAF in IETF. It would be nice to get more people involved in looking at the details, of course, but at least there are already two independent implementations beyond my own. Cheers, Tobbe From: Magnus Westerlund <magnus.westerlund=40ericsson.com@dmarc.ietf.org> Date: Thursday, 12 November 2026 at 16:07 To: MOQ Mailing List <moq@ietf.org> Subject: [Moq] Way forward for LOCMAF WG, At the London Interim meeting (11-12 June 2026) the WG showed strong interest to adopt LOCMAF draft-einarsson-moq-locmaf<https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-einarsson-moq-locmaf/__;!!GjvTz_vk!WyyJm3V_4SocwnAtjtup5K-vvpyJmwyJUyuwIesx1--aeA2QbY4TxkeCcCEPtQaARw0XYCw-zrYjTluiOnBLTa2f8-ZF$> as a technique to optimize the CMAF object sizes in transit, especially for audio. The WG chairs identified the potential overlap with MPEG Systems that define the CMAF format and the WG sent an LS: https://datatracker.ietf.org/liaison/2285/<https://urldefense.com/v3/__https://datatracker.ietf.org/liaison/2285/__;!!GjvTz_vk!WyyJm3V_4SocwnAtjtup5K-vvpyJmwyJUyuwIesx1--aeA2QbY4TxkeCcCEPtQaARw0XYCw-zrYjTluiOnBLTeb19hg6$> We have now received the liaison reply, see https://mailarchive.ietf.org/arch/msg/moq/uJYkXAr3QkI_xPw9TUgsq9llTUc/<https://urldefense.com/v3/__https://mailarchive.ietf.org/arch/msg/moq/uJYkXAr3QkI_xPw9TUgsq9llTUc/__;!!GjvTz_vk!WyyJm3V_4SocwnAtjtup5K-vvpyJmwyJUyuwIesx1--aeA2QbY4TxkeCcCEPtQaARw0XYCw-zrYjTluiOnBLTR9BsE5d$> for the response document. My summary of the LS response is basically: * MPEG Systems have started studying CMAF profiles and reusable media-format definitions that may be used by a range of applications, including compact representations such as LOCMAF. * MPEG Systems invites LOCMAF enthusiasts and other interested IETF experts to contribute to low overhead version of CMAF. * They have a potential concern that an IETF LOCMAF specification would result in using the compacted form in API and in files, possibly leading to interoperability issues. * "MPEG Systems is committed to ensuring that standardizing these media-format solutions within MPEG will not impede the agility or schedule of the IETF MOQ WG. To facilitate this, we can offer a dedicated Ad hoc Group for this project where both MPEG Systems experts and IETF LOCMAF enthusiasts will jointly work on this topic. We can also make the ongoing developments of the study publicly accessible by non-MPEG members." * They kindly request that IETF MOQ WG take these considerations into account prior to proceeding with a formal adoption call, and also to inform MPEG Systems of our plans. There can be several ways for how to proceed. However, my thought at this stage is that there are two basic forward directions: 1. MOQ WG adopt the LOCMAF draft and develop it as the transport optimization only. If MPEG Systems develop low overhead version of CMAF we can select to include this as a format to support. 2. MOQ WG decided to not adopt LOCMAF and ask MPEG Systems to do what work they can to make CMAF more efficient and MOQ WG adopt those specifications when available. While thinking what you think is the right or if you want to propose another direction I think it can be worth taking into consideration the following: * What is possibility for you and others in the WG to participate in work to optimise the transfer of CMAF? * There are clear differences in the IPR Rules of IETF vs those of MPEG do they impact your view? * What is most important, a transmission transformation vs general file format improvements? * Is there a relevant different in who control the publication timeline here? If you have thoughts or comments please provide them. There are some agenda time set apart for discussion on Tuesday. I do expect us to hold a formal consensus call in the end on this way forward on this topic. Cheers Magnus Westerlund As MoQ WG chair
- [Moq] Way forward for LOCMAF Magnus Westerlund
- [Moq] Re: Way forward for LOCMAF Torbjörn Einarsson
- [Moq] Re: Way forward for LOCMAF Law, Will