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

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Fri, 16 July 2021 18:36 UTC

Return-Path: <spencerdawkins.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 EE1AE3A3E74; Fri, 16 Jul 2021 11:36:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 zZLq-X-xKaya; Fri, 16 Jul 2021 11:36:11 -0700 (PDT)
Received: from mail-vk1-xa2b.google.com (mail-vk1-xa2b.google.com [IPv6:2607:f8b0:4864:20::a2b]) (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 CBDF93A4055; Fri, 16 Jul 2021 11:36:10 -0700 (PDT)
Received: by mail-vk1-xa2b.google.com with SMTP id bb26so2337306vkb.10; Fri, 16 Jul 2021 11:36:10 -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=UyyVN+GbU+A5jtlaDtLJsiaEfZ578deF+33RLWC1rio=; b=sUXqz52N6y6/2li2+dXcCnky8mQEV7NzXBQEIc9Fx0hQfnwZllkEOlSaUpHXPJcC8i 31qj48HcvFBGYB4zZeNlC7MJiPbrrhRegwAGHyk9/+fOtPmDdVQlW5W8XeFsC3G8kn/2 NrfFfBsWqwx7ix2JHAimQqfmPzCPtG27CjNbkjdGeu0hdR+EoGEyCwVBHdv/ptZvA7od nhlY2nJ+qyFF1oB73kvfOWBFB9/Vvxp2TjPr02ZZlhMG6jfm5T/yzruIggc9319WMsfU O4MHjfNJ5GoKgCRQdlMWvtPP63r3xfuJBpyt5J4ko4go4WdIb1xeP5hqqTwhKotyPUDQ TFxQ==
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=UyyVN+GbU+A5jtlaDtLJsiaEfZ578deF+33RLWC1rio=; b=TffBVB5/aR5u2MzHhmsu+UHUqyzn3Q0fQg8taGSpB3053PFg/ou2Xy+OxWTHmhz0O0 OlPHvfDU8weqDJ27oA3U6UAMTRRLOQqk88A9e9SdKSCWWWphzkQppgne/FKACU+pPmfq BAzlQSFhJzg/W42H8LvwLaMSU3oXJc6ddZvryMu4l7+bofq/3OQ8/nknm8Dv/aZ55Lj/ 9ZE5a0h98FU3hZUyitFub58AeCa+I1Gh95E8Q32J6A+/02xuF9vyN3D5XrCbOYILbzhz u7uwrC7UKerE0DKVmrNqw/H0K9cx4l8TosXLvY4PGsMT/HAkSHOdb9pKuHtDlW3hlsLY PQiA==
X-Gm-Message-State: AOAM533Z7eUhJcG/o2A2kAhbJggL1JciVbKGgkPpZnoKx5PjHSzr/Zqn X+RbsR+JTiWHeiFxG0v1rhI+Cfwh7XcwAx5dzVs=
X-Google-Smtp-Source: ABdhPJwRwUjISPzVeKXxkOA6FCpWtWx/7MJvlrLOfENU8VMjCgUWCFdHxLQIdD0rc//dgxZaXCA1B7VuW0BBzXSXyB4=
X-Received: by 2002:a1f:6009:: with SMTP id u9mr13339961vkb.24.1626460569124; Fri, 16 Jul 2021 11:36:09 -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> <CAK=xEZO_5b+JqTADtFB1BpM9GkRJTEOhS6fuDnC8t1r_eMNfnA@mail.gmail.com>
In-Reply-To: <CAK=xEZO_5b+JqTADtFB1BpM9GkRJTEOhS6fuDnC8t1r_eMNfnA@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Fri, 16 Jul 2021 13:35:42 -0500
Message-ID: <CAKKJt-f=W+fNzZXGhmvZWm9td_JWyUUS1fN-FsVNLtAyK5psKA@mail.gmail.com>
Subject: Re: [Wish] [AVTCORE] Video ingest over QUIC
To: Mike English <ietf@englishm.net>
Cc: Victor Vasiliev <vasilvv=40google.com@dmarc.ietf.org>, Roberto Peon <fenix=40fb.com@dmarc.ietf.org>, "avt@ietf.org" <avt@ietf.org>, "wish@ietf.org" <wish@ietf.org>, juberti@alphaexplorationco.com, Alan Frindell <afrind=40fb.com@dmarc.ietf.org>, "quic@ietf.org" <quic@ietf.org>, Kirill Pugin <ikir@fb.com>, Luke Curley <kixelated@gmail.com>
Content-Type: multipart/alternative; boundary="00000000000076c42d05c741dcbf"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/eM_b08x_UFfRkYljRm77-G0mw8c>
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: Fri, 16 Jul 2021 18:36:16 -0000

This is, of course, why ADs get paid the big bucks (ha!), but

On Wed, Jul 14, 2021 at 12:10 PM Mike English <ietf@englishm.net> wrote:

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

Martin Thompson said (in a reply that, I think, only went to the QUIC
mailing list(*)) that he thought this was big enough to BOF (which doesn't
mean it shouldn't be discussed at DISPATCH at IETF 111), but does say
something about what a mailing list could be used for. Offhand, I can
imagine:

   - discussion of the existing
   https://www.ietf.org/archive/id/draft-kpugin-rush-00.html draft
   - discussion of potential scope for a BOF proposal
   - discussion of proposed text for a BOF request

Could I ask what the people who are expressing interest in a mailing list
are thinking about?

Best,

Spencer

(*) email is archived at
https://mailarchive.ietf.org/arch/msg/quic/ocCm8E-GzP_pn4LBcJyKQeN7GRU/.

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
>>
>