Re: [Wish] [AVTCORE] Video ingest over QUIC

Mike English <ietf@englishm.net> Wed, 14 July 2021 17:10 UTC

Return-Path: <englishm.ietf@gmail.com>
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 F1DFC3A25C3; Wed, 14 Jul 2021 10:10:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.645
X-Spam-Level:
X-Spam-Status: No, score=-1.645 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 C_ySQ30JiKj1; Wed, 14 Jul 2021 10:10:12 -0700 (PDT)
Received: from mail-pf1-f173.google.com (mail-pf1-f173.google.com [209.85.210.173]) (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 B41093A25C2; Wed, 14 Jul 2021 10:10:11 -0700 (PDT)
Received: by mail-pf1-f173.google.com with SMTP id p36so2592321pfw.11; Wed, 14 Jul 2021 10:10:11 -0700 (PDT)
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=uNYI87jPz8MeBnGtzZQuWiynHLr35QMfkW77g86EDks=; b=mFgHerQGhODAD15719KBlMo75vYrBEUh4jrgtdJJvdEB7wA1NztFJoJMQOEbmRnJ+Y RD79jCije3aiae5NGMTagip/01Yk56UGAkhYtDtcB3UNE3IllX9X9ucw0Du2XI+9nopo zMyfA3UvhYXdEctzlXCCkb7oiN9kERSyutwCTnCAF9kYixifIZklQDMZ4c9GZauXEXhr 6GbdSHUbV40UY7CzFPexPPkcTJXNrJA8HPLGlHq1QpaWTieQRDazX0nVZ0kppf3mkv7N Sox1BY4qhq2/UngMnE3aO5VguSrl0rvNoI40G7HeoRRWKMmnRHKWEkzXqIL+aPCQIPe8 0bAw==
X-Gm-Message-State: AOAM533VmF9zbmI3VYRYjG/e5tcoyI09qxR+ovn9oGeF2f/gWwlXvVYe X1iw2p6ijOuuiic8DqJuPoC5XJYqEiVnfg==
X-Google-Smtp-Source: ABdhPJyfleMAcPdilfVFZzAPT/aCy1jTukEE1F76KxJmCYl3oypQVggdlJ8j++qnwSmul4gXCuoN/Q==
X-Received: by 2002:a63:2b92:: with SMTP id r140mr10464406pgr.394.1626282610784; Wed, 14 Jul 2021 10:10:10 -0700 (PDT)
Received: from mail-pf1-f171.google.com (mail-pf1-f171.google.com. [209.85.210.171]) by smtp.gmail.com with ESMTPSA id i18sm3647381pfa.149.2021.07.14.10.10.10 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 14 Jul 2021 10:10:10 -0700 (PDT)
Received: by mail-pf1-f171.google.com with SMTP id j199so2609066pfd.7; Wed, 14 Jul 2021 10:10:10 -0700 (PDT)
X-Received: by 2002:a63:2f05:: with SMTP id v5mr10398988pgv.449.1626282610013; Wed, 14 Jul 2021 10:10:10 -0700 (PDT)
MIME-Version: 1.0
References: <674A60FB-8F32-472A-AB35-DBABE8EED38F@fb.com> <CA+ag07ZaaPmij_LZPPAkM_DDF0vbwTXTV0X-tzwPaBc-M50+TA@mail.gmail.com> <DD4D4FF0-D969-499B-BB2F-FACF48CDEE7B@fb.com> <CAHVo=Zk=jb8DGCYUhvW6C7ZjbGoaCLM7vavtrjfYg2jxB7Oz9w@mail.gmail.com> <BB6D02DF-88D0-4CF0-9E3E-57B9FB77F586@fb.com> <CAOLzse344PWsATjRaya6CbNHV8UAOa_2VYHKjg3ORs5i4aQVfg@mail.gmail.com> <CAAZdMaffLiCKd3xvaeOPkgFqGdkSwZR-_H-2f5TNOn8_-WRKoA@mail.gmail.com>
In-Reply-To: <CAAZdMaffLiCKd3xvaeOPkgFqGdkSwZR-_H-2f5TNOn8_-WRKoA@mail.gmail.com>
From: Mike English <ietf@englishm.net>
Date: Wed, 14 Jul 2021 13:09:59 -0400
X-Gmail-Original-Message-ID: <CAK=xEZO_5b+JqTADtFB1BpM9GkRJTEOhS6fuDnC8t1r_eMNfnA@mail.gmail.com>
Message-ID: <CAK=xEZO_5b+JqTADtFB1BpM9GkRJTEOhS6fuDnC8t1r_eMNfnA@mail.gmail.com>
Subject: Re: [Wish] [AVTCORE] Video ingest over QUIC
To: Victor Vasiliev <vasilvv=40google.com@dmarc.ietf.org>
Cc: juberti@alphaexplorationco.com, Roberto Peon <fenix=40fb.com@dmarc.ietf.org>, "avt@ietf.org" <avt@ietf.org>, "wish@ietf.org" <wish@ietf.org>, Luke Curley <kixelated@gmail.com>, Alan Frindell <afrind=40fb.com@dmarc.ietf.org>, "quic@ietf.org" <quic@ietf.org>, Kirill Pugin <ikir@fb.com>
Content-Type: multipart/alternative; boundary="000000000000463b2d05c7186d01"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/VLcamP3AxvnnJv66ye-aQ61Z2-Y>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Jul 2021 17:10:18 -0000

I would personally be very interested in a "video over QUIC" working group
or mailing list.

The directness of this draft is perhaps what's most interesting to me.
In particular, the absence of out-of-band signaling / session establishment
stands in striking contrast with another UDP-based media ingest option:
WebRTC.

The signaling needed for session establishment (and the diversity of
implementations for such signaling) has historically been a barrier for
WebRTC adoption as an ingest protocol outside of the browser context.
WISH-WG is working to improve that situation for WebRTC of course, but a
new QUIC-based ingest protocol presents an opportunity to sidestep some of
those known-issues by making an architectural decision up front about
whether that style of session management is necessary in a video
contribution workflow.

I'm hoping others with more experience on these lists can speak to the
history and tradeoffs associated with those approaches, but I just wanted
to call attention to the aspect of the draft that seemed most notable to me
as an operator of a low latency streaming platform where WebRTC egress and
ingest capabilities are provided, but where RTMP is still the de facto
ingest protocol of choice for many users.

Thanks for sharing this work!
-Mike

On Wed, Jul 14, 2021 at 12:32 PM Victor Vasiliev <vasilvv=
40google.com@dmarc.ietf.org> 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?
>
> Cheers,
>  Victor.
>
> On Wed, Jul 14, 2021 at 3:27 AM Justin Uberti <
> juberti@alphaexplorationco.com> wrote:
>
>> +1
>>
>> On Tue, Jul 13, 2021 at 1:35 PM Roberto Peon <fenix=
>> 40fb.com@dmarc.ietf.org> wrote:
>>
>>> Seems like a good idea to me, unless there is a home that is already
>>> well suited!
>>>
>>> -=R
>>>
>>>
>>>
>>> *From: *QUIC <quic-bounces@ietf.org> on behalf of Luke Curley <
>>> kixelated@gmail.com>
>>> *Date: *Tuesday, July 13, 2021 at 1:16 PM
>>> *To: *Alan Frindell <afrind=40fb.com@dmarc.ietf.org>
>>> *Cc: *"quic@ietf.org" <quic@ietf.org>, Sergio Garcia Murillo <
>>> sergio.garcia.murillo@gmail.com>, "avt@ietf.org" <avt@ietf.org>, "
>>> wish@ietf.org" <wish@ietf.org>, Kirill Pugin <ikir@fb.com>
>>> *Subject: *Re: [Wish] Video ingest over QUIC
>>>
>>>
>>>
>>> Hey Alan, thanks for publishing your protocol!
>>>
>>>
>>>
>>> Twitch has also been working on a video over QUIC protocol, albeit
>>> primarily for video distribution instead of contribution. We're very
>>> interested in collaborating on RUSH and producing a new standard for live
>>> streaming! Would there be broader interest in forming a video over QUIC
>>> working group?
>>>
>>>
>>>
>>> On Tue, Jul 13, 2021 at 12:04 PM Alan Frindell <afrind=
>>> 40fb.com@dmarc.ietf.org> wrote:
>>>
>>> Hi Sergio, thanks for your interest in the draft.
>>>
>>>
>>>
>>> I’m interested in seeing a video ingest protocol standard that leverages
>>> QUIC as a transport, has some partial reliability support, and is less
>>> connection-oriented so that servers can go down for maintenance without
>>> impacting ingest reliability or having arbitrarily long drain times.  We
>>> published our RUSH draft to help kickstart the conversation but we’re open
>>> to feedback and modifications if they help advance those goals.
>>>
>>>
>>>
>>> Thanks
>>>
>>>
>>>
>>> -Alan
>>>
>>>
>>>
>>> *From: *Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
>>> *Date: *Tuesday, July 13, 2021 at 9:02 AM
>>> *To: *Alan Frindell <afrind@fb.com>
>>> *Cc: *"quic@ietf.org" <quic@ietf.org>, "wish@ietf.org" <wish@ietf.org>,
>>> "avt@ietf.org" <avt@ietf.org>, Kirill Pugin <ikir@fb.com>
>>> *Subject: *Re: [Wish] Video ingest over QUIC
>>>
>>>
>>>
>>> Hi Alan,
>>>
>>>
>>>
>>> I think that the correct place for discussing it is AVTCORE as Bernard
>>> has indicated, as  WISH is not chartered to implement any new media
>>> protocol.
>>>
>>>
>>>
>>> The draft is very interesting and I would be willing to collaborate,
>>> what is your main interest? Do you want to try to publish it as it is or
>>> would you be accepting feedback and include modifications?
>>>
>>>
>>>
>>> Best regards
>>>
>>> Sergio
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> El mar, 13 jul 2021 a las 17:37, Alan Frindell (<afrind=
>>> 40fb.com@dmarc.ietf.org>) escribió:
>>>
>>> Hi, for several years, Facebook has been using its own video ingest
>>> protocol over QUIC from our apps to our infra.  While we’ve spoken about it
>>> before, we just now published a draft documenting how it works:
>>> https://www.ietf.org/archive/id/draft-kpugin-rush-00.html.
>>>
>>> The protocol leverages the advantages of QUIC transport, and features a
>>> partially reliable mode using only QUIC v1 RST_STREAM.
>>>
>>> We welcome your feedback
>>>
>>> Thanks
>>>
>>> -Alan Frindell
>>>
>>>
>>>
>>>
>>>
>>> --
>>> Wish mailing list
>>> Wish@ietf.org
>>> https://www.ietf.org/mailman/listinfo/wish
>>>
>>> --
>>> Wish mailing list
>>> Wish@ietf.org
>>> https://www.ietf.org/mailman/listinfo/wish
>>>
>>> _______________________________________________
>>> Audio/Video Transport Core Maintenance
>>> avt@ietf.org
>>> https://www.ietf.org/mailman/listinfo/avt
>>>
>> --
> Wish mailing list
> Wish@ietf.org
> https://www.ietf.org/mailman/listinfo/wish
>