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

Harald Alvestrand <harald@alvestrand.no> Fri, 24 April 2015 08:06 UTC

Return-Path: <harald@alvestrand.no>
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 155611B3594 for <rtcweb@ietfa.amsl.com>; Fri, 24 Apr 2015 01:06:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 rT69jtZzKZCg for <rtcweb@ietfa.amsl.com>; Fri, 24 Apr 2015 01:06:16 -0700 (PDT)
Received: from mork.alvestrand.no (mork.alvestrand.no [IPv6:2001:700:1:2::117]) by ietfa.amsl.com (Postfix) with ESMTP id CF8C91B3583 for <rtcweb@ietf.org>; Fri, 24 Apr 2015 01:05:45 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id B16747C3E1C for <rtcweb@ietf.org>; Fri, 24 Apr 2015 10:05:44 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at alvestrand.no
Received: from mork.alvestrand.no ([127.0.0.1]) by localhost (mork.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xxH8RDIzVwdB for <rtcweb@ietf.org>; Fri, 24 Apr 2015 10:05:42 +0200 (CEST)
Received: from [192.168.1.192] (unknown [188.113.88.47]) by mork.alvestrand.no (Postfix) with ESMTPSA id B07D87C3E1B for <rtcweb@ietf.org>; Fri, 24 Apr 2015 10:05:42 +0200 (CEST)
Message-ID: <5539F956.8070705@alvestrand.no>
Date: Fri, 24 Apr 2015 10:05:42 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; 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> <CABkgnnW6KFuJhswLK97LE6J=9vqkf-cmeRMZOuz516ZryeSRQw@mail.gmail.com> <CAPvvaa+wid8y2h0g2040V8bSr50+rQRzpg-tCTK9EUFmtJrZYw@mail.gmail.com> <CABkgnnUt2fwdOWqTjHUjkUZN_aqAfrBW90Q4Q-EPrid4sCSWQg@mail.gmail.com> <BB960D2D-3176-4D54-8133-7F12B79DCAFA@cisco.com> <CABkgnnWuRYW8w6xCLt2dJVZ1ePxAxZWbyYqrV68cZaA2uHgmGg@mail.gmail.com> <CAOJ7v-3W7+Lfd8DCs_91K_DGaqjdyZ_qtkoQBiSO2pi-j1fuOA@mail.gmail.com> <CABkgnnXOXc+Jq4mSq02_As9ii5g_EpeRnO_sVF+OnZrLoGC9Xg@mail.gmail.com> <CAOJ7v-0niXySrvkPnSGXA5YVe_O5YVvae_8zGsEYtPqpw43UZw@mail.gmail.com> <CABkgnnWzdn9FVO27G7ioz5soLhckseAEEHV+QZJsyiTOD_sYnA@mail.gmail.com> <551A902A.9080402@alvestrand.no> <CABkgnnU+r-8UXXMVKt_eiK_hd3eutWpUXiGQ=KsGrwCxB11cMg@mail.gmail.com> <55361DCA.7000101@ericsson.com> <553621A8.5000400@alvestrand.no> <7B 9A5F8B-5269-4CB3-8741-976AB7BAA9C6@csperkins.org> <A368210C-B789-4B8C-A055-BECDF9580856@iii.ca>
In-Reply-To: <A368210C-B789-4B8C-A055-BECDF9580856@iii.ca>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/lH105Wq_XFamTxvgsCPwFvWA1dA>
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: Fri, 24 Apr 2015 08:06:18 -0000

Den 23. april 2015 21:44, skrev Cullen Jennings:
> 
>> On Apr 22, 2015, at 4:44 PM, Colin Perkins <csp@csperkins.org> wrote:
>>
>>> Perpetuating tolerance for the broken behavior of ignoring "MUST send
>>> RTCP" seems like a path that doesn't lead to getting rid of the behavior
>>> in the end.
>>
>> I tend to agree: this seems like something where the gateway ought to handle the interoperability, and synthesise appropriate RTCP. 
>>
>> Or, if that's really too onerous, tie into some other consent check that can indicate that the flow is still wanted and not causing problems.
> 
> People keep talking about gateway's but I'm talking about endpoints that do ICE and DTLS-SRTP but don't do RTCP. They also don't do video. 
> 
> The reason they don't do RTCP is because they don't perceive a value in it. I'm not arguing this is right or wrong, I'm just saying they don't see the value. The point the folks that think this is a good idea make is that if RTCP says there is X jitter, or Y % packet loss, there is nothing they can do with this. They will not stop the call until the audio is so bad that user hangs up. Only the user hanging up stops the call. Thus the only thing RTCP does is cause more congestion. Again, not saying this is right but given that most the audio only RTP I see on the network does not have RTCP, I don't think this is likely to change any time soon.  And I want to say again, for video it is the opposite story, the bulk of the interactive video RTP I see has RTCP. 
> 

And I'm arguing (thinking out loud) that if we condone this behavior by
successfully interoperating with these devices from WebRTC
installations, we're prolonging the problem.

If our consensus (or consensus-minus-Emil) is that we need devices to
back off on sending RTP in the face of severe congestion for the sake of
the network, and our consensus is that we need RTCP in order to detect
that condition, the only reasonable conclusion is that we should refuse
to interoperate with those devices that do not send RTCP.

These devices already upgraded to ICE and DTLS-SRTP, presumably because
they wanted to interoperate with WebRTC installations. Sending an RTCP
packet once every few seconds is not going to be what kills them.