Re: [Moq] Charter adjustment

Christian Huitema <huitema@huitema.net> Fri, 22 July 2022 02:24 UTC

Return-Path: <huitema@huitema.net>
X-Original-To: moq@ietfa.amsl.com
Delivered-To: moq@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16ABBC157B4D for <moq@ietfa.amsl.com>; Thu, 21 Jul 2022 19:24:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jhOC7Uz8X9FM for <moq@ietfa.amsl.com>; Thu, 21 Jul 2022 19:24:10 -0700 (PDT)
Received: from mx36-out10.antispamcloud.com (mx36-out10.antispamcloud.com [209.126.121.30]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5E9BCC13C537 for <moq@ietf.org>; Thu, 21 Jul 2022 19:24:10 -0700 (PDT)
Received: from xse412.mail2web.com ([66.113.197.158] helo=xse.mail2web.com) by mx259.antispamcloud.com with esmtp (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1oEiKZ-000CG7-Co for moq@ietf.org; Fri, 22 Jul 2022 04:24:08 +0200
Received: from xsmtp22.mail2web.com (unknown [10.100.68.61]) by xse.mail2web.com (Postfix) with ESMTPS id 4LptXm44r1z9ZQ for <moq@ietf.org>; Thu, 21 Jul 2022 19:23:52 -0700 (PDT)
Received: from [10.5.2.14] (helo=xmail04.myhosting.com) by xsmtp22.mail2web.com with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1oEiKW-0001NI-EY for moq@ietf.org; Thu, 21 Jul 2022 19:23:52 -0700
Received: (qmail 8727 invoked from network); 22 Jul 2022 02:23:51 -0000
Received: from unknown (HELO [192.168.1.104]) (Authenticated-user:_huitema@huitema.net@[172.58.46.184]) (envelope-sender <huitema@huitema.net>) by xmail04.myhosting.com (qmail-ldap-1.03) with ESMTPA for <bernard.aboba@gmail.com>; 22 Jul 2022 02:23:51 -0000
Content-Type: multipart/alternative; boundary="------------4Fin0F2hoL0tcN5YAYKAHG3C"
Message-ID: <b2312817-f859-53f8-0fba-307c71ac05e7@huitema.net>
Date: Thu, 21 Jul 2022 19:23:51 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0
Content-Language: en-US
To: Bernard Aboba <bernard.aboba@gmail.com>, Ian Swett <ianswett=40google.com@dmarc.ietf.org>
Cc: Suhas Nandakumar <suhasietf@gmail.com>, Lucas Pardue <lucaspardue.24.7@gmail.com>, "Mo Zanaty (mzanaty)" <mzanaty=40cisco.com@dmarc.ietf.org>, "Ali C. Begen" <ali.begen=40networked.media@dmarc.ietf.org>, Ted Hardie <ted.ietf@gmail.com>, MOQ Mailing List <moq@ietf.org>
References: <CA+9kkMAr=dMSg9efcYBd5QZquvDhYcQi_gibyttxjqcxvWZKMw@mail.gmail.com> <511BF9AE-C84B-4AC2-9430-B268979078B4@networked.media> <CAMRcRGRGR3bXroZch4DAgeN65GodUp2J4=44pvB-6_ieGLKDTg@mail.gmail.com> <BN7PR11MB275378CDC1463041BB4E71CEB4919@BN7PR11MB2753.namprd11.prod.outlook.com> <CALGR9oaFWKvjaHg_bjoTFFMavpwAWLLe2FEGyLzNcYFqxWHswg@mail.gmail.com> <CAMRcRGTs8UPLHzw9PiJB2rOh8MwE402LvBi+xRXbnVdrx2sSwA@mail.gmail.com> <CAMRcRGRdTk_kXnd=s5ZB0XuHTRtTH0xPir3hJkBprAV70dtsTw@mail.gmail.com> <CAKcm_gMbWtbJe=kcbCXxAphLpiaiGHQPcm=00Tqoioh2SC6VZA@mail.gmail.com> <CAOW+2dvwEr3uZ0BKJeOO9eYHJhYZsZ4w_hWVckG5n4F6bSJ_2g@mail.gmail.com>
From: Christian Huitema <huitema@huitema.net>
In-Reply-To: <CAOW+2dvwEr3uZ0BKJeOO9eYHJhYZsZ4w_hWVckG5n4F6bSJ_2g@mail.gmail.com>
X-Originating-IP: 66.113.197.158
X-Spampanel-Domain: xsmtpout.mail2web.com
X-Spampanel-Username: 66.113.197.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=66.113.197.0/24@xsmtpout.mail2web.com
X-Spampanel-Outgoing-Class: unsure
X-Spampanel-Outgoing-Evidence: Combined (0.15)
X-Recommended-Action: accept
X-Filter-ID: Pt3MvcO5N4iKaDQ5O6lkdGlMVN6RH8bjRMzItlySaT9WLQux0N3HQm8ltz8rnu+BPUtbdvnXkggZ 3YnVId/Y5jcf0yeVQAvfjHznO7+bT5xu6w3L23EOleH9nr/v5kMyj3CSdYahsEhiizd3WfZtESck xb+A+CSo6QY6IGFM7D/lYLLlWSy3OGfGBNeqx2anHyJxjDLo4/ugN15VVJm4KWrxEaaKeSxe0Wrx 6M4G5/Wm4Zd53xWOh54QqC5fJ2uR8XhWGJmzLGHcTLN/GJy/Ylxh7hoyMoWHMkqYfQEaAmsLx37j FXSWNb1fNzg7BhSepbt3W3gfNnuKkqGP09ZKLP25Cgscc2Nqd9azmDa4ZbYxn04qRLKGrOrEzQDq o2Fe5e0H1p2YD3fIDgqE3F/hSENKwnAR2oVisY+bnEqWCKi5klmK1va3wJScg92pg//jdNpXP/ul EV6DIUDLc0Yd6iTlYE+Zcn8p1rPpG64P1y7nVrUQfxkYoV3jt7fqlPgR0kaOEXLuWd+6zLg4wp8u X1nsyWu8Q0HDoORE+fy5gr3LgKffTIgl7nuGO/IJU1342OUMeHyTpNN0eXybX/w7/4a+Zyc1sUYl ckMDbruAhxeLAMKmgwH2OI1KXZVCaM7UA33SSIOjk6trAcgw0LwdtKj++xWy52ftDvMewfznDwLo L5VivOTcNe47fR5GNNriC8CKASqFe0kBQ5ZmwPhPJiyZvdx3ZJDsPzrvEdt+b8mxX4OQOI/UQ6jn FfMBgzwOSHunMg5j/UO+IMRndiIcro3adS6NTA3JKCpDv4OjD1zZcpPgEJKLbDyaC/LdLvvYsbhi Cj5KW8NhUUiU381JpPpVB9v9zY0h8asEYmbGGsJD9ySC20IzFkBtfP+lFUR4L5akmgve9zwCUB4g w2vzQ713qFZSq8Fx+9otn0aqja8VKPqpdskk5LxBR/9t1zMMkdu6/R2FM84kxYRFSvC1IDg1BRW7 hzp8w3iHcOwbVtsmWfnQGGis4EvbR3jXsI0ESXwhBU2hwt/J18C+HygJl/jEzm1SsR8v3aJbN/NZ fa8pHhHaz+HPa0HAgEx4sWDF
X-Report-Abuse-To: spam@quarantine11.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/moq/L4QEAgLWqm7DN1mpL9ZprwaDOgM>
Subject: Re: [Moq] Charter adjustment
X-BeenThere: moq@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Media over QUIC <moq.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/moq>, <mailto:moq-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/moq/>
List-Post: <mailto:moq@ietf.org>
List-Help: <mailto:moq-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/moq>, <mailto:moq-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jul 2022 02:24:14 -0000

On 7/21/2022 7:13 PM, Bernard Aboba wrote:

> Ian said:
>
> "HTTPS proxies have been around for a long time, and MoQ shares many 
> of those properties."
>
> [BA] Indeed, there are proposals (such as HESP 
> <https://www.hespalliance.org/>) aimed at low-latency distribution 
> that run over HTTP/3 and support caching.
>
> This begs the question of "Why is MoQ better?"


If you want low latency, you need to support datagrams, and have some 
way to fragment long frames over series of datagrams. But then, if you 
require reassembly of fragmented frames at each step in the relaying 
chain, you can easily run into head-of-line blocking. That's something 
we can handle in MoQ. I don't know whether HESP does that -- the specs 
do not appear to be publicly available.

-- Christian Huitema