[rtcweb] #2: Section 7.1
"rtcweb issue tracker" <trac+rtcweb@trac.tools.ietf.org> Mon, 22 October 2012 22:58 UTC
Return-Path: <trac+rtcweb@trac.tools.ietf.org>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C23B521F8470 for <rtcweb@ietfa.amsl.com>; Mon, 22 Oct 2012 15:58:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VOWhSXdK7ygU for <rtcweb@ietfa.amsl.com>; Mon, 22 Oct 2012 15:58:38 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id 3B01D21F844C for <rtcweb@ietf.org>; Mon, 22 Oct 2012 15:58:37 -0700 (PDT)
Received: from localhost ([127.0.0.1]:55142 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from <trac+rtcweb@trac.tools.ietf.org>) id 1TQQwx-0003iW-Cw; Tue, 23 Oct 2012 00:58:23 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: rtcweb issue tracker <trac+rtcweb@trac.tools.ietf.org>
X-Trac-Version: 0.12.2
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.2, by Edgewall Software
To: csp@csperkins.org, bernard_aboba@hotmail.com
X-Trac-Project: rtcweb
Date: Mon, 22 Oct 2012 22:58:23 -0000
X-URL: http://tools.ietf.org/rtcweb/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/rtcweb/trac/ticket/2
Message-ID: <066.81f7a0339f5b268a5112f46329622778@trac.tools.ietf.org>
X-Trac-Ticket-ID: 2
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: csp@csperkins.org, bernard_aboba@hotmail.com, rtcweb@ietf.org
X-SA-Exim-Mail-From: trac+rtcweb@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
X-Mailman-Approved-At: Tue, 23 Oct 2012 01:27:04 -0700
Cc: rtcweb@ietf.org
Subject: [rtcweb] #2: Section 7.1
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 22:58:40 -0000
#2: Section 7.1 Section 7.1 states: The circuit breaker defines a conservative boundary condition for safe operation, chosen such that applications that trigger the circuit breaker will almost certainly be causing severe network congestion. [BA] While it is true that when circuit breakers are triggered it is likely that very severe network congestion is occurring along the path, severe network congestion (or even a congestive collapse) will not necessarily trigger the circuit breakers. For example, one of the circuit breakers is only triggered if *no* packets are received; even in a congestive collapse, *some* packets will get through. Therefore the lack of circuit breaker triggering does not imply that an application is behaving "conservatively" or safely. Recommend change to: "Circuit breakers are designed to enable applications to recognize and react to situations of extreme network congestion. However, since circuit breakers may not be triggered until congestion becomes extreme, circuit breakers are not a substitute for congestion control and applications implementing circuit breakers cannot be considered "conservative" or "safe"." -- --------------------------------+------------------------ Reporter: bernard_aboba@… | Owner: csp@… Type: defect | Status: new Priority: major | Milestone: milestone1 Component: rtp-usage | Version: 1.0 Severity: Active WG Document | Keywords: --------------------------------+------------------------ Ticket URL: <http://trac.tools.ietf.org/wg/rtcweb/trac/ticket/2> rtcweb <http://tools.ietf.org/rtcweb/>
- [rtcweb] #2: Section 7.1 rtcweb issue tracker
- Re: [rtcweb] #2: Section 7.1 rtcweb issue tracker