Re: [AVTCORE] Call for Adoption (CfA): RTP over QUIC

Joerg Ott <ott@in.tum.de> Sun, 26 June 2022 16:44 UTC

Return-Path: <ott@in.tum.de>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C4F2C15AD2D for <avt@ietfa.amsl.com>; Sun, 26 Jun 2022 09:44:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.884
X-Spam-Level:
X-Spam-Status: No, score=-3.884 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, NICE_REPLY_A=-1.876, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=in.tum.de
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 7B8n3-z3gRlQ for <avt@ietfa.amsl.com>; Sun, 26 Jun 2022 09:44:54 -0700 (PDT)
Received: from mailout2.rbg.tum.de (mailout2.rbg.tum.de [IPv6:2a09:80c0::202]) (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 21EADC15AD25 for <avt@ietf.org>; Sun, 26 Jun 2022 09:44:53 -0700 (PDT)
Received: from mailrelay1.rbg.tum.de (mailrelay1.in.tum.de [131.159.254.14]) by mailout2.rbg.tum.de (Postfix) with ESMTPS id 60CE64C01FE; Sun, 26 Jun 2022 18:44:47 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=in.tum.de; s=20220209; t=1656261887; bh=RJ5NpKDRab9YBENxKq6sqa3Lxyf2qIdNPdLpgaO3z+A=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=KuSq2Qjj1KIJK/pvUuUAFy37LEvvD4FjXyoGpGr2r4RplIK9pkm2QnFcpHxnn+BbG 9SJ3+t96FGIn5oMJJ/41+ETUNpH6268sQyy5Hjl8MvqwAA1sEuurCSH6OjVPAOrazd 9t72l54WzA1ZsRuWy/wtjmL9DbfIUpllpyyh3f2zwZRU/F59c1p3CuB75qhhgXdKeM HC/gqhHbtIdg+8yTn17TUD8PmD5i392grwqGHsF9qJ78VTQcrs/I6yI1ue08Fm+rYY TB0sXeVF3rXAcY50mU72QRdtZYKIi5UznazCm8CQji3f2ypmAsq4K7IqDPfObwb87z u5KwjRVpaQTmw==
Received: by mailrelay1.rbg.tum.de (Postfix, from userid 112) id 5B47F3AC; Sun, 26 Jun 2022 18:44:47 +0200 (CEST)
Received: from mailrelay1.rbg.tum.de (localhost [127.0.0.1]) by mailrelay1.rbg.tum.de (Postfix) with ESMTP id 39627191; Sun, 26 Jun 2022 18:44:47 +0200 (CEST)
Received: from mail.in.tum.de (mailproxy.in.tum.de [IPv6:2a09:80c0::78]) by mailrelay1.rbg.tum.de (Postfix) with ESMTPS id 37B8A14B; Sun, 26 Jun 2022 18:44:47 +0200 (CEST)
Received: by mail.in.tum.de (Postfix, from userid 112) id 3242F4A0247; Sun, 26 Jun 2022 18:44:47 +0200 (CEST)
Received: (Authenticated sender: ott) by mail.in.tum.de (Postfix) with ESMTPSA id 2A45B4A011B; Sun, 26 Jun 2022 18:44:45 +0200 (CEST) (Extended-Queue-bit xtech_qs@fff.in.tum.de)
Message-ID: <8e44acd9-d723-2b4d-2218-379f205c0d99@in.tum.de>
Date: Sun, 26 Jun 2022 18:44:44 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.10.0
Content-Language: en-US
To: Bernard Aboba <bernard.aboba@gmail.com>, Roland.Schott@telekom.de
Cc: avt@ietf.org
References: <FR2P281MB17972F344A5C1A20ED10D42187B79@FR2P281MB1797.DEUP281.PROD.OUTLOOK.COM> <C9A8F005-5AE3-4208-847B-CB3A08CC9856@gmail.com>
From: Joerg Ott <ott@in.tum.de>
In-Reply-To: <C9A8F005-5AE3-4208-847B-CB3A08CC9856@gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/w6JaHJO_vcx6zD7BBZSzZQeulRQ>
Subject: Re: [AVTCORE] Call for Adoption (CfA): RTP over QUIC
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Jun 2022 16:44:59 -0000

Quickly on the two points inline:

> I support adoption of RTP over QUIC.
> 
> I do have two concerns, though:
> 
> 1. The draft currently does not address how data would be multiplexed 
> with media. Part of the appeal of QUIC transport is the potential 
> ability to handle both data and media within a single QUIC connection.

We do have a flow identifier to demuxing and we have initial wording
on mixing real-time and possibly non-real-time data especially
concerning congestion control.  Likely not all will be handled by
the doc since, at some point, we get into too many application
specifics.  But the basic mechanisms will be in place.

> 2. WebTransport support. Currently the draft does not support RTP over 
> WebTransport.

This is something to be looked at closer.  The discussion with David
showed that it is non-trivial to get the ALPN allocations and all the
implications right.

Jörg

>> On Jun 25, 2022, at 08:56, Roland.Schott@telekom.de wrote:
>>
>> 
>>
>> * I support adoption of "RTP over QUIC".
>>
>> Thanks
>>
>> Roland
>>
>> *Von:* avt <avt-bounces@ietf.org> *Im Auftrag von * Bernard Aboba
>> *Gesendet:* Freitag, 24. Juni 2022 19:59
>> *An:* IETF AVTCore WG <avt@ietf.org>
>> *Betreff:* [AVTCORE] Call for Adoption (CfA): RTP over QUIC
>>
>> This is a Call for Adoption (CfA) of "RTP over QUIC".    The draft is 
>> available for inspection here:
>>
>> https://datatracker.ietf.org/doc/html/draft-engelbart-rtp-over-quic 
>> <https://datatracker.ietf.org/doc/html/draft-engelbart-rtp-over-quic>
>>
>> The Github repo used to track issues is here:
>>
>> https://github.com/mengelbart/rtp-over-quic-draft 
>> <https://github.com/mengelbart/rtp-over-quic-draft>
>>
>> The Call for Adoption will run until midnight Pacific Time on Monday, 
>> July 11, 2022.
>>
>> In response, please indicate one of the following:
>>
>> * I support adoption of "RTP over QUIC".
>>
>> * I object to adoption of "RTP over QUIC" due to the following open 
>> Issues <link to filed issues>
>>
>> Bernard
>>
>> For the Chairs
>>
>> _______________________________________________
>> Audio/Video Transport Core Maintenance
>> avt@ietf.org
>> https://www.ietf.org/mailman/listinfo/avt
> 
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt