Re: [rtcweb] Strawman for how to prevent voice-hammer without ICE

Hadriel Kaplan <HKaplan@acmepacket.com> Thu, 28 July 2011 14:48 UTC

Return-Path: <HKaplan@acmepacket.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E89021F8CB8 for <rtcweb@ietfa.amsl.com>; Thu, 28 Jul 2011 07:48:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.479
X-Spam-Level:
X-Spam-Status: No, score=-2.479 tagged_above=-999 required=5 tests=[AWL=0.120, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JciJ-PqxgfES for <rtcweb@ietfa.amsl.com>; Thu, 28 Jul 2011 07:48:11 -0700 (PDT)
Received: from ETMail2.acmepacket.com (etmail2.acmepacket.com [216.41.24.9]) by ietfa.amsl.com (Postfix) with ESMTP id 4C62F21F8CB4 for <rtcweb@ietf.org>; Thu, 28 Jul 2011 07:48:11 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by ETMail2.acmepacket.com (216.41.24.9) with Microsoft SMTP Server (TLS) id 8.1.240.5; Thu, 28 Jul 2011 10:47:09 -0400
Received: from mailbox1.acmepacket.com ([216.41.24.12]) by mail ([127.0.0.1]) with mapi; Thu, 28 Jul 2011 10:48:09 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>
Date: Thu, 28 Jul 2011 10:48:07 -0400
Thread-Topic: Strawman for how to prevent voice-hammer without ICE
Thread-Index: AcxNNV1zFnPAe+pkSveuLg9KTGFoZQ==
Message-ID: <464DADBD-EEBE-43C8-8552-EAA40FBB610D@acmepacket.com>
References: <B6527F21-4DE2-46B1-AE2E-891D56461313@acmepacket.com> <A444A0F8084434499206E78C106220CA08F1D75CF6@MCHP058A.global-ad.net>
In-Reply-To: <A444A0F8084434499206E78C106220CA08F1D75CF6@MCHP058A.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAQAAAUA=
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Strawman for how to prevent voice-hammer without ICE
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Jul 2011 14:48:12 -0000

On Jul 28, 2011, at 8:10 AM, Elwell, John wrote:

> [JRE] The problem with requiring continued RTP receipt (or even ANY RTP receipt) is sessions where RTP is one-way, e.g., when mic muted, camera off. With many asymmetric possibilities coming out of the CLUE work, this could be a problem, although it perhaps goes away if everything is multiplexed onto the same port. It depends whether we can expect all legacy devices to behave in a way that would make this work.

Yes, but they don't turn off RTCP (assuming they do RTCP).  I'm not suggesting that it's a 1:1 mechanism of receipt/send, nor that it even be very dynamic/real-time.  But sure there will be some cases that it won't work.  But that's no worse than the current state of things, since it won't work to begin with for such devices if ICE is mandated.  We can't achieve 100% interop regardless - I'm just trying for as much as possible.

With regards to CLUE, I don't consider their devices "legacy".  They'll be upgrading to handle CLUE's final spec, so they can be "redeemed".

-hadriel