Re: [rtcweb] Summary of ICE discussion

Cullen Jennings <fluffy@cisco.com> Tue, 04 October 2011 22:37 UTC

Return-Path: <fluffy@cisco.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 656B421F8467 for <rtcweb@ietfa.amsl.com>; Tue, 4 Oct 2011 15:37:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.961
X-Spam-Level:
X-Spam-Status: No, score=-101.961 tagged_above=-999 required=5 tests=[AWL=-1.516, BAYES_00=-2.599, FRT_BELOW2=2.154, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0Kcl6mkOd2Cv for <rtcweb@ietfa.amsl.com>; Tue, 4 Oct 2011 15:37:48 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id E5DE921F84AE for <rtcweb@ietf.org>; Tue, 4 Oct 2011 15:37:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fluffy@cisco.com; l=3301; q=dns/txt; s=iport; t=1317768055; x=1318977655; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=WnqNnx4exeglKaqMFFs/ZIRk34wEe8RV29xrI4obrNI=; b=Ojn31aIMRBhCW7dIy2B7KmYdPy7hqvhhsIwdcgKwAbniGM66yaiEe6VJ ol+JGMS1i/cjEIx9gS98vGdoHS2X4maCvffRFWzxnrhDKwfLEDOdxq7c7 tkfV3T1PJoTGw7Xbr3RStLZwySLMTIbhYljxXeURhfaEMQLHUgQ5j+sL+ A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Aq4IAHaKi06rRDoI/2dsb2JhbABCmQaPBYEFgVMBAQEBAgEBAQEPASc0CwULCxEDAQIvJygIBhMbB4dbBpltAZ1pA4ZCYQSHeItuhSeEeYdB
X-IronPort-AV: E=Sophos;i="4.68,487,1312156800"; d="scan'208";a="5943980"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-1.cisco.com with ESMTP; 04 Oct 2011 22:40:54 +0000
Received: from [192.168.4.100] (sjc-fluffy-8914.cisco.com [10.20.249.165]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p94MeAev031950; Tue, 4 Oct 2011 22:40:54 GMT
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <BLU152-W2342F5823933FA1F2B9F9C93FB0@phx.gbl>
Date: Tue, 4 Oct 2011 16:40:53 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <37C37EE6-3D48-4C77-A025-3207F040572B@cisco.com>
References: <4E8B192E.80809@ericsson.com>, , <CALiegfmnxO+BrfycOmL=hptBFdcEpsLeBn=zsJTX=ivKBBumWw@mail.gmail.com>, <BLU152-W139AA2913C1CFFDB50726193FB0@phx.gbl> <BLU152-W2342F5823933FA1F2B9F9C93FB0@phx.gbl>
To: Bernard Aboba <bernard_aboba@hotmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Summary of ICE discussion
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: Tue, 04 Oct 2011 22:37:49 -0000

Could you say more... I'm not following your logic.


On Oct 4, 2011, at 10:47 AM, Bernard Aboba wrote:

> In particular, I'm concerned about vulnerabilities created by multiplexing
> audio and video on the same port.  When that is done, the ICE procedure loses
> some of its DoS prevention properties.
> 
> From: bernard_aboba@hotmail.com
> To: magnus.westerlund@ericsson.com
> Date: Tue, 4 Oct 2011 09:28:34 -0700
> CC: rtcweb@ietf.org
> Subject: Re: [rtcweb] Summary of ICE discussion
> 
> I think this is a good summary of where we are with respect to ICE, and
> since there are no good alternatives on the table, it seems reasonable to
> move on to the next step. 
> 
> IMHO, this would involve a more detailed analysis of the threats and what
> needs to be done to resolve them. 
> 
> In particular, the statement "STUN Connectivity Check MUST have succeeded" is 
> necessary but not sufficient.   We need to get into a discussion of the specific
> conditions under which media can be sent, and what attacks are still
> possible.  For example, there exist public STUN servers on the Internet, and 
> RTCWEB should not permit the browser to execute a DoS attack on these servers. 
> Also, it would be desirable to prevent a browser from sending much more
> bandwidth than the receiver has consented to;  however, because signaling
> is largely opaque to the browser, it is not obvious (at least to me) how to 
> prevent this. 
> 
> > 2011/10/4 Magnus Westerlund <magnus.westerlund@ericsson.com>;:
> > I have bellow tired to summarize the result of the ICE discussion. This
> > is intended as furthering this discussion and form a basis for going
> > forward in the consensus process. I do expect people that disagree with
> > my summary of the discussion to speak up.
> >
> > Major requirements
> >
> > - Need for data transmission consent for protocols using UDP as the
> > traffic receiver needs to consent to receiving the data
> >
> > - Perform NAT and FW traversal when ever needed
> >
> > - Support IPv4 to IPv6 transition
> >
> > Desired behavior:
> >
> > - Be interoperable with deployed legacy systems as SIP Trunk, PSTN
> > gateways, VoIP phones.
> > 
> > WG chairs conclusion of discussion so far:
> > 
> > - ICE is so far the only solution that provides the security goals and
> > have any legacy deployment.
> >
> > - ICE usage will require that STUN connectivity MUST have succeeded
> > prior to any data transmission to fulfill security goals.
> >
> >  * The Browser will enforce this requirement to prevent being an attack
> > vector in all cases.
> >
> > - If anyone can find a solution that fulfill the security goals and have
> > improved legacy interoperability people would be interested in that
> > solution. So far RTCP has been discarded as insufficient.
> >
> > - Media Gateway can support a reduced functionality set from Full ICE
> 
> 
> _______________________________________________ rtcweb mailing list rtcweb@ietf.org https://www.ietf.org/mailman/listinfo/rtcweb
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb