IETF Logo Mail Archive

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

"DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com> Thu, 23 April 2015 13:38 UTC

Return-Path: <keith.drage@alcatel-lucent.com>
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 ADF521B3097 for <rtcweb@ietfa.amsl.com>; Thu, 23 Apr 2015 06:38:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] 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 2S9VWmph31zZ for <rtcweb@ietfa.amsl.com>; Thu, 23 Apr 2015 06:38:53 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 198B31B309F for <rtcweb@ietf.org>; Thu, 23 Apr 2015 06:38:53 -0700 (PDT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (unknown [135.239.2.42]) by Websense Email Security Gateway with ESMTPS id 2481C4DB538D6; Thu, 23 Apr 2015 13:38:49 +0000 (GMT)
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id t3NDcm6T019991 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 23 Apr 2015 15:38:49 +0200
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.203]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.03.0195.001; Thu, 23 Apr 2015 15:38:48 +0200
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Colin Perkins <csp@csperkins.org>, Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
Thread-Topic: [rtcweb] Endpoints that don't support RTCP
Thread-Index: AQHQfUw3D6jG0bV1yEuF2X1NGaVsvZ1Z8XyAgAAllICAAB9VgIAABB8AgAAUngCAAEoKIA==
Date: Thu, 23 Apr 2015 13:38:47 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B697093ED@FR712WXCHMBA11.zeu.alcatel-lucent.com>
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> <5538C10C.10905@gmail.com> <B8DBE816-9947-4983-956A-7361F472734D@csperkins.org>
In-Reply-To: <B8DBE816-9947-4983-956A-7361F472734D@csperkins.org>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.40]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/jgVFId7sblOKUy3hV11jTA3q8P8>
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: Thu, 23 Apr 2015 13:38:55 -0000

I have to agree with Colin's request for details and measurements here.

The first thing I learnt about congestion control (in telephony networks based on Erlang's work) was that sounds like a good solution to congestion does not look as good when you either do the maths or simulate it.

So measurements (or the maths if you are expert in things like Markov chains) are needed for the particular use case to prove that the general testing performed by Colin is invalid for that use case.

Keith

> -----Original Message-----
> From: rtcweb [mailto:rtcweb-bounces@ietf.org] On Behalf Of 
> Colin Perkins
> Sent: 23 April 2015 12:07
> To: Sergio Garcia Murillo
> Cc: rtcweb@ietf.org
> Subject: Re: [rtcweb] Endpoints that don't support RTCP
> 
> On 23 Apr 2015, at 10:53, Sergio Garcia Murillo 
> <sergio.garcia.murillo@gmail.com> wrote:
> > On 23/04/2015 11:38, Emil Ivov wrote:
> >> 
> >> I am claiming that we don't have sufficient evidence that 
> they work 
> >> and am concerned that they would trigger in situations 
> where common 
> >> sense dictates they shouldn't.
> > 
> > +1
> > 
> > I completely agree with Emil.
> 
> What scenarios are you concerned with? I keep hearing claims 
> that the circuit breaker is problematic, but have been given 
> no examples. 
> 
> > In fact, as a WebRTC service providers, what we are going to do in 
> > case of CB is to re-establish the connection immediately (maybe 
> > disabling video),
> 
> As described in Section 4.3 of the circuit breaker draft, you mean?
> 
> --
> Colin Perkins
> https://csperkins.org/
> 
> 
> 
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>

v2.23.0 | Report a Bug | By Email