Re: [rtcweb] Summary of ICE discussion

Bernard Aboba <bernard_aboba@hotmail.com> Tue, 04 October 2011 16:25 UTC

Return-Path: <bernard_aboba@hotmail.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 2149E21F8DE6 for <rtcweb@ietfa.amsl.com>; Tue, 4 Oct 2011 09:25:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.338
X-Spam-Level:
X-Spam-Status: No, score=-101.338 tagged_above=-999 required=5 tests=[AWL=-0.894, BAYES_00=-2.599, FRT_BELOW2=2.154, HTML_MESSAGE=0.001, 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 i+RzS0S0qPs1 for <rtcweb@ietfa.amsl.com>; Tue, 4 Oct 2011 09:25:30 -0700 (PDT)
Received: from blu0-omc3-s15.blu0.hotmail.com (blu0-omc3-s15.blu0.hotmail.com [65.55.116.90]) by ietfa.amsl.com (Postfix) with ESMTP id 7AAF321F8DE5 for <rtcweb@ietf.org>; Tue, 4 Oct 2011 09:25:29 -0700 (PDT)
Received: from BLU152-W13 ([65.55.116.72]) by blu0-omc3-s15.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 4 Oct 2011 09:28:34 -0700
Message-ID: <BLU152-W139AA2913C1CFFDB50726193FB0@phx.gbl>
Content-Type: multipart/alternative; boundary="_e9b4e328-0b7e-448d-a368-01bc48755880_"
X-Originating-IP: [98.237.179.165]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Date: Tue, 4 Oct 2011 09:28:34 -0700
Importance: Normal
In-Reply-To: <CALiegfmnxO+BrfycOmL=hptBFdcEpsLeBn=zsJTX=ivKBBumWw@mail.gmail.com>
References: <4E8B192E.80809@ericsson.com>, <CALiegfmnxO+BrfycOmL=hptBFdcEpsLeBn=zsJTX=ivKBBumWw@mail.gmail.com>
MIME-Version: 1.0
X-OriginalArrivalTime: 04 Oct 2011 16:28:34.0995 (UTC) FILETIME=[A9B5B830:01CC82B2]
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 16:25:32 -0000

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