Re: [rtcweb] Question about ICE-Lite server

Harald Alvestrand <harald@alvestrand.no> Sun, 06 July 2014 09:13 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 63E2C1A037F for <rtcweb@ietfa.amsl.com>; Sun, 6 Jul 2014 02:13:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level:
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] 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 RLBSkGeFE1V5 for <rtcweb@ietfa.amsl.com>; Sun, 6 Jul 2014 02:13:15 -0700 (PDT)
Received: from mork.alvestrand.no (mork.alvestrand.no [158.38.152.117]) by ietfa.amsl.com (Postfix) with ESMTP id B73F61A031D for <rtcweb@ietf.org>; Sun, 6 Jul 2014 02:13:15 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id B2B2A7C0193 for <rtcweb@ietf.org>; Sun, 6 Jul 2014 11:13:14 +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 K180LDgEVZ20 for <rtcweb@ietf.org>; Sun, 6 Jul 2014 11:13:13 +0200 (CEST)
Received: from [IPv6:2001:470:de0a:27:65d2:58fb:7fb7:e81a] (unknown [IPv6:2001:470:de0a:27:65d2:58fb:7fb7:e81a]) by mork.alvestrand.no (Postfix) with ESMTPSA id BC8577C37D0 for <rtcweb@ietf.org>; Sun, 6 Jul 2014 11:13:13 +0200 (CEST)
Message-ID: <53B91327.50401@alvestrand.no>
Date: Sun, 06 Jul 2014 11:13:11 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <CALiegf=kLtiUKoue=ahXP4fUhLJNNd8vCaQTECQxjK5R7cjLTQ@mail.gmail.com>
In-Reply-To: <CALiegf=kLtiUKoue=ahXP4fUhLJNNd8vCaQTECQxjK5R7cjLTQ@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/CPrSFDx9dWg9M2oJ9mHeNad-qRg
Subject: Re: [rtcweb] Question about ICE-Lite server
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: Sun, 06 Jul 2014 09:13:18 -0000

On 07/04/2014 03:15 PM, Iñaki Baz Castillo wrote:
> Hi,
>
> In case of aggressive ICE the controlling agent (let's say: the
> client), and assuming the client has IPv4 and IPv6 and the ICE-Lite
> server as well, the server will receive multiple STUN Requests with
> USE-CANDIDATE and will decide which one to select based on computed
> candidate-pair priorities (so both the client and server select the
> same as they follow the same algorithm).
>
> Now my question is: let's assume that the server is just provided with
> local ICE username and password, but knows nothing about the fields in
> ICE candidates (let's assume that the SDP is negotiated by other
> entity which does not notify the media server about ICE candidate
> parameters others than local username and password).

To me this sounds like "can an endpoint participate in ICE without 
participating in the exchange of candidates" - and my immediate reaction 
is "if it could, it would be a security risk".

I don't think it's possible. And I think that's a Good Thing.

>
> So the media server just knows its local ICE username and password,
> but it receives a ICE Request with USE-CANDIDATE on the IPv4 interface
> and another on the IPv6 interface.
>
> Can the ICE server determine which pair to select (the IPv4 or the
> IPv6) by just inspecting the PRIORITY attribute in both STUN Requests
> and select the one with highest value?
>
> Or does the server need to assign priority, component and all the ICE
> stuff to its interfaces and also be provided with the client's and its
> own ICE candidates?
>
> Thanks a lot.
>