Re: [MMUSIC] Comment on SIP Trickle ICE based on INFO draft - FORKING

Christer Holmberg <> Sun, 30 March 2014 09:48 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id BCC5D1A07AE for <>; Sun, 30 Mar 2014 02:48:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.24
X-Spam-Status: No, score=-1.24 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, HOST_MISMATCH_NET=0.311, SPF_PASS=-0.001] autolearn=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id hSCrJBFrZPS4 for <>; Sun, 30 Mar 2014 02:48:44 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 1DE7F1A0473 for <>; Sun, 30 Mar 2014 02:48:43 -0700 (PDT)
X-AuditID: c1b4fb31-b7f688e000003e64-e8-5337e878178e
Received: from (Unknown_Domain []) by (Symantec Mail Security) with SMTP id 4A.F8.15972.878E7335; Sun, 30 Mar 2014 11:48:40 +0200 (CEST)
Received: from ([]) by ([]) with mapi id 14.03.0174.001; Sun, 30 Mar 2014 11:48:39 +0200
From: Christer Holmberg <>
To: Parthasarathi R <>, 'Emil Ivov' <>, "'Enrico Marocco (TiLab)'" <>
Thread-Topic: [MMUSIC] Comment on SIP Trickle ICE based on INFO draft - FORKING
Thread-Index: AQHPS/02PLTBD8bHIkyTiQF+pdjMCw==
Date: Sun, 30 Mar 2014 09:48:38 +0000
Message-ID: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrKLMWRmVeSWpSXmKPExsUyM+JvjW7FC/Ngg60bpCzW7JzAYtFyx8ti 6vLHLBaTP/WxOrB4LFnyk8nj/5tAjw/zv7B7tJzrZQ9gieKySUnNySxLLdK3S+DKWHtiJ0vB W46KX63xDYwv2boYOTkkBEwkLt59ywRhi0lcuLceKM7FISRwklHiyOHbUM4SRonNt+YwdzFy cLAJWEh0/9MGiYsITGSUOPD/DFicWUBd4uriIJBBwgIBEs+//WYDCYsIBEqsu8cKEhYR0JPY +/4VI4jNIqAqcXbVNHYQm1fAV2Ly9qdgNYxAN3w/tQbsHmYBcYlbT+ZD3SYgsWTPeWYIW1Ti 5eN/rCDjJQQUJZb3y0GU60gs2P2JDcLWlli28DUzxHhBiZMzn7BMYBSZhWTqLCQts5C0zELS soCRZRWjZHFqcVJuupGhXm56bolealFmcnFxfp5eceomRmDUHNzy23AH48Rr9ocYpTlYlMR5 GaZ3BgkJpCeWpGanphakFsUXleakFh9iZOLglGpgtKsx/+AbxBnB9FQ886C1hrBS3sod88Im FAsuEfFn37AzbaepVHqQeOuUaMnsdxN6NO6vayya28k6dYr8ydWttVv6f7Z907tlq5vz/seh yYsfGZye6vf/um/0Y3XrpNg3M9z6F2g53o+c8tn7nWFFr99XkW8f3hZvvXDn94QHYdzlP4ul Vvg6KrEUZyQaajEXFScCABrKgMBoAgAA
Cc: "" <>
Subject: Re: [MMUSIC] Comment on SIP Trickle ICE based on INFO draft - FORKING
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sun, 30 Mar 2014 09:48:46 -0000


> 2) Trickle ICE INFO with serial forking
>   a) INVITE from local
>   b) INVITE is forked by proxy to first remote destination
>   c) 100 trying is reaching local
>   d) INFO with Trickle ICE from local
>   e) INFO is forward by proxy to first remote destination
>   f) INVITE is forked by proxy to second remote destination
>   g) Whether INFO has to be forked?
> It is not mentioned in the draft whether INFO has to be forked to the
> second remote destination as well. Could you please explain the expect
> behavior for this scenario.

I am not sure what you mean by the INFO being forked.

When a new fork is created (i.e. when the offerer receives a 18x response from a new destination), whatever candidates have been trickled on previously created fork(s) of course need to be provided also on the new fork.

And, when multiple forks exist, whenever a new candidate is to be trickled, an INFO carrying the candidate needs to be sent on each fork.

I don't see a problem with this, but if it is unclear in the spec then some additional text might be needed.