IETF Logo Mail Archive

Re: [AVTCORE] Registering AVP Profiles for RTP over QUIC

Ross Finlayson <finlayson@live555.com> Tue, 17 May 2022 03:40 UTC

Return-Path: <finlayson@live555.com>
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 33D5FC079B4D for <avt@ietfa.amsl.com>; Mon, 16 May 2022 20:40:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
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 bQRAuD66lVcV for <avt@ietfa.amsl.com>; Mon, 16 May 2022 20:40:03 -0700 (PDT)
Received: from us.live555.com (us.live555.com [52.8.240.222]) (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 E73EEC079B47 for <avt@ietf.org>; Mon, 16 May 2022 20:40:03 -0700 (PDT)
Received: from smtpclient.apple (localhost.live555.com [IPv6:0:0:0:0:0:0:0:1]) by us.live555.com (8.16.1/8.16.1) with ESMTP id 24H3e1O8085388 for <avt@ietf.org>; Mon, 16 May 2022 20:40:02 -0700 (PDT) (envelope-from finlayson@live555.com)
From: Ross Finlayson <finlayson@live555.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.80.82.1.1\))
Date: Mon, 16 May 2022 21:40:01 -0600
References: <CAKKJt-dvotzuaK66T8WQd7YgNLNr_6vqa4W8-z=5FvujpGWA=A@mail.gmail.com> <CAD5OKxs66qObT3YY-FNuxNE_5cE6TwqWt-W4vzWKNCP=x70SWg@mail.gmail.com>
To: IETF AVTCore WG <avt@ietf.org>
In-Reply-To: <CAD5OKxs66qObT3YY-FNuxNE_5cE6TwqWt-W4vzWKNCP=x70SWg@mail.gmail.com>
Message-Id: <4BFD72D7-FC98-4A07-8408-5CE9CE7FD423@live555.com>
X-Mailer: Apple Mail (2.3696.80.82.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/7Hh8iU7kvSaxjILtEizCm8ifJcs>
Subject: Re: [AVTCORE] Registering AVP Profiles for RTP over QUIC
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.34
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: Tue, 17 May 2022 03:40:05 -0000


> On May 16, 2022, at 8:46 PM, Roman Shpount <roman@telurix.com> wrote:
> One more question: How would you signal RTP over QUIC when it is encapsulated using the RFC 4571 framing method? Is it going to be TCP/QUIC/RTP/AVPF?
> 
> You would end up with this encoding when RTP over QUIC is used on top of TCP

What does “QUIC on top of TCP" even mean, given that QUIC is a UDP-based protocol?

In any case, it seems to me that this whole discussion is begging the question.  First, we should come to consensus as to what problem(s) we are trying to solve.  Then, and only then, we can decide whether 'RTP over QUIC’ is an appropriate way to solve these problem(s).

It may well turn out that 'RTP over QUIC’ is a solution in search of a problem.

	Ross.

v2.23.0 | Report a Bug | By Email