Re: [AVTCORE] I-D Action: draft-ietf-avtcore-cc-feedback-message-04.txt

Colin Perkins <csp@csperkins.org> Sun, 14 July 2019 16:39 UTC

Return-Path: <csp@csperkins.org>
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 6D016120111 for <avt@ietfa.amsl.com>; Sun, 14 Jul 2019 09:39:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sz4UpY-ubrzI for <avt@ietfa.amsl.com>; Sun, 14 Jul 2019 09:39:34 -0700 (PDT)
Received: from haggis.mythic-beasts.com (haggis.mythic-beasts.com [IPv6:2a00:1098:0:86:1000:0:2:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 591C11200C5 for <avt@ietf.org>; Sun, 14 Jul 2019 09:39:34 -0700 (PDT)
Received: from [81.187.2.149] (port=46414 helo=[192.168.0.81]) by haggis.mythic-beasts.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <csp@csperkins.org>) id 1hmhX6-00084d-My for avt@ietf.org; Sun, 14 Jul 2019 17:39:33 +0100
From: Colin Perkins <csp@csperkins.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_61455AD4-7E2F-4D6A-AC2D-3CC1B74F538E"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Sun, 14 Jul 2019 17:39:27 +0100
References: <156262748144.1089.14095324486332907632@ietfa.amsl.com>
To: IETF AVTCore WG <avt@ietf.org>
In-Reply-To: <156262748144.1089.14095324486332907632@ietfa.amsl.com>
Message-Id: <F6062B09-9503-4FAF-B964-E5830C26284A@csperkins.org>
X-Mailer: Apple Mail (2.3445.104.11)
X-BlackCat-Spam-Score: 14
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/q64SMgLDHiBr0LNM-kJTaO4aV8A>
Subject: Re: [AVTCORE] I-D Action: draft-ietf-avtcore-cc-feedback-message-04.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.29
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, 14 Jul 2019 16:39:36 -0000

> On 9 Jul 2019, at 00:11, Internet-Drafts@ietf.org wrote:
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Audio/Video Transport Core Maintenance WG of the IETF.
> 
>        Title           : RTP Control Protocol (RTCP) Feedback for Congestion Control
>        Authors         : Zaheduzzaman Sarker
>                          Colin Perkins
>                          Varun Singh
>                          Michael A. Ramalho
> 	Filename        : draft-ietf-avtcore-cc-feedback-message-04.txt
> 	Pages           : 15
> 	Date            : 2019-07-08
> 
> Abstract:
>   This document describes an RTCP feedback message intended to enable
>   congestion control for interactive real-time traffic using RTP.  The
>   feedback message is designed for use with a sender-based congestion
>   control algorithm, in which the receiver of an RTP flow sends RTCP
>   feedback packets to the sender containing the information the sender
>   needs to perform congestion control.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-avtcore-cc-feedback-message/ <https://datatracker.ietf.org/doc/draft-ietf-avtcore-cc-feedback-message/>

This version addresses feedback received during IETF-104. It does not change the packet format or signalling, but rather makes a number of clarifications:
add an example of use of the "a=rtcp-fb:" attribute;
clarify that congestion control feedback is sent for FEC and retransmission packets, if used;
clarify that congestion control feedback signalling is IDENTICAL-PER-PT when used with the SDP BUNDLE;
clarify that if an SDP offer indicates support for several different ways of providing congestion control feedback, the receiver SHOULD pick its preferred mechanism use use it consistently;
clarify that feedback reports indicating that packets were lost are not explicit requests for retransmission;
clarify that large feedback packets might need to be split across multiple RTCP packets if the RTCP bandwidth fraction is misconfigured; and
add a section on the desired congestion response in cases where congestion control feedback packets are lost.
The only remaining open issue is to add some discussion of how this solution compares to the Holmer draft, in particular to discuss the trade-offs around a single sequence number space vs the per-flow sequence numbers used in this draft.

-- 
Colin Perkins
https://csperkins.org/