Re: [AVTCORE] Fwd: I-D Action: draft-ietf-avtcore-rtp-over-quic-09.txt

Mathis Engelbart <mathis.engelbart@tum.de> Tue, 05 March 2024 18:22 UTC

Return-Path: <mathis.engelbart@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 772D9C14F69E for <avt@ietfa.amsl.com>; Tue, 5 Mar 2024 10:22:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.406
X-Spam-Level:
X-Spam-Status: No, score=-4.406 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, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 WdSR_gmeyaC2 for <avt@ietfa.amsl.com>; Tue, 5 Mar 2024 10:21:57 -0800 (PST)
Received: from postout2.mail.lrz.de (postout2.mail.lrz.de [129.187.255.138]) (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 5B45FC14F5F3 for <avt@ietf.org>; Tue, 5 Mar 2024 10:21:56 -0800 (PST)
Received: from lxmhs52.srv.lrz.de (localhost [127.0.0.1]) by postout2.mail.lrz.de (Postfix) with ESMTP id 4Tq3my2F47zyYY for <avt@ietf.org>; Tue, 5 Mar 2024 19:21:54 +0100 (CET)
Authentication-Results: postout.lrz.de (amavisd-new); dkim=pass (2048-bit key) reason="pass (just generated, assumed good)" header.d=tum.de
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tum.de; h= content-transfer-encoding:content-type:content-type:in-reply-to :from:from:references:content-language:subject:subject :user-agent:mime-version:date:date:message-id:received:received; s=tu-postout21; t=1709662912; bh=rBPfFtc7rbhVTy3fGKERf8ModQkBF8 C0oRJKiDfvyWY=; b=azH/asR1zpKr0fsKu6eA+NO/Fz6UwasF1/ddqCkSSwAysB f+yNe+fCAvQrGUCaWtJRpwn2kDoHvqHRa1Lp0o0jPq43CHaaH1UNr6Kt9LoJTRws KZVKYC8MGoLwMzEFARATmcXMEO3DoybUR4Cic13G6dvLQbLMHi79PmQR236MUjO8 Sg8Ye7OWNB5BpyQhb8rEyaeMowAs0HkJwbFxW9Wk1K8vdLT2wd0uVu/SePeS+WLC aVlvP6VQO+SGEICoMVQ0rH6zJ1he4pFj7GJjsHbA3ZVLJMucJ8u1YSaNudnJuxOE cl0DQ6FWyxkSR7fAyLHozfNxowkZBZkdUetnTQwQ==
X-Virus-Scanned: by amavisd-new at lrz.de in lxmhs52.srv.lrz.de
Received: from postout2.mail.lrz.de ([127.0.0.1]) by lxmhs52.srv.lrz.de (lxmhs52.srv.lrz.de [127.0.0.1]) (amavisd-new, port 20024) with LMTP id 9rFCYG_PI-tt for <avt@ietf.org>; Tue, 5 Mar 2024 19:21:52 +0100 (CET)
Received: from [IPV6:2003:ed:a72c:9058:81b0:cd73:6275:fb29] (p200300eda72c905881b0cd736275fb29.dip0.t-ipconnect.de [IPv6:2003:ed:a72c:9058:81b0:cd73:6275:fb29]) (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 postout2.mail.lrz.de (Postfix) with ESMTPSA id 4Tq3mw4jmXzyTX for <avt@ietf.org>; Tue, 5 Mar 2024 19:21:52 +0100 (CET)
Message-ID: <d25f848f-9b54-45de-948b-b33ca1e91d0c@tum.de>
Date: Tue, 05 Mar 2024 19:21:51 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-US
To: avt@ietf.org
References: <170956895231.58675.5332920420860909319@ietfa.amsl.com> <CAKKJt-fLXT8m5q_kT5eWo+36iD0EVGJBDCGS9Tach6kgScMt7Q@mail.gmail.com>
From: Mathis Engelbart <mathis.engelbart@tum.de>
In-Reply-To: <CAKKJt-fLXT8m5q_kT5eWo+36iD0EVGJBDCGS9Tach6kgScMt7Q@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/P2HbaIRjrjWeVyXj-iwZAiPMrpY>
Subject: Re: [AVTCORE] Fwd: I-D Action: draft-ietf-avtcore-rtp-over-quic-09.txt
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: Tue, 05 Mar 2024 18:22:02 -0000

Hi,

In addition to what Spencer mentioned, there is one more change worth 
pointing out: As discussed in the last interim meeting, we removed the 
multiplexing of RTP and RTCP with other protocols. The reason for this 
change is that we don't know what these other protocols will be.

If there is a specific use case for multiplexing a particular protocol 
with RTP and RTCP in the same QUIC connection, that can be done in a 
future document. That document can then describe how the multiplexing 
will work. That document may, of course, reference RoQ.

To reflect this change in ALPN, we also updated the ALPN token. RoQ now 
uses the ALPN token 'roq', while future documents describing the 
multiplexing of RoQ with other protocols must define their own ALPN token.

Best,
Mathis

On 3/5/24 18:17, Spencer Dawkins at IETF wrote:
> Dear RTP over QUIC fans,
> 
> Mathis and I have completed PRs for all of the issues that we talked 
> about during the recent virtual interim meeting (slides here 
> <https://datatracker.ietf.org/doc/slides-interim-2024-avtcore-01-sessa-avtcore-wg-virtual-interim-slides/>, minutes here <https://datatracker.ietf.org/doc/minutes-interim-2024-avtcore-01-202402131700/>).
> 
> We've merged most of them, and submitted this -09 revision. A diff from 
> the previous version is available at 
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-avtcore-rtp-over-quic-09 <https://author-tools.ietf.org/iddiff?url2=draft-ietf-avtcore-rtp-over-quic-09>.
> 
> In addition to the usual corrections and improvements, there's quite a 
> bit of entirely new text. You might pay special attention to these 
> sections - they're entirely new.
> 
>   * 8
>     <https://www.ietf.org/archive/id/draft-ietf-avtcore-rtp-over-quic-09.html#section-8>. Guidance on Choosing QUIC Streams, QUIC DATAGRAMs, or a Mixture <https://www.ietf.org/archive/id/draft-ietf-avtcore-rtp-over-quic-09.html#name-guidance-on-choosing-quic-s>
>   * 12.3
>     <https://www.ietf.org/archive/id/draft-ietf-avtcore-rtp-over-quic-09.html#section-12.3>. Coalescing RTP packets in single QUIC packet <https://www.ietf.org/archive/id/draft-ietf-avtcore-rtp-over-quic-09.html#name-coalescing-rtp-packets-in-s>
>   * 13
>     <https://www.ietf.org/archive/id/draft-ietf-avtcore-rtp-over-quic-09.html#section-13>. Directions for Future work <https://www.ietf.org/archive/id/draft-ietf-avtcore-rtp-over-quic-09.html#name-directions-for-future-work>
> 
> There's quite a lot of movement in Section 2 
> <https://www.ietf.org/archive/id/draft-ietf-avtcore-rtp-over-quic-09.html#section-2>. Terminology and Notation <https://www.ietf.org/archive/id/draft-ietf-avtcore-rtp-over-quic-09.html#name-terminology-and-notation>, but we also moved some of the text about congestion control from a terminology section to Section 7.1 <https://www.ietf.org/archive/id/draft-ietf-avtcore-rtp-over-quic-09.html#section-7.1>. Congestion Control at the Transport Layer <https://www.ietf.org/archive/id/draft-ietf-avtcore-rtp-over-quic-09.html#name-congestion-control-at-the-t>
> 
> Section 3.1 
> <https://www.ietf.org/archive/id/draft-ietf-avtcore-rtp-over-quic-09.html#section-3.1>. Motivations <https://www.ietf.org/archive/id/draft-ietf-avtcore-rtp-over-quic-09.html#name-motivations> LOOKS like a large chunk of new text, but it's simply text that was moved later in the document.
> 
> Next Steps - Mathis and I asked about WGLC for this document during the 
> previous virtual interim, and the meeting minutes said that seemed 
> realistic. If the working group is going to be responding to WGLC soon 
> after the AVTCORE session at IETF 119, and you want time for a careful 
> look, you might review where the document is now, in preparation for 
> discussion and feedback during the meeting.
> 
> We have two remaining issues:
> 
>   * Specify how the contents of the 0-RTT initial packet payload are
>     handled in RoQ
>     <https://github.com/mengelbart/rtp-over-quic-draft/issues/181> (this
>     one has proposed PR text here
>     <https://github.com/mengelbart/rtp-over-quic-draft/pull/184>), and
>   * General clean-up of the current draft #163
>     <https://github.com/mengelbart/rtp-over-quic-draft/issues/163> (this
>     one just says "proofread the draft before we request WGLC", and I
>     was working on PR text before the I-D submission cutoff, but we'll
>     do that "soon"). 
> 
> Comments on issues and PRs are welcome, as always.
> 
> Best,
> 
> Spencer
> 
> ---------- Forwarded message ---------
> From: <internet-drafts@ietf.org <mailto:internet-drafts@ietf.org>>
> Date: Mon, Mar 4, 2024 at 10:16 AM
> Subject: [AVTCORE] I-D Action: draft-ietf-avtcore-rtp-over-quic-09.txt
> To: <i-d-announce@ietf.org <mailto:i-d-announce@ietf.org>>
> Cc: <avt@ietf.org <mailto:avt@ietf.org>>
> 
> 
> Internet-Draft draft-ietf-avtcore-rtp-over-quic-09.txt is now available. 
> It is
> a work item of the Audio/Video Transport Core Maintenance (AVTCORE) WG 
> of the
> IETF.
> 
>     Title:   RTP over QUIC (RoQ)
>     Authors: Jörg Ott
>              Mathis Engelbart
>              Spencer Dawkins
>     Name:    draft-ietf-avtcore-rtp-over-quic-09.txt
>     Pages:   66
>     Dates:   2024-03-04
> 
> Abstract:
> 
>     This document specifies a minimal mapping for encapsulating Real-time
>     Transport Protocol (RTP) and RTP Control Protocol (RTCP) packets
>     within the QUIC protocol.  This mapping is called RTP over QUIC
>     (RoQ).  It also discusses how to leverage state from the QUIC
>     implementation in the endpoints, in order to reduce the need to
>     exchange RTCP packets and how to implement congestion control and
>     rate adaptation without relying on RTCP feedback.
> 
> The IETF datatracker status page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-over-quic/ 
> <https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-over-quic/>
> 
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-ietf-avtcore-rtp-over-quic-09.html 
> <https://www.ietf.org/archive/id/draft-ietf-avtcore-rtp-over-quic-09.html>
> 
> A diff from the previous version is available at:
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-avtcore-rtp-over-quic-09 <https://author-tools.ietf.org/iddiff?url2=draft-ietf-avtcore-rtp-over-quic-09>
> 
> Internet-Drafts are also available by rsync at:
> rsync.ietf.org::internet-drafts
> 
> 
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org <mailto:avt@ietf.org>
> https://www.ietf.org/mailman/listinfo/avt 
> <https://www.ietf.org/mailman/listinfo/avt>
> 
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt