From nobody Wed Jul 14 10:00:04 2021 Return-Path: X-Original-To: quic@ietfa.amsl.com Delivered-To: quic@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D8623A251E; Wed, 14 Jul 2021 09:59:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.847 X-Spam-Level: X-Spam-Status: No, score=-1.847 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RMlYqvvJkvcd; Wed, 14 Jul 2021 09:59:52 -0700 (PDT) Received: from mail-ej1-x62a.google.com (mail-ej1-x62a.google.com [IPv6:2a00:1450:4864:20::62a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 36FEF3A251D; Wed, 14 Jul 2021 09:59:51 -0700 (PDT) Received: by mail-ej1-x62a.google.com with SMTP id c17so4380988ejk.13; Wed, 14 Jul 2021 09:59:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=5c9XssFNAdvq/WDdXotxPR9PnrcCVzp5F+EMCSkrRMA=; b=AkyT9hiF/3bbb6R+fqW6aUGCPfJI/NOcouOXLfa3GYWdaeGR8hyX+SA5PbhF5FNTCe d/ZuIOtNo6yZaz1oSuOZn22ENyTwYa3TSsqpoH1IFd4ULWlN4x72djRHd309xkKbq3ox ZQQ0Z6F61wcFUdmRWGnbMP3UWMe86g8VhlA2Oqw6GPxG685MGz+3Jl2aqxV+ZNXKhX5f DaOfuz7o1fJuI5fimi+VchiTME5IuQiuNAZeTcL4uZh7sqw3umieBF5SXUVYNSBbP1sg d6t67y6+Xw4Hx+GA16pwJffNqTr5eklzErwAlpAC0+BbXqVZuIPuuRvXTGH0Wfg7kdEM F1dA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=5c9XssFNAdvq/WDdXotxPR9PnrcCVzp5F+EMCSkrRMA=; b=dMv7EHWzyOsTdzxIFZbMYViSYk7cTlfBzJ6QoUNI7Gw///UCVkg5ntaQQd1uDMvl63 bty9P+hSoAAAMgTbqlnqEHna4SNWPuHK7uSQsWgOzOjZqbwV/KA8hSv1+fshBNN7ba/i N6baY2R/NJFlZB8ChTByeisvGCFoo3RirZqVDBttfr7mONqvxA47zGohk50bjok+jCNA XEWRHRUmh/geZmP7o2Mt+pVPbEMXGA5yHncTJ3f1jqUVQ7HMcJD44I60KwPuMG0WvFKV 9u70qtLwRd9yGeD2sOGNlW16o5NSOTEA4m9cdSea+oDPp9cJ99h3xqAvm7qT8V3o5DPr 5VWw== X-Gm-Message-State: AOAM532obrWswwTl8bKRDoOXwP5hlRlY+bpNrEqu97fNPwluIKR+9DqN 0kLPWj4W0sqZy53LfLos672e9wF5Mv5vFuG19Aw= X-Google-Smtp-Source: ABdhPJzl41muIF8/7wMEtIhlJ6EczwNyhRP1uEp12Se2LSGsuBtck1EbAnUFf5Pl96rHpuuUX1rbvdVq3+E6UeWoGD0= X-Received: by 2002:a17:906:4e85:: with SMTP id v5mr13340517eju.67.1626281987522; Wed, 14 Jul 2021 09:59:47 -0700 (PDT) MIME-Version: 1.0 References: <674A60FB-8F32-472A-AB35-DBABE8EED38F@fb.com> In-Reply-To: From: Lucas Pardue Date: Wed, 14 Jul 2021 17:59:31 +0100 Message-ID: Subject: Re: [AVTCORE] [Wish] Video ingest over QUIC To: Victor Vasiliev Cc: juberti@alphaexplorationco.com, Roberto Peon , "avt@ietf.org" , "wish@ietf.org" , Luke Curley , Alan Frindell , "quic@ietf.org" , Kirill Pugin Content-Type: multipart/alternative; boundary="0000000000002bc52d05c718481a" Archived-At: X-BeenThere: quic@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Main mailing list of the IETF QUIC working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jul 2021 16:59:57 -0000 --0000000000002bc52d05c718481a Content-Type: text/plain; charset="UTF-8" Thanks for sharing Alan. On Wed, Jul 14, 2021 at 5:32 PM Victor Vasiliev wrote: > Hi Alan, > > Excited to see this draft! > > Since this isn't technically in scope for either avtcore, wish or quic > working groups, what would people think about making a new mailing list for > video over QUIC? > It isn't technically out of scope for the QUIC WG either :-) Our charter [1] says: "Specifications describing how new or existing application protocols use the QUIC transport layer, called application protocol mappings below, need not be specified in the QUIC WG, although they can. The QUIC WG will collaborate with other groups that define such application protocols that intend to use QUIC" That said, I think between the potential interested parties and the application mapping not requiring change from QUIC, it warrants the work taking place somewhere that can focus on more of the video needs. I'd support another mailing list as a place to continue this conversation. I think more discussion is required before trying to formulate a WG, the ADs should definitely have some input here. Cheers, Lucas [1] - https://datatracker.ietf.org/wg/quic/about/ --0000000000002bc52d05c718481a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks for sharing Alan.

On Wed, Jul 1= 4, 2021 at 5:32 PM Victor Vasiliev <vasilvv=3D40google.com@dmarc.ietf.org> wrote:
Hi Alan,

Excited to see this draft!
<= br>
Since this isn't technically in scope for either avtcore,= wish or quic working groups, what would people think about making a new ma= iling list for video over QUIC?

It isn't technically out of scope for the QUIC WG either :-) Our= charter [1] says:

"Specifications describing how ne= w or existing application protocols use=20 the QUIC transport layer, called application protocol mappings below,=20 need not be specified in the QUIC WG, although they can. The QUIC WG=20 will collaborate with other groups that define such application=20 protocols that intend to use QUIC"

That said,= I think between the potential interested parties and the application mappi= ng not requiring change from QUIC, it warrants the work taking place somewh= ere that can focus on more of the video needs. I'd support another mail= ing list as a place to continue this conversation. I think more discussion = is required before trying to formulate a WG, the ADs should definitely have= some input here.

Cheers,
Lucas


--0000000000002bc52d05c718481a--