IETF Logo Mail Archive

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

Roman Shpount <roman@telurix.com> Tue, 17 May 2022 03:48 UTC

Return-Path: <roman@telurix.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 C0100C079B47 for <avt@ietfa.amsl.com>; Mon, 16 May 2022 20:48:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, 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 (1024-bit key) header.d=telurix.com
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 6dJA-xr9kSEu for <avt@ietfa.amsl.com>; Mon, 16 May 2022 20:48:13 -0700 (PDT)
Received: from mail-qt1-x835.google.com (mail-qt1-x835.google.com [IPv6:2607:f8b0:4864:20::835]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 DA786C079B55 for <avt@ietf.org>; Mon, 16 May 2022 20:48:13 -0700 (PDT)
Received: by mail-qt1-x835.google.com with SMTP id i20so13510033qti.11 for <avt@ietf.org>; Mon, 16 May 2022 20:48:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=VIUeN8xeM3JzC9Yvd7ZVdhBTocX7Ad92M0z5IcNE9YA=; b=B8dlok98sbot6lA7blLcarO/yxHOjiEzMzoVs7hKtV0eAP6XeUbVUCQ08chrTd6uFv QUZrAyvqoQe5M6MFukBKeSB7PH5zHDF+1YABBPJTVbZ3lXLgEMYUNXLZAhhrBYD0upoU MF3BHHkgfdq7dMUwrdzffhhwsymBSOkCyFIpc=
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=VIUeN8xeM3JzC9Yvd7ZVdhBTocX7Ad92M0z5IcNE9YA=; b=cCzlIRSmWjGxDYKt4uBHrAXCOGSclmNXWXSR/miQnTqeeltyOytGkNdptZQTcMNoTc mTzgKBD4lMuAf80OoGtMD8D1oNiO2Io5JRkqMLroCi6NqELcH1hxRLcOuwwLWjeCy9r3 IKbLzNk0vSCAgLZjMzD8qGyDaX4TgWQBsd5KgmqAHwSkK1i8/kEXHzoGVh5FzqgkbEk4 kQ8zfY3AZllFwaCeRQXpAIdTf2M9wQrTBiB4HZ7KIoM28tLupG9j9F7LBuK9GMp+VVym b1vhYjV6j0cWIeam2O7pLr4Ju4gRVHAOU0wNFGPnqp9y78h+tECwgtpy5rUcl9XhwXsX BFeQ==
X-Gm-Message-State: AOAM530r0bkO+cSVDVd2vzWkRrMY9t0Ctz36q015csJkW5NIVxiPSnMi thRjkYfKzFV7eNk60DNWG/lWVsK+0E+wlg==
X-Google-Smtp-Source: ABdhPJxyrnvmbcJDC2MBuUhpWhPDsij05v2lf0PQPMwnry1lNdKbI4qiG8+EyejFN6o4u79JXuWwSg==
X-Received: by 2002:ac8:7f82:0:b0:2f3:fbbd:476f with SMTP id z2-20020ac87f82000000b002f3fbbd476fmr17986599qtj.174.1652759292427; Mon, 16 May 2022 20:48:12 -0700 (PDT)
Received: from mail-yw1-f177.google.com (mail-yw1-f177.google.com. [209.85.128.177]) by smtp.gmail.com with ESMTPSA id bi4-20020a05620a318400b0069fcf0da629sm6921616qkb.134.2022.05.16.20.48.12 for <avt@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 16 May 2022 20:48:12 -0700 (PDT)
Received: by mail-yw1-f177.google.com with SMTP id 00721157ae682-2fee9fe48c2so52632747b3.3 for <avt@ietf.org>; Mon, 16 May 2022 20:48:12 -0700 (PDT)
X-Received: by 2002:a81:5d42:0:b0:2ff:152d:2a2e with SMTP id r63-20020a815d42000000b002ff152d2a2emr5027073ywb.302.1652759291916; Mon, 16 May 2022 20:48:11 -0700 (PDT)
MIME-Version: 1.0
References: <CAKKJt-dvotzuaK66T8WQd7YgNLNr_6vqa4W8-z=5FvujpGWA=A@mail.gmail.com> <CAD5OKxs66qObT3YY-FNuxNE_5cE6TwqWt-W4vzWKNCP=x70SWg@mail.gmail.com> <4BFD72D7-FC98-4A07-8408-5CE9CE7FD423@live555.com>
In-Reply-To: <4BFD72D7-FC98-4A07-8408-5CE9CE7FD423@live555.com>
From: Roman Shpount <roman@telurix.com>
Date: Mon, 16 May 2022 23:48:01 -0400
X-Gmail-Original-Message-ID: <CAD5OKxsPmF48oTsm7X04CRb-OauyikaYKeYyrm5jpPHNc8GzFg@mail.gmail.com>
Message-ID: <CAD5OKxsPmF48oTsm7X04CRb-OauyikaYKeYyrm5jpPHNc8GzFg@mail.gmail.com>
To: Ross Finlayson <finlayson@live555.com>
Cc: IETF AVTCore WG <avt@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007e77ab05df2d0226"
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/DMk7cKmkImK7Vsbg_iTrBJWI0sg>
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:48:17 -0000

On Mon, May 16, 2022 at 11:40 PM Ross Finlayson <finlayson@live555.com>
wrote:

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

RTP, DTLS, and SCTP are also UDP-based protocols. They all can run over TCP
(see  RFC 4571) when the ICE-TCP (RFC 6544) candidate is used.

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.
>
>
I can see a few problems that it can solve:

1. Run real-time media over WebTransport
2. Get rid of SCTP for data channels in the WebRTC stack
3. Replace DTLS in secure RTP channel setup by using a more modern protocol
with cleaner implementation and faster connection establishment
4. Better NAT and firewall traversal with QUIC vs. plain SRTP
_____________
Roman Shpount

v2.23.0 | Report a Bug | By Email