Re: [rtcweb] [Suspected Junk Mail] Endpoints that don't support RTCP

Paul Kyzivat <pkyzivat@alum.mit.edu> Thu, 23 April 2015 22:33 UTC

Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E400A1A889F for <rtcweb@ietfa.amsl.com>; Thu, 23 Apr 2015 15:33:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=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 7QxZgPlfRe_W for <rtcweb@ietfa.amsl.com>; Thu, 23 Apr 2015 15:33:09 -0700 (PDT)
Received: from resqmta-ch2-10v.sys.comcast.net (resqmta-ch2-10v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:42]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 350F11A8888 for <rtcweb@ietf.org>; Thu, 23 Apr 2015 15:33:01 -0700 (PDT)
Received: from resomta-ch2-15v.sys.comcast.net ([69.252.207.111]) by resqmta-ch2-10v.sys.comcast.net with comcast id KaXs1q0032Qkjl901aZ0w2; Thu, 23 Apr 2015 22:33:00 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by resomta-ch2-15v.sys.comcast.net with comcast id KaYz1q00K3Ge9ey01aZ0XV; Thu, 23 Apr 2015 22:33:00 +0000
Message-ID: <5539731B.4010904@alum.mit.edu>
Date: Thu, 23 Apr 2015 18:32:59 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <7978938E-B510-43E2-9F19-C4752F6D23FD@cisco.com> <CABkgnnWvU+aYT9zgwEXCUhaO98y9kPyKwHnT=KXSr8O=knfW8w@mail.gmail.com> <CAPvvaa+SNPY+Ait2c8w9GPT-QfP7LEiuU6ejrokba93k60DdVg@mail.gmail.com> <CABkgnnW6KFuJhswLK97LE6J=9vqkf-cmeRMZOuz516ZryeSRQw@mail.gmail.com> <CAPvvaa+wid8y2h0g2040V8bSr50+rQRzpg-tCTK9EUFmtJrZYw@mail.gmail.com> <55361B07.3010707@ericsson.com> <CAPvvaaK-OxXk4=igyqix-XdubRhq+OafYvaTsJhNsbi4KHXJpw@mail.gmail.com> <5537948F.6040007@ericsson.com> <20150422152908.GF63465@verdi> <5538EFE9.7040200@ericsson.com> <20150423134742.GI63465@verdi>
In-Reply-To: <20150423134742.GI63465@verdi>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1429828380; bh=amOfj6wCyWL/qxSMAGdRXWgcaLAgYPT6FmQy9wAEWRc=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=WaTOOtywF+FGZc5IWM+D/0qUVbqSllK8fmo0b7gorMbH0E0ZJGtGdJty9GwJsL4Vi mBKVRNYkQTGHwAJdjRftfQ2HSL0W6EBCbDCXT+wnKY414LB2h+2Lvqi9vwGO8K5RJw CJR6oPNTQHIuqufiueqFh5YMmvkNw0Ap458E5wjw00MOINO5dL4800AYFVb9JW+1ui qmPK2fJXwM+nxcwLaY5XIS9SEDC95CI6p33syQ51slChLQLHFLPNm29MbkKP0lTbwR vsupEB4OV3k4NMeZ6hnPI1SVSsdj3ikt+cBh/u34vGrS+6ma+LRFx/cIDPx5yjltMv WjnvA+tb1FWkA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/yVLMkd1aeGfKoA91H0pdnrvfJGU>
Subject: Re: [rtcweb] [Suspected Junk Mail] Endpoints that don't support RTCP
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 23 Apr 2015 22:33:11 -0000

On 4/23/15 9:47 AM, John Leslie wrote:

>     Very roughly speaking, a WebRTC application could add 20% FEC bits
> to compensate for 20% packet loss. This _is_ a step down the road to
> congestion collapse; but it's not -- of itself -- a _big_ step. Its
> effect upon competing TCP traffic _is_ substantial (and there may be
> political considerations saying we have to reduce that effect).
>
>     "Circuit-breaker" is not a terribly effective way to do that --
> especially when the WebRTC application can simply start another call.

I'm just a kibitzer here, but IIUC CB indeed doesn't *intend* to do 
that. Rather, its goal is to motivate the application to do something 
better, so that the CB isn't triggered.

	Thanks,
	Paul