IETF Logo Mail Archive

Re: [rtcweb] Filling in details on "trickle ICE"

Martin Thomson <martin.thomson@gmail.com> Sat, 25 August 2012 00:08 UTC

Return-Path: <martin.thomson@gmail.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 C9BC621F8598 for <rtcweb@ietfa.amsl.com>; Fri, 24 Aug 2012 17:08:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.907
X-Spam-Level:
X-Spam-Status: No, score=-3.907 tagged_above=-999 required=5 tests=[AWL=-0.308, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 aBveB1FQUIBe for <rtcweb@ietfa.amsl.com>; Fri, 24 Aug 2012 17:08:43 -0700 (PDT)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 0FBC121F8595 for <rtcweb@ietf.org>; Fri, 24 Aug 2012 17:08:42 -0700 (PDT)
Received: by lahm15 with SMTP id m15so1524558lah.31 for <rtcweb@ietf.org>; Fri, 24 Aug 2012 17:08:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=/eaUG+cWTaUVO0sPIBPIrBIfV1Da+5dmfTuw9oYPDmc=; b=NG8eUE8/qF2VDvP4ytGAFaJDmkSMmWbrnQHhhL4ObC6z+6Rt1mElxgvPj7D02CBMS5 EdZYY5f96OqnUeJgmd2DmbkQB8+afHdCoDFlDJMHs+1SdRaLgXU+RTVwnZS/VdK6DDq6 1Npv2uuBEmc1EAOnA8Qa/TIrh6zxrMz2tNcUaU63XDXI8GGPVHDqyNYUp0pH2HGpQQKL bkjkI5W3Za0NjLGSDfUbGTYZlHHSofHYIJqJjsrOMqUMKY+M86WKfx9PB9V0ZiaeVQ87 v80D4kWX3O3ncgn8/Gcpa8xMxbAbp7I4TJF4+cmnY1jR9feHoAVLvmmHHfARJz2ZYq99 qdBQ==
MIME-Version: 1.0
Received: by 10.112.25.100 with SMTP id b4mr3392672lbg.55.1345853319719; Fri, 24 Aug 2012 17:08:39 -0700 (PDT)
Received: by 10.112.41.193 with HTTP; Fri, 24 Aug 2012 17:08:39 -0700 (PDT)
In-Reply-To: <E17CAD772E76C742B645BD4DC602CD81069D82BF@NAHALD.us.int.genesyslab.com>
References: <CABcZeBMzgAs=hK38hCjS7t6yLjkTydS2TQUb8R3rBbRKGakVdQ@mail.gmail.com> <CABkgnnVBBAH=HCkn_cksBs_9A_hm=VfFwcTtvOM3C7XB2h2KTA@mail.gmail.com> <CABcZeBMFUFjU=FQo5LeJrcMfajeae0j+PWw5U2g5dUQNcJLWaA@mail.gmail.com> <CABkgnnXiL3_U+Hci9ooDqBCsoV3KF8pwgcf9zbuN6EKZkK+aiQ@mail.gmail.com> <CABcZeBNkkH93ybuMWoFg-ddKWnRgdn2Vgyb50W21A2GoMWxw6Q@mail.gmail.com> <CABkgnnXQ25ZYNqeO+=FsYDR3aNvFS2zvrKWGs5o=h8m+Eq=Y+Q@mail.gmail.com> <3B8DB12B-ABB3-4AC2-A0A0-93DC62C619D3@iii.ca> <CABkgnnU3ecmhUwCYHmppwLJz-nbSA6=VRF7nF7wcpb+5QAWmdQ@mail.gmail.com> <E17CAD772E76C742B645BD4DC602CD81069D82BF@NAHALD.us.int.genesyslab.com>
Date: Fri, 24 Aug 2012 17:08:39 -0700
Message-ID: <CABkgnnWR1n+bKFjFt+FyQVBpnn_myPiWLPyk_DT=vZS39ef_RA@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Jim Barnett <Jim.Barnett@genesyslab.com>
Content-Type: text/plain; charset="UTF-8"
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Filling in details on "trickle 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: Sat, 25 Aug 2012 00:08:43 -0000

On 24 August 2012 15:33, Jim Barnett <Jim.Barnett@genesyslab.com> wrote:
> Martin,
>   Just to make sure that I understand your position, I take you to be
> saying:
> 1) in the case where both endpoints have downloaded their apps from the
> same server, they can do trickle ICE any way that they want.
> 2) in the case where an application is  talking to an unknown or legacy
> peer, trickle  ICE is a bad idea because there is no standard way to do
> it. (i.e. try it at your own risk)
>
> Is this correct?

A fair summation.  In 1) they can do whatever they want within the
necessary security constraints.

v2.23.0 | Report a Bug | By Email