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

Christer Holmberg <> Thu, 18 October 2012 06:30 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 73AC621F8584 for <>; Wed, 17 Oct 2012 23:30:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.119
X-Spam-Status: No, score=-6.119 tagged_above=-999 required=5 tests=[AWL=0.130, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 95Cxkt8ySIAr for <>; Wed, 17 Oct 2012 23:30:39 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 6141821F8582 for <>; Wed, 17 Oct 2012 23:30:39 -0700 (PDT)
X-AuditID: c1b4fb30-b7f7d6d0000042ea-9a-507fa20d4835
Received: from (Unknown_Domain []) by (Symantec Mail Security) with SMTP id AC.78.17130.D02AF705; Thu, 18 Oct 2012 08:30:37 +0200 (CEST)
Received: from ( by ( with Microsoft SMTP Server (TLS) id; Thu, 18 Oct 2012 08:30:37 +0200
Received: from ([]) by ([]) with mapi id 14.02.0318.001; Thu, 18 Oct 2012 08:30:37 +0200
From: Christer Holmberg <>
To: Matthew Kaufman <>, Justin Uberti <>, Emil Ivov <>
Thread-Topic: [rtcweb] Filling in details on "trickle ICE"
Thread-Index: Ac2XjRRR2xT3N2ETRimioq1qbE99zgVCc2oAABiJLGA=
Date: Thu, 18 Oct 2012 06:30:36 +0000
Message-ID: <>
References: <> <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpkkeLIzCtJLcpLzFFi42KZGfG3Vpd3UX2AwaReHYs1OyewWGydKmQx 49ZZFou1/9rZHVg8Fmwq9Viy5CeTx/83gR63HkxiC2CJ4rJJSc3JLEst0rdL4Mp482YCY0EH b0XvzN0sDYx3eLoYOTkkBEwk+s4fZIawxSQu3FvP1sXIxSEkcIpR4sCD/1DOTkaJG0sWMUI4 Sxglti59AuRwcLAJWEh0/9MG6RYRKJI49vAf2CRmAXWJO4vPsYPYwgKWEus+XmGHqLGS+Lno OZx99uN7NhCbRUBV4seJx2C9vALeEl/610HtWssk8efXHEaQBKdAosTCHUtZQWxGoFO/n1rD BLFMXOLWk/lMEC8ISCzZcx7qHVGJl4//sULYihI7z7Yzg9zMLKApsX6XPkSrosSU7ofsEHsF JU7OfMICYgsJaEu0LJ7APoFRYhaSDbMQumch6Z6FpHsBI8sqRuHcxMyc9HJzvdSizOTi4vw8 veLUTYzAaDy45bfBDsZN98UOMUpzsCiJ8+qp7vcXEkhPLEnNTk0tSC2KLyrNSS0+xMjEwSnV wLiJ/4v/3XZ75tXdnz3OxnBphk5adrphYu0qHiEG9XKrqMWTTeRfcJpO2maUtVgk54Jh96WY wHhTyf9/vO5OTlVT9LLu7WfaubTuevskxZrEUy77jl5IvbviLNvf0lOXBWXXHSg4nXv07rki B+vgXUk36ip1dtvG3J0sOKM/SnKB4KKo9M5tMkosxRmJhlrMRcWJAHKhjLuUAgAA
Cc: "" <>
Subject: Re: [rtcweb] Filling in details on "trickle ICE"
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 18 Oct 2012 06:30:40 -0000

Hi Matthew,

>A few questions raised by this thread:
>1) Did the discussion about “trickle ICE” actually turn into an I-D for (I suppose) MMUSIC to look at?

There has been some discussion on the list already.

>2) Are we seriously considering defining the allowed SDP for RTCWEB/WEBRTC by referencing an I-D and not an RFC, or are we going to delay defining the allowed SDP until trickle ICE is in an RFC, or are we going to drop trickle ICE from RTCWEB 1.0?

I guess the same question applies also to BUNDLE, and potentially to a number of other I-Ds.

>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.

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"...