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

Emil Ivov <emcho@jitsi.org> Thu, 18 October 2012 09:54 UTC

Return-Path: <emil@sip-communicator.org>
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 2E56221F85C4 for <rtcweb@ietfa.amsl.com>; Thu, 18 Oct 2012 02:54:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000, 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 Jh5+jIsERwU6 for <rtcweb@ietfa.amsl.com>; Thu, 18 Oct 2012 02:54:19 -0700 (PDT)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5178121F85C2 for <rtcweb@ietf.org>; Thu, 18 Oct 2012 02:54:19 -0700 (PDT)
Received: by mail-we0-f172.google.com with SMTP id u46so5481715wey.31 for <rtcweb@ietf.org>; Thu, 18 Oct 2012 02:54:18 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding:x-gm-message-state; bh=FfnlzSr7Yb+6PhGv0MhWegNdSFJkEAg0c2g0Rs1OxQ0=; b=HW+44TiRhTSW5AaC9uwIo0Iq1M+lNxjyk8XsAjlavTUsW3f7fhZDWKmI9fbWXCksW3 k2ZoYYv3smfQsdB1WaRMGmSG3sALbSURjBwpRBuc1vxbRzSG210YLlmE2t+OHKSuK2kS dVxQiZ0uk2T3JZh/NGQuo53rT57AZ51b+CPcBeZM+wmvRZ4Vy85bXRd97HBdeF7uV5TC y9kNUBTZxtmZiUsfwcjRJ1uHw+Rh9NKcTOelvKOLLFYBqqo8iq8HE6m/HaCxODXG0d4R FH/ogIwypuKuHMbuyGB1EbxLO/uGxbuz/d1xK7X9tQejpbP8O7sNX07ezZNcVH9Jfg0d Sp1g==
Received: by 10.180.100.136 with SMTP id ey8mr10150070wib.1.1350554058369; Thu, 18 Oct 2012 02:54:18 -0700 (PDT)
Received: from camionet.local ([2a01:e35:8a55:abc0:3d45:139d:6e4e:60df]) by mx.google.com with ESMTPS id dt9sm28737714wib.1.2012.10.18.02.54.17 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 18 Oct 2012 02:54:17 -0700 (PDT)
Message-ID: <507FD1C8.8000100@jitsi.org>
Date: Thu, 18 Oct 2012 11:54:16 +0200
From: Emil Ivov <emcho@jitsi.org>
Organization: Jitsi
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <CABcZeBMzgAs=hK38hCjS7t6yLjkTydS2TQUb8R3rBbRKGakVdQ@mail.gmail.com> <50508ED7.9080805@ericsson.com> <505B6A7E.6010309@jitsi.org> <CAOJ7v-00BAp8M0_+FJGuXqAdXQ=e=MRN_L_6_CmkQWX-Gy5JAg@mail.gmail.com> <AE1A6B5FD507DC4FB3C5166F3A05A484160ED5CD@tk5ex14mbxc272.redmond.corp.microsoft.com> <7594FB04B1934943A5C02806D1A2204B018842@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B018842@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQnh3rHOE4On0yyVvPZ1NGXdDE1WZ5Qll4dYGbeHvTaXb4Nsl67Y2Y5FKF/kcmSJgtDWBJUo
Cc: "rtcweb@ietf.org" <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: Thu, 18 Oct 2012 09:54:20 -0000

Hey folks,

On 18.10.12, 08:30, Christer Holmberg wrote:
> On 17.10.12, 22:40, Matthew Kaufman wrote:
>> 
>> 4) How does trickle ICE work without “relaxing” RFC3264 O/A? It
>> seems like you really want to be able to trickle via updated offers
>> that may be generated prior to the corresponding answer or reject?
> 
> One of my comments on the trickle draft was about that. The draft
> says that a new offer can be sent "at any time", but my comment was
> that it should be according to 3264.

That's not exactly what the draft says. What it does say is:

  At any point of ICE processing, a trickle ICE agent may receive new
  candidates from the remote agent.

> IF we are going to relax 3264 (I really hope we are NOT), it needs to
> be clearly described somewhere. We cannot have a number of I-Ds doing
> it "on the run"...

I don't see how trickle ICE would require any changes to the O/A model.
Candidate trickling semantics are completely separate from those in 3264.

Yes, the 3264 offer may, in some cases, contain a first batch of
candidates and the the 3264 may have to be delayed until ICE processing
yields valid pairs for every component but that's about it.

Am I missing something?

Emil


-- 
https://jitsi.org