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

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Tue, 05 March 2024 17:17 UTC

Return-Path: <spencerdawkins.ietf@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 3BB49C180B56 for <avt@ietfa.amsl.com>; Tue, 5 Mar 2024 09:17:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=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=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 uQWPmkdJ-p1d for <avt@ietfa.amsl.com>; Tue, 5 Mar 2024 09:17:39 -0800 (PST)
Received: from mail-pg1-x52a.google.com (mail-pg1-x52a.google.com [IPv6:2607:f8b0:4864:20::52a]) (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 64A41C180B50 for <avt@ietf.org>; Tue, 5 Mar 2024 09:17:39 -0800 (PST)
Received: by mail-pg1-x52a.google.com with SMTP id 41be03b00d2f7-5d8ddbac4fbso5615857a12.0 for <avt@ietf.org>; Tue, 05 Mar 2024 09:17:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1709659058; x=1710263858; darn=ietf.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=1mVzaXOkaH/56Uf6BBoWzSL9Cb20gRdeWKh6hWPCrrc=; b=JvT4SDo9Yt9cwPLRVbJNDT54ZXvWxZPuFbguSw9fZekLEZRsWd7x1/RpYsDXRBFKTh RTSUEkZGx4egEfSFdNl2wOq6t7GI8EFWU0KTwK8NvVDlI91J3JwY+N7D1mYFyMIrhUpD eC/odixPlJQ7dCe+Q+OYeYYVDav4SpIp68JTKJNRfKR8tbLaHmGqxrSCp1XYDrw1B3mI sjC6bGtrKxAfxlQoFb/8fgezF7iyAy5+phu15NM7HFnvrBs6JmvKqfRcKqJlxeeuZqzm 319GyEswbdVEvgP/WXJEMcH1GmGXsUqMr4bnfLL6LW4on4jej09xMOSjHsSUYXh7ZsPU rLFA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1709659058; x=1710263858; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=1mVzaXOkaH/56Uf6BBoWzSL9Cb20gRdeWKh6hWPCrrc=; b=Emswrj/hEvh3F5NgwZdGHye8dV9OWQ555ALvndvJXhbY71x2f5hBJYyqJoRCkNw4Ki qx7lA7B7hyeC1z16W103kBpWzzUjgEA2xMQI1fzEHLNJ7jefTxs+jTYWX1F5QhXdb/bA fUbH95h0N2Tnk/B8/LAxZhJVOSte1GLJWwp4oB1cXb+hBoO0krPRX48Uu/IWDleb63vz jG/C/tl6OkZf02gONFZu4wnfZQGdTd0oKgeDdMdNW1wze35etMKES5sd2+Rf10G8EGlC lNgRHlyr++qj7VvHHyLnaqWTFnPDMtgwQobernx1Zo5nq8l9zfCwERE4TRu5+SzFOPnD Iagw==
X-Gm-Message-State: AOJu0Yw7CBcaOrzfXPU4UtXozI3eRWJKkqMl/s+RTDAxf/Ht1Lpzc7HW VBZvgpx4wxlAvU4MngDfwXH1mqYKLFvPonCOiFdrlp0IHDxT8N1S9htQuJXQh7BkBk6n7ZVjTyB agpLfLJz4ZpWHhxhFFgA4QZXs2FmWr4igDsY=
X-Google-Smtp-Source: AGHT+IHG7FiCUEP9UDyfPDV6F57dbzNF6FjIxgxKxyceOBp6qgEhawUFarhRvA9i2R90hrihaXkaxDVeGlXUW5ar/kY=
X-Received: by 2002:a05:6a20:c892:b0:1a1:4cd3:9d84 with SMTP id hb18-20020a056a20c89200b001a14cd39d84mr2817417pzb.34.1709659058347; Tue, 05 Mar 2024 09:17:38 -0800 (PST)
MIME-Version: 1.0
References: <170956895231.58675.5332920420860909319@ietfa.amsl.com>
In-Reply-To: <170956895231.58675.5332920420860909319@ietfa.amsl.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Tue, 05 Mar 2024 11:17:12 -0600
Message-ID: <CAKKJt-fLXT8m5q_kT5eWo+36iD0EVGJBDCGS9Tach6kgScMt7Q@mail.gmail.com>
To: IETF AVTCore WG <avt@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000dc24990612ed0469"
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/e-v96LkosGHuwgw9dmdJLNE7pBE>
Subject: [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 17:17:43 -0000

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
.

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>
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>
Cc: <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/

There is also an HTML version available at:
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

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts


_______________________________________________
Audio/Video Transport Core Maintenance
avt@ietf.org
https://www.ietf.org/mailman/listinfo/avt