Re: [AVTCORE] Last question about AVP profiles for RTP over QUIC (was: Re: Registering AVP Profiles for RTP over QUIC)

Bernard Aboba <bernard.aboba@gmail.com> Sun, 26 June 2022 14:58 UTC

Return-Path: <bernard.aboba@gmail.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 AF192C14CF1D for <avt@ietfa.amsl.com>; Sun, 26 Jun 2022 07:58:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Level:
X-Spam-Status: No, score=-2.109 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, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 VJBzqTZr3CO4 for <avt@ietfa.amsl.com>; Sun, 26 Jun 2022 07:58:48 -0700 (PDT)
Received: from mail-pj1-x1033.google.com (mail-pj1-x1033.google.com [IPv6:2607:f8b0:4864:20::1033]) (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 63179C14F728 for <avt@ietf.org>; Sun, 26 Jun 2022 07:58:48 -0700 (PDT)
Received: by mail-pj1-x1033.google.com with SMTP id go6so7051783pjb.0 for <avt@ietf.org>; Sun, 26 Jun 2022 07:58:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:content-transfer-encoding:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=xchZeKaXSRz8vjWrwqogy4Fso7BV5QreZkHzbKWHiGs=; b=nUt+ILJ6c1QHbGeQ/8V7KO8v65eUWcx6rwfIUB+XGTIodSofpB9FzY6HuWy8778AU4 0GmfEpU35uMg2jBJoa2FPOLGv2LUWaYh545NN/f/TcdkuICnRECn+ycNI6aLoRDq5nfS BDiGpk5+zl8VlS8/dS+1jkIFWUNvmx1LOBtMNRmovT9+ezMq1DvrPlioEu2l4StV80UC 7b9iFAA/TquQoDoLM9WNV/lHLtCGLNUHYAEz6HASQXe+LXC5NL3mqYtTiGhnVBSKAukB 4w+cLFvRjZs+sf5gPuhCbT/WjY04yRWlfK0TllYGYTFuy+yxQnXKrlggFitLE905NIjF p88A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=xchZeKaXSRz8vjWrwqogy4Fso7BV5QreZkHzbKWHiGs=; b=g9zrYYi/cAaMmK7htZOMLVTMg2ErRvA1W8TPvLLQUTC9b2YE/ZuJl/HlGmTPki+oUT fKhDDCUxV+q+Vh0M1D3elHQuZdFMpcIxd1VqNJuuJp/SmPHDKU4MvvvGjycwc+FrTKq9 BxCvO96F/P2j1SZtxP0KeOS9Q1l2FTSCvVXW1ViBnm27wGzNpY91WLx9bt0L7YCozr+1 vtsTPzEv98kn4XA7CsoHtrZzH7fFajZidEGeEJRMrPHsYSPRi/RwByycs7znprqKZF+R OyDvO3uqB0jdNkdfOFygAIYyAuIFJ69p0Xr8aivtI7kxMA2AdKQbrZC1h7WYc9/nfQJZ dzcQ==
X-Gm-Message-State: AJIora/SA1bRevTOLHFKOIp0q5q9ji0+a/y9J+yDHS466e0hIitGZp0E EiTvDsEwhutU4J20Ka8AJqYYapFl97w=
X-Google-Smtp-Source: AGRyM1uCtwcbp/kMo+DUcZ12YALXqGBVAGFbJ3SWZUGrDLMCoeWoDCktX1nSDOQIP6stY6GrxBLHbA==
X-Received: by 2002:a17:902:cec4:b0:16a:16d6:f67f with SMTP id d4-20020a170902cec400b0016a16d6f67fmr9388261plg.139.1656255527184; Sun, 26 Jun 2022 07:58:47 -0700 (PDT)
Received: from smtpclient.apple (c-24-16-156-188.hsd1.wa.comcast.net. [24.16.156.188]) by smtp.gmail.com with ESMTPSA id cu7-20020a056a00448700b00525373aac7csm5322176pfb.26.2022.06.26.07.58.46 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 26 Jun 2022 07:58:46 -0700 (PDT)
From: Bernard Aboba <bernard.aboba@gmail.com>
X-Google-Original-From: Bernard Aboba <Bernard.Aboba@gmail.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
Date: Sun, 26 Jun 2022 07:58:45 -0700
Message-Id: <DD9293D4-329A-4934-8E03-1D5EB7244D84@gmail.com>
References: <CAD5OKxvkWB-xcYDCtuOTq0_um-4UA=3wHphYDwJnE8T9mettfQ@mail.gmail.com>
Cc: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, IETF AVTCore WG <avt@ietf.org>
In-Reply-To: <CAD5OKxvkWB-xcYDCtuOTq0_um-4UA=3wHphYDwJnE8T9mettfQ@mail.gmail.com>
To: Roman Shpount <roman@telurix.com>
X-Mailer: iPhone Mail (19F77)
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/e9YZwR9FXMI_ucaez-KqbktLnTg>
Subject: Re: [AVTCORE] Last question about AVP profiles for RTP over QUIC (was: Re: Registering AVP Profiles for 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 14:58:48 -0000

> On Jun 25, 2022, at 22:17, Roman Shpount <roman@telurix.com> wrote:.
> 
> I do not think any work needs to be done by the QUIC working group. No work was required for DTLS or SCTP. This is an ICE-specific issue and is quite different from a typical QUIC to HTTP/2 fallback.

[BA] Agreed. In the case of RTP over WebTransport, the fallback is from HTTP/3 over QUIC to HTTP/2 over TCP, which can occur automatically. WebTransport is a client/server protocol so ICE would not be involved (or SDP, for that matter).