Re: [rtcweb] consent freshness vs. circuit breakers

Dan Wing <dwing@cisco.com> Tue, 10 September 2013 20:33 UTC

Return-Path: <dwing@cisco.com>
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 5B6A511E811B for <rtcweb@ietfa.amsl.com>; Tue, 10 Sep 2013 13:33:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.598
X-Spam-Level:
X-Spam-Status: No, score=-110.598 tagged_above=-999 required=5 tests=[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 ai+YmZ8Vb4ra for <rtcweb@ietfa.amsl.com>; Tue, 10 Sep 2013 13:33:22 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id E32CE21E8094 for <rtcweb@ietf.org>; Tue, 10 Sep 2013 13:33:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5353; q=dns/txt; s=iport; t=1378845202; x=1380054802; h=mime-version:subject:from:in-reply-to:date:cc:message-id: references:to; bh=jFnyyjnUAy8MiKOBmJv430+/4xUGhSiid4zf59qWelY=; b=eZ89DMSx8Yyx0AsdNGRr53PYl1K08lCBSJib/AgdWNApXQRwgMMGHkCo LykkBHNLS28F7vR4G8WbVl+Chlf/oEdTePZM/uJvQxydc8jsFbNHthsU3 GF6gycc7KfxUTBY0ePv9HTUndOCwj73cEGVl3yZVVvRfmavWhU4oEYcP9 o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhUFAJ2BL1KrRDoH/2dsb2JhbABbgkNEOLBgklCBJhZ0giUBAQECAQEBAQFrCxALBEInMAYTCYdnAwkFDcMpjHCCaweDHYEAA4k2jFiBaIw7hTCDQBw
X-IronPort-AV: E=Sophos; i="4.90,879,1371081600"; d="scan'208,217"; a="91547677"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-2.cisco.com with ESMTP; 10 Sep 2013 20:33:13 +0000
Received: from dhcp-10-155-84-136.cisco.com (dhcp-10-155-84-136.cisco.com [10.155.84.136]) by mtv-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r8AKWlHC020665; Tue, 10 Sep 2013 20:33:13 GMT
Content-Type: multipart/alternative; boundary="Apple-Mail=_970D3A7B-7DA7-431D-B846-4DDF881D6F30"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Dan Wing <dwing@cisco.com>
In-Reply-To: <BLU169-W33B76B08BBA4CBCBADBECA933F0@phx.gbl>
Date: Tue, 10 Sep 2013 13:33:29 -0700
Message-Id: <E7CFA718-BCD0-41E9-A040-91A7BF88C7E4@cisco.com>
References: <522D88A8.3010209@ericsson.com>, <7594FB04B1934943A5C02806D1A2204B1C49B5A1@ESESSMB209.ericsson.se> <BLU169-W33B76B08BBA4CBCBADBECA933F0@phx.gbl>
To: Bernard Aboba <bernard_aboba@hotmail.com>
X-Mailer: Apple Mail (2.1508)
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] consent freshness vs. circuit breakers
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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: Tue, 10 Sep 2013 20:33:27 -0000

On Sep 9, 2013, at 8:45 AM, Bernard Aboba <bernard_aboba@hotmail.com> wrote:

> 
> Christer said: 
> 
> "Now, as we have decided to not use SDES, I guess that can be removed."
> 
> [BA] Actually, I believe that a sentence or two describing why the needs of consent freshness are not met by mechanisms such as SRTCP is worth keeping, and possibly should even be expanded upon.  One reason is that we also have the "circuit breakers" mechanism which *does* rely (in part) on SRTCP.   
> 
> Christer said: 
> 
> "But, based on that, I'd just like to verify whether there is still a need for the draft :)"
> 
> [BA] I do think that the draft is still necessary, even without SDES/SRTP.   The usage of ICE for consent seems to me to be less susceptible to a variety of issues than a dependency on SRTCP might be. 
> 
> However, I am concerned about the interaction between circuit breakers and consent freshness.  At IETF 87, we heard that the circuit breakers mechanism could fire even when the overall loss rate was quite low, due to burst losses.  That shouldn't be true of consent, since loss of consent requires up to 30 consecutive losses over a 15 second period.  However, it would appear to me that the current circuit breakers algorithms will cause media sending to be curtailed prior to loss of consent in many cases.  

Yes, consent needs to avoid the same pitfalls that were explained for circuit breakers.  

(For others that might be interested, the AVT presentation describing the research on circuit breakers is at http://www.ietf.org/proceedings/87/slides/slides-87-avtcore-2.pdf.)

-d


> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb