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

Hadriel Kaplan <HKaplan@acmepacket.com> Thu, 28 July 2011 17:07 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 8F3CD11E8095 for <rtcweb@ietfa.amsl.com>; Thu, 28 Jul 2011 10:07:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.873
X-Spam-Level:
X-Spam-Status: No, score=-1.873 tagged_above=-999 required=5 tests=[AWL=-0.514, BAYES_00=-2.599, SARE_LWSHORTT=1.24]
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 V7eCnxUqfzwa for <rtcweb@ietfa.amsl.com>; Thu, 28 Jul 2011 10:07:40 -0700 (PDT)
Received: from ETMail2.acmepacket.com (etmail2.acmepacket.com [216.41.24.9]) by ietfa.amsl.com (Postfix) with ESMTP id 1731821F880C for <rtcweb@ietf.org>; Thu, 28 Jul 2011 10:07:39 -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 13:07:49 -0400
Received: from mailbox1.acmepacket.com ([216.41.24.12]) by mail ([127.0.0.1]) with mapi; Thu, 28 Jul 2011 13:07:38 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Jonathan Rosenberg <jdrosen@jdrosen.net>
Date: Thu, 28 Jul 2011 13:07:36 -0400
Thread-Topic: [rtcweb] Strawman for how to prevent voice-hammer without ICE
Thread-Index: AcxNSNnONZ06rkPvRrW1HW4ZbnH0Zw==
Message-ID: <445CB6A5-F1B6-4553-9E95-16F7D4CF8C4D@acmepacket.com>
References: <B6527F21-4DE2-46B1-AE2E-891D56461313@acmepacket.com> <4E31951E.1080108@jdrosen.net>
In-Reply-To: <4E31951E.1080108@jdrosen.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 17:07:40 -0000

On Jul 28, 2011, at 12:58 PM, Jonathan Rosenberg wrote:

> Let me suggest a variation on this..
> 
> The rtcweb client can send RTP packet, voice-only, for a brief period of 
> time (say, 2x the RTCP interval). It waits to receive an RTCP packet. 
> The RTCP packet should have an RR which reflects back the SSRC sent by 
> the client, if it does, the rtcweb client continues. If not, it stops 
> sending.
> 
> The purpose of the RTCP SSRC check is to emulate what the STUN 
> transaction ID provides; that there is something on the media path which 
> is expecting this RTP packet. Not as good as STUN which also has the 
> short term credential, but its something.
> 

I had considered using the SSRC before, but I think you're gonna have to let the javascript know the SSRC to handle some SIP/SDP usages (since there's an SSRC attribute for SDP, I assume someone needs it).  No?

-hadriel