IETF Logo Mail Archive

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

Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com> Thu, 23 April 2015 09:53 UTC

Return-Path: <sergio.garcia.murillo@gmail.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 645531A907A for <rtcweb@ietfa.amsl.com>; Thu, 23 Apr 2015 02:53:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 1Kuok8_k9Y2M for <rtcweb@ietfa.amsl.com>; Thu, 23 Apr 2015 02:53:17 -0700 (PDT)
Received: from mail-wg0-x22c.google.com (mail-wg0-x22c.google.com [IPv6:2a00:1450:400c:c00::22c]) (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 80E241A905D for <rtcweb@ietf.org>; Thu, 23 Apr 2015 02:53:17 -0700 (PDT)
Received: by wgyo15 with SMTP id o15so12539880wgy.2 for <rtcweb@ietf.org>; Thu, 23 Apr 2015 02:53:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=L07KYpo4qAbtKAdtu87FJQnOcV7TD3FLJVH23jSHxSM=; b=EmhPIWyIpZw+e2Jyl+bxubUIS53O/jmmplOhox8ZmEr3WUN24Sv1qX9ODbCtGBtdHG 5Kyw8hSzXHD1A1JRlunwkUrFfx2jBf3pjdMyyOG1shCwvyUwTMo+KEQDEA/qsPNVuB4x KWe0RRbT8KUCsTCpvCWn1E4NfYXMSq4I1ZGh57kJQiRJhGs9mBcE/LYX3IGMvIm0LS4V U1xzemZNomThGnuJxVoRKko+oIbJXQ57+QzE71R5XnNIxlix6IEaJZX7lJwRzU4NIjbB 2Oz58XOS0fZPPas4RtehD/pu+0W/b2DGJPE2qRAGBEruZqSJiFohHUc7li0rjs/Wx6RQ fBCA==
X-Received: by 10.180.73.180 with SMTP id m20mr4378369wiv.2.1429782796270; Thu, 23 Apr 2015 02:53:16 -0700 (PDT)
Received: from [192.168.1.39] (136.Red-81-36-170.dynamicIP.rima-tde.net. [81.36.170.136]) by mx.google.com with ESMTPSA id i13sm28375155wic.13.2015.04.23.02.53.14 for <rtcweb@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 23 Apr 2015 02:53:15 -0700 (PDT)
Message-ID: <5538C10C.10905@gmail.com>
Date: Thu, 23 Apr 2015 11:53:16 +0200
From: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: rtcweb@ietf.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>
In-Reply-To: <CAPvvaaKZ5OkB+kVqiX4iTZ+TnUotTK-MWah8W+goQW9DPVT+dg@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/g8XSorAd3hvFHXxgJ-7XXf8Yg2s>
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 09:53:19 -0000

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. 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), so in fact the effectivity of the 
CB are going to be null and only add burdens to developers .

Best regards
Sergio

v2.23.0 | Report a Bug | By Email