Re: [AVTCORE] [R-C] Fwd: I-D Action: draft-perkins-avtcore-rtp-circuit-breakers-00.txt
Harald Alvestrand <harald@alvestrand.no> Tue, 06 March 2012 07:53 UTC
Return-Path: <harald@alvestrand.no>
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 5047121F8797 for <avt@ietfa.amsl.com>; Mon, 5 Mar 2012 23:53:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.42
X-Spam-Level:
X-Spam-Status: No, score=-110.42 tagged_above=-999 required=5 tests=[AWL=0.178, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EdEw1Zd6KCYW for <avt@ietfa.amsl.com>; Mon, 5 Mar 2012 23:53:01 -0800 (PST)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 2324B21F878B for <avt@ietf.org>; Mon, 5 Mar 2012 23:53:01 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 9FAE939E107; Tue, 6 Mar 2012 08:52:59 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gmH3t0Te-deA; Tue, 6 Mar 2012 08:52:58 +0100 (CET)
Received: from [192.168.11.193] (c213-89-143-9.bredband.comhem.se [213.89.143.9]) by eikenes.alvestrand.no (Postfix) with ESMTPS id 6D6CE39E090; Tue, 6 Mar 2012 08:52:58 +0100 (CET)
Message-ID: <4F55C25A.9010407@alvestrand.no>
Date: Tue, 06 Mar 2012 08:52:58 +0100
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Colin Perkins <csp@csperkins.org>
References: <20120305201759.24406.49431.idtracker@ietfa.amsl.com> <766FE318-7DE3-4481-B3C4-C45F2A94C881@csperkins.org>
In-Reply-To: <766FE318-7DE3-4481-B3C4-C45F2A94C881@csperkins.org>
Content-Type: multipart/alternative; boundary="------------000708040804020905030709"
Cc: rtp-congestion@alvestrand.no, "avt@ietf.org WG" <avt@ietf.org>
Subject: Re: [AVTCORE] [R-C] Fwd: I-D Action: draft-perkins-avtcore-rtp-circuit-breakers-00.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 06 Mar 2012 07:53:02 -0000
On 03/06/2012 12:32 AM, Colin Perkins wrote: > Here's our initial attempt at a "circuit breakers" draft for RTCWeb. Comments welcome - this is very much a straw-man for discussion, rather than a final solution. > > Colin > > > > Begin forwarded message: >> From: internet-drafts@ietf.org >> Subject: I-D Action: draft-perkins-avtcore-rtp-circuit-breakers-00.txt >> Date: 5 March 2012 20:17:59 GMT >> To: i-d-announce@ietf.org >> Reply-To: internet-drafts@ietf.org >> >> >> A New Internet-Draft is available from the on-line Internet-Drafts directories. >> >> Title : RTP Congestion Control: Circuit Breakers for Unicast Sessions >> Author(s) : Colin Perkins >> Varun Singh >> Filename : draft-perkins-avtcore-rtp-circuit-breakers-00.txt >> Pages : 14 >> Date : 2012-03-05 >> >> The Real-time Transport Protocol (RTP) is widely used for telephony, >> video conferencing, and telepresence applications. These >> applications are often used over best-effort UDP/IP networks. If >> congestion control is not implemented then network congestion will >> deteriorate the user's multimedia experience. This document does not >> propose a congestion control algorithm. Instead, it specifies a >> minimal set of "circuit-breakers". Circuit-breakers are conditions >> under which an RTP flow should cease to transmit media to protect the >> network from excessive congestion. It is expected that all RTP >> applications running on best-effort networks will be able to run >> without triggering these circuit breakers in normal operation. >> >> >> A URL for this Internet-Draft is: >> http://www.ietf.org/internet-drafts/draft-perkins-avtcore-rtp-circuit-breakers-00.txt Thanks for this work! A few questions (to make sure I get them noted down): Section 4.1: Accordingly, if a sender of RTP data packets receives two or more consecutive RTCP RR packets from the same receiver that correspond to its transmission and have a non-increasing extended highest sequence number received field, then that sender SHOULD cease transmission. If I see RTCP packets with 1: highest sequence number = 2 2: highest sequence number = 2 3: highest sequence number = 2 do I cease transmission after packet 3 has arrived, or after packet 2 has arrived? I *think* the logical time is after packet 3 has arrived, but I'm a little unsure that the words are unambiguously saying that; it's not 100% clear to me whether packet 1 is considered included in the set of "non-increasing highest sequence number". Section 4.2: Is it reasonable to replace, for the purposes of this calculation, "an order of magnitude" with "a factor of ten"? (for those who don't have a physics background, putting text somewhere that says that an order of magnitude is "somewhere around a factor of ten" might be appropriate.) We might also want to add the words about doing a dramatically reduced rate if we can from section 4.1 here, factor it out as a general statement, or say that it is not appropriate here if it's not. Security considerations (missing section): For an end node that implements this specification, an active attacker can cut the transmission by faking two RTCP packets that get accepted instead of the recipient's RTCP packets. This may be worthy of a note, and pointer to appropriate defenses. Good stuff! Harald
- Re: [AVTCORE] [R-C] Fwd: I-D Action: draft-perkin… Harald Alvestrand
- [AVTCORE] Fwd: I-D Action: draft-perkins-avtcore-… Colin Perkins
- Re: [AVTCORE] [R-C] Fwd: I-D Action: draft-perkin… Varun Singh
- Re: [AVTCORE] [R-C] Fwd: I-D Action: draft-perkin… Harald Alvestrand
- Re: [AVTCORE] [R-C] Fwd: I-D Action: draft-perkin… Varun Singh
- Re: [AVTCORE] [R-C] I-D Action: draft-perkins-avt… Colin Perkins
- [AVTCORE] rtp-circuit-breakers-00 when not using … James M. Polk
- Re: [AVTCORE] [R-C] Fwd: I-D Action: draft-perkin… Harald Alvestrand
- Re: [AVTCORE] [R-C] Fwd: I-D Action: draft-perkin… Colin Perkins
- Re: [AVTCORE] [R-C] Fwd: I-D Action: draft-perkin… Harald Alvestrand
- Re: [AVTCORE] I-D Action: draft-perkins-avtcore-r… Colin Perkins
- Re: [AVTCORE] [R-C] I-D Action: draft-perkins-avt… Varun Singh
- Re: [AVTCORE] Fwd: I-D Action: draft-perkins-avtc… Mark Handley
- Re: [AVTCORE] rtp-circuit-breakers-00 when not us… Colin Perkins