Re: [Moq] Agenda topics for side meeting on Tuesday

Ian Swett <ianswett@google.com> Mon, 08 November 2021 17:38 UTC

Return-Path: <ianswett@google.com>
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 C28E93A12B3 for <moq@ietfa.amsl.com>; Mon, 8 Nov 2021 09:38:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.599
X-Spam-Level:
X-Spam-Status: No, score=-17.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 BGezSKUq5BuO for <moq@ietfa.amsl.com>; Mon, 8 Nov 2021 09:38:24 -0800 (PST)
Received: from mail-yb1-xb31.google.com (mail-yb1-xb31.google.com [IPv6:2607:f8b0:4864:20::b31]) (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 5BAFD3A12B2 for <moq@ietf.org>; Mon, 8 Nov 2021 09:38:24 -0800 (PST)
Received: by mail-yb1-xb31.google.com with SMTP id s186so45634252yba.12 for <moq@ietf.org>; Mon, 08 Nov 2021 09:38:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=0PI00Xs5tro24T0Ykl/CjslUND++7vAjA3YHu0VYbek=; b=eMrpyzVghe7dUwnCpag8bZebsOpdTbq+QEZWHC5Q9gmJ0nZYTmFtuMYXGT5MA4WGSx Q+BVuRuTZqjowAtDK8fHilDfkwBF5P+Xto4yI/kQjPK2pVUZL8bAl6SLugYEbHYNTSgr 40KepYtUncpFZc/Zuf3JSf3BWUTOEcZhmNMBJITl7yGiREysTjqCPeZK4mG469sPiwHR 4KczQUlwI1itn6lV4Zi5o10dVlG23yNBO8qq/N68tWN/v+lZTGIyOFxXVyemEFPUh7UD pmoKDoTRaQ4bs+bfecFlszNv6UebB2WQWDNycibVa8yQYQ640K/a6mWEV22c0iqE1ECv c34Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=0PI00Xs5tro24T0Ykl/CjslUND++7vAjA3YHu0VYbek=; b=kW4Z5ySTqHpLGQqaFkCvwRnleoLQKDIjCZkdq86/3TUsSqQ1tbnwjFIjm014fn02ZQ R4jtrrEdijlYNYAyI2TkZ1IJtQ3qjmhD1kxWcNvjmLTl/U/ZdMwwBHBY2u2Sho7cHbth dhjW8vqZc9j79GPKZhPOJIPaSe+AW3ZQqFkr5EScVA2VwWpGOVg/ByHeu05FVJ+ZBjtT XXK/hwkCm7MHKSFhdE5iBHIYnCbgyKIGrWNKWkKm10v9+mEKKt9jVfejHYDbwq1Lgm0W QRg5XpPRKXE7jccTrkZhsUaL0LncleMrwmXRYh2mjALNHD2qLueYYnYsHd+wEp/r7mCQ v26Q==
X-Gm-Message-State: AOAM5303RR72ZHmvfeZIcTRQ8ge8MvdIZNU3/f/iDnco9p2lOdr67aOu bYLuLqeCGvF9kIviqGC3N+h4O+tIle1+pWH4esrTyZgsc44=
X-Google-Smtp-Source: ABdhPJzyYlHkVd8L8/+L+AkCEe2SVJTKMDlA4OIsQ46zT5Fpaaq9Xbcy/gjz8V0btTChnWptBf39de87sNJ2c6IWSe8=
X-Received: by 2002:a25:c68a:: with SMTP id k132mr958221ybf.531.1636393101865; Mon, 08 Nov 2021 09:38:21 -0800 (PST)
MIME-Version: 1.0
References: <CAKKJt-euVt2j5+B_1+GPSvwaT-RcwvX=nMTJcnuD6RwgccCn_w@mail.gmail.com> <CAKKJt-f=AULS=ZXGdoYsYwvwxe16DF=Y-FjTPDdH-DFtrrNm3Q@mail.gmail.com>
In-Reply-To: <CAKKJt-f=AULS=ZXGdoYsYwvwxe16DF=Y-FjTPDdH-DFtrrNm3Q@mail.gmail.com>
From: Ian Swett <ianswett@google.com>
Date: Mon, 08 Nov 2021 12:38:10 -0500
Message-ID: <CAKcm_gO0b92qw2HjsEzdjhaA_zEWGWO7Ld+HQU9nbiDooLwBcA@mail.gmail.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Cc: MOQ Mailing List <moq@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000008d25f205d04a7574"
Archived-At: <https://mailarchive.ietf.org/arch/msg/moq/dbnjcGxcvfPKCbdvi6fGv_53IXU>
Subject: Re: [Moq] Agenda topics for side meeting on Tuesday
X-BeenThere: moq@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 08 Nov 2021 17:38:29 -0000

Hi,

I've looked at the following uses cases fairly closely for QUIC in the past.

   - Live Video Ingestion - Existing protocols don't fully meet our needs
   (ie: performance vs reliability, standardization, etc), and this is
   becoming a real problem.
   - Live Video Delivery - Currently we're pushing the edge of what HTTP
   can do efficiently, including some non-standard extensions.  This is also
   not optimized for QUIC or HTTP/3, which could improve performance.
   - WebRTC over QUIC, ie: RTP over QUIC + Datachannels over QUIC - There
   could be a number of benefits of WebRTC over QUIC.  A number of people who
   were interested in this are now focused on WebTransport, but there's still
   the matter of what you send over WebTransport, so I think there's some work
   to be done in addition to finishing WebTransport.

As with QUIC, I see we have a number of different working groups different
parts or applications could land in.  I worry that could cause
fragmentation if each sub-domain solves their problem without collaborating
closely with others.  I'm not sure if a new WG(ie: QUIC-style) is necessary
here, but I do think caution should be taken to ensure we don't reinvent
the wheel 3+ different ways.

Thanks, Ian

On Mon, Nov 8, 2021 at 7:13 AM Spencer Dawkins at IETF <
spencerdawkins.ietf@gmail.com> wrote:

> So, three things I should say before the Tuesday side meeting.
>
> First - this side meeting will be under Notewell, because it's focused on
> input to the IETF.
>
> Second - I'm planning to record the session, just so I can verify what we
> said, so that I can produce decent minutes. If anyone objects, please also
> volunteer to take excellent notes!
>
> Third - James and I are most familiar with the RTP over QUIC proposals,
> but we recognize that there will be commonalities between various
> proposals, so  we're perfectly happy to talk about other use cases and
> requirement sets. So, letting us know what you're thinking about, as
> requested below, will be super useful.
>
> Please Do The Right Thing.
>
> Best,
>
> Spencer
>
> On Sun, Nov 7, 2021 at 12:36 PM Spencer Dawkins at IETF <
> spencerdawkins.ietf@gmail.com> wrote:
>
>> Dear MOQ fans,
>>
>> It's time to put together an agenda for the Tuesday meeting. I'd like for
>> this meeting to be a working session, not a forum for presentations, so
>> please keep that in mind.
>>
>> As a high-order bit, I think we've spent a lot of time thinking about use
>> cases here, and I'd like to push down another level, and make sure we
>> understand what the work for the IETF (and possibly for the IRTF) is.
>>
>> I know what the protocol work is for my use cases:
>>
>>    - Mapping RTP onto QUIC (many options exist, so picking one or more
>>    would be helpful) This is squarely in scope for AVTCORE
>>    - Mapping RTCP onto QUIC (which may be the same approach as used for
>>    RTP, or may include things like using QUIC facilities instead of RTCP
>>    facilities, where those QUIC facilities exist).. Again, this is squarely in
>>    scope for AVTCORE
>>    - SDP description for RTP/RTCP over QUIC. This is squarely in scope
>>    for MMUSIC, as soon as we figure out the details in AVTCORE.
>>
>> What is the IETF/IRTF work for your use cases?
>>
> --
> Moq mailing list
> Moq@ietf.org
> https://www.ietf.org/mailman/listinfo/moq
>