IETF Logo Mail Archive

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

Joerg Ott <ott@in.tum.de> Mon, 27 June 2022 08:46 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 87C5FC15D881 for <avt@ietfa.amsl.com>; Mon, 27 Jun 2022 01:46:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.885
X-Spam-Level:
X-Spam-Status: No, score=-3.885 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, 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 MBDbZLR4R937 for <avt@ietfa.amsl.com>; Mon, 27 Jun 2022 01:46:05 -0700 (PDT)
Received: from mailout1.rbg.tum.de (mailout1.rbg.tum.de [131.159.0.201]) (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 E1C87C15D879 for <avt@ietf.org>; Mon, 27 Jun 2022 01:46:03 -0700 (PDT)
Received: from mailrelay1.rbg.tum.de (mailrelay1.in.tum.de [131.159.254.14]) by mailout1.rbg.tum.de (Postfix) with ESMTPS id CB0CDB0C; Mon, 27 Jun 2022 10:46:00 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=in.tum.de; s=20220209; t=1656319560; bh=kKSvkbKZveM7ONrXpuVBOfydQkPaA5tlorgRfqyOxmY=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=bvl/HqHb7PDCEMl6WWNJwcF7qmPfgK73PS6K2Pq9STOBxQMbrtN73oxYV7GIgC7vX 4bSVv3gHb80nSDYTRJAqvCEdMvCl+17D2ogZbPxyZiof/IZUAn/QPHO7z9o2uciXPX oV8MRzVYuww8hmoLe6So6LOi9j338sLumO/tOXMvnoul45PQZtu+YS7bWwncBkIcFx IQa/Fhqfwfd+b8Fd01pPwewfl6MLPWW2wkNDN1FAPuxV5AMb878xeCXvVSvADtxJwk Lv/EK1rmj+xsPrngHilXA/rVdXldz1Bl4i6vmISK17mcQ80Q2wCTUPn01HGqVNo7LE LgQJ+DeoXCX7w==
Received: by mailrelay1.rbg.tum.de (Postfix, from userid 112) id C85193F6; Mon, 27 Jun 2022 10:46:00 +0200 (CEST)
Received: from mailrelay1.rbg.tum.de (localhost [127.0.0.1]) by mailrelay1.rbg.tum.de (Postfix) with ESMTP id A5CCB3F5; Mon, 27 Jun 2022 10:46:00 +0200 (CEST)
Received: from mail.in.tum.de (vmrbg426.in.tum.de [131.159.0.73]) by mailrelay1.rbg.tum.de (Postfix) with ESMTPS id A3F013F1; Mon, 27 Jun 2022 10:46:00 +0200 (CEST)
Received: by mail.in.tum.de (Postfix, from userid 112) id A15A34A02B0; Mon, 27 Jun 2022 10:46:00 +0200 (CEST)
Received: (Authenticated sender: ott) by mail.in.tum.de (Postfix) with ESMTPSA id A0E994A006E; Mon, 27 Jun 2022 10:45:58 +0200 (CEST) (Extended-Queue-bit xtech_ep@fff.in.tum.de)
Message-ID: <bc37feb2-630b-ba93-e402-c134c9029053@in.tum.de>
Date: Mon, 27 Jun 2022 10:45:56 +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: Roland.Schott@telekom.de, bernard.aboba@gmail.com
Cc: avt@ietf.org
References: <FR2P281MB17972F344A5C1A20ED10D42187B79@FR2P281MB1797.DEUP281.PROD.OUTLOOK.COM> <C9A8F005-5AE3-4208-847B-CB3A08CC9856@gmail.com> <8e44acd9-d723-2b4d-2218-379f205c0d99@in.tum.de> <FR2P281MB1797051C090D3642B07593F987B69@FR2P281MB1797.DEUP281.PROD.OUTLOOK.COM>
From: Joerg Ott <ott@in.tum.de>
In-Reply-To: <FR2P281MB1797051C090D3642B07593F987B69@FR2P281MB1797.DEUP281.PROD.OUTLOOK.COM>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/GqiAlXzUEJxLahReULEmsijDOUo>
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: Mon, 27 Jun 2022 08:46:09 -0000

Hi,

I don't think so: effectively adoption means agreeing on the problem to
solve and the rough direction and then handing change control over to
the WG, where the authors become "editors" to reflect consensus of the
group and further the work.

Jörg

On 26.06.22 21:56, Roland.Schott@telekom.de wrote:
> Hi,
> 
> does this need to be clarified before the draft can be adopted or
> is this something that can be worked on after adoption of the draft?
> 
> Roland
> 
> 
> -----Ursprüngliche Nachricht-----
> Von: Joerg Ott <ott@in.tum.de>
> Gesendet: Sonntag, 26. Juni 2022 18:45
> An: Bernard Aboba <bernard.aboba@gmail.com>; Schott, Roland <Roland.Schott@telekom.de>
> Cc: avt@ietf.org
> Betreff: Re: [AVTCORE] Call for Adoption (CfA): RTP over QUIC
> 
> 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

v2.23.0 | Report a Bug | By Email