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

Emil Ivov <emcho@jitsi.org> Sun, 26 April 2015 14:03 UTC

Return-Path: <emcho@sip-communicator.org>
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 26B131A9024 for <rtcweb@ietfa.amsl.com>; Sun, 26 Apr 2015 07:03:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 HQ3mT9hx9Pnz for <rtcweb@ietfa.amsl.com>; Sun, 26 Apr 2015 07:03:01 -0700 (PDT)
Received: from mail-ob0-f171.google.com (mail-ob0-f171.google.com [209.85.214.171]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 617F31A9023 for <rtcweb@ietf.org>; Sun, 26 Apr 2015 07:03:01 -0700 (PDT)
Received: by obfe9 with SMTP id e9so66986460obf.1 for <rtcweb@ietf.org>; Sun, 26 Apr 2015 07:03:00 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=6XgRNWL4LURjCLtJsm1bIVLx0bxlM8gj+psU1GYdizw=; b=jbIJ3To5haBllUJmj/woM7FJR5eXz2o8iSGSR8rj0Ilgum1JQtFXi8Ja9PrwOUgx+0 nZADLYBW1OLxZnTe9iIK157EzKx868EjZJO/X2/Slo3+UGP4Tiqdj0JDVQrn2QIgMSL4 MqL13mRo1vMHKz4I84Llu5OLR8XeM9hA4TILM8sJa6pi2YYht1CxubQB05nyHb+un7ps PiavhLbdwj8NI2/3cCnguQ0TjpeFjNm3/qQSB4E/74KkBpkgR5iQ/HTWumxY/LGthpIc Sroql4Fwse9JhjzMOA0Wtml9Foornv4g0uuBHr+8A4CV7z00tuAm+I4L+Im2CsHFSz7o BWmg==
X-Gm-Message-State: ALoCoQn21SLqCUFE6WGZjBhDnO4aidNtmg7M0bYRTxIqVsv59c6JNf0GeSBBWuXGw9tk8qyJ0feN
X-Received: by 10.60.116.170 with SMTP id jx10mr6332239oeb.7.1430056980682; Sun, 26 Apr 2015 07:03:00 -0700 (PDT)
Received: from camionet.local ([84.238.157.117]) by mx.google.com with ESMTPSA id zk5sm9745755obc.22.2015.04.26.07.02.54 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 26 Apr 2015 07:02:55 -0700 (PDT)
Message-ID: <553CF00C.8060701@jitsi.org>
Date: Sun, 26 Apr 2015 17:02:52 +0300
From: Emil Ivov <emcho@jitsi.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Colin Perkins <csp@csperkins.org>
References: <CAOJ7v-01DhCKewmC-Cvh4Z-jeOmi=CunisjFWceoPfk2ZM9Wgg@mail.gmail.com> <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> <553627F7.6010407@alvestrand.no> <CAPvvaaLZXH1bFeAVPD=gHUB8egJcemKcCLhtnZrCW3DrdMA9UA@mail.gmail.com> <B3EC2C3A-3DF1-4AA3-96FC-0C24B5FACDCE@csperkins.org> <CAPvvaaK+BoLVtK9XKKR4VWkrTw=TsZwd282ZO+RC8y-JeEOvLQ@mail.gmail.com> <8FC332B1-653F-423B-8B37-CD5574BF9A85@csperkins.org> <CAPvvaaKZ5OkB+kVqiX4iTZ+TnUotTK-MWah8W+goQW9DPVT+dg@mail.gmail.com> <B32981BB-BF46-4808-9DBD-CF9DA4284950@csperkins.org>
In-Reply-To: <B32981BB-BF46-4808-9DBD-CF9DA4284950@csperkins.org>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/ymcb56LqnZRlBAbnnmCfywmoIx8>
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] 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: Sun, 26 Apr 2015 14:03:03 -0000

Hey Colin,

On 23.04.15 14:01, Colin Perkins wrote:
> Emil,
>
> On 23 Apr 2015, at 10:38, Emil Ivov <emcho@jitsi.org> wrote:
>> On Thu, Apr 23, 2015 at 10:46 AM, Colin Perkins <csp@csperkins.org>
>> wrote:
>>> Emil,
>>>
>>> I have repeatedly presented evidence,
>>
>> You inadvertently forgot to paste the link to these presentations.
>> I am particularly interested in the "real-world networks" ones.
>
> They're in the IETF proceedings, for example AVTCORE at IETF 87 and
> 88:
> http://www.ietf.org/proceedings/87/slides/slides-87-avtcore-2.pdf
> http://www.ietf.org/proceedings/88/slides/slides-88-avtcore-4.pdf
>
> I had assumed you were at the meetings and saw the presentations, but
> perhaps not.

Indeed not. Thanks very much for forwarding!

Unfortunately, as far as Circuit Breakers are concerned I fail to find 
the "measurements on real-world networks" that you mentioned. Maybe I 
missed something?

The results that Varun and you presented are based on a simulation 
derived from a semi-synthetic data set. Zahed's is exclusively based on 
simulations.

All of this is obviously great work and very rewarding to read (some of 
it was new to me), so thanks for forwarding. Still, none of it however 
represents a practical evaluation of CB behaviour.

Ideally what we need in order to validate CBs is:

A) For a given real-world deployment, how much congestion do we see with 
and without CBs
B) For a given real-world deployment, how does user satisfaction vary 
with and without CBs

What I am worried about is that A) might not be particularly important 
because users, server-side apps and JS apps themselves would 
automatically resume calls.

As for B) I suspect that real-world scenarios might cause more cases 
where CBs trigger prematurely, which would have a negative impact on 
user satisfaction.

So with all that in mind I find that at this stage we are likely overly 
confident in CBs to MUST them in cases with no congestion control. Still 
given how people simply ignore the parts they don't like when 
implementing IETF RFCs I don't think we are in the face of a disaster or 
anything ...

Emil


-- 
https://jitsi.org