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

Cullen Jennings <fluffy@iii.ca> Fri, 24 August 2012 18:16 UTC

Return-Path: <fluffy@iii.ca>
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 8EDCE21F85F4 for <rtcweb@ietfa.amsl.com>; Fri, 24 Aug 2012 11:16:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.469
X-Spam-Level:
X-Spam-Status: No, score=-2.469 tagged_above=-999 required=5 tests=[AWL=0.130, BAYES_00=-2.599]
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 LY-+yRk5wM-K for <rtcweb@ietfa.amsl.com>; Fri, 24 Aug 2012 11:16:40 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id D142321F85B4 for <rtcweb@ietf.org>; Fri, 24 Aug 2012 11:16:40 -0700 (PDT)
Received: from sjc-vpn6-639.cisco.com (unknown [128.107.239.233]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id ABEAD22E256; Fri, 24 Aug 2012 14:16:32 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <CABkgnnXQ25ZYNqeO+=FsYDR3aNvFS2zvrKWGs5o=h8m+Eq=Y+Q@mail.gmail.com>
Date: Fri, 24 Aug 2012 11:16:36 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <3B8DB12B-ABB3-4AC2-A0A0-93DC62C619D3@iii.ca>
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>
To: Martin Thomson <martin.thomson@gmail.com>
X-Mailer: Apple Mail (2.1278)
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: Fri, 24 Aug 2012 18:16:44 -0000

I'm confused on what you are trying to say. Are you saying 

1) we don't need trickle ICE

2) we can do trickily ICE but no standards need to be written for two different devices to do trickle ICE


On Aug 24, 2012, at 9:56 , Martin Thomson wrote:

> On 24 August 2012 09:42, Eric Rescorla <ekr@rtfm.com> wrote:
>> I'm not following what you are saying here. Ignoring the question of
>> non-trickle (i.e., strict RFC 5245) endpoints, if you are a trickle endpoint
>> that gives up under conditions when RFC 5245 says you should give
>> up, you are likely to have problems.
> 
> If you are a trickle endpoint, then you are not implementing RFC 5245.
> RFC 5245 might not explicitly exclude the possibility, but it is
> certainly implicit, as the problems you cite in your email attest.
> 
> What I think we want to with trickle is to create a new method.  That
> method is only like RFC 5245 to the extent that it shares some
> properties: the good parts.
> 
>> You don't think it's worth writing
>> that down somewhere more permanent/definitive than an email
>> to the mailing list?
> 
> Only if it addresses a specific interoperability need does it need to
> be in an RFC.
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb