IETF Logo Mail Archive

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

Christer Holmberg <christer.holmberg@ericsson.com> Thu, 03 April 2014 08:03 UTC

Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDF601A0117 for <mmusic@ietfa.amsl.com>; Thu, 3 Apr 2014 01:03:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4ijp6ULEc3Ib for <mmusic@ietfa.amsl.com>; Thu, 3 Apr 2014 01:03:02 -0700 (PDT)
Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id 611BA1A00B2 for <mmusic@ietf.org>; Thu, 3 Apr 2014 01:03:01 -0700 (PDT)
X-AuditID: c1b4fb38-b7f518e000000889-9b-533d14f9cc7b
Received: from ESESSHC021.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id 9A.B6.02185.9F41D335; Thu, 3 Apr 2014 09:59:53 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.213]) by ESESSHC021.ericsson.se ([153.88.183.81]) with mapi id 14.03.0174.001; Thu, 3 Apr 2014 09:59:38 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] Comment on SIP Trickle ICE based on INFO draft - FORKING
Thread-Index: AQHPS/02PLTBD8bHIkyTiQF+pdjMC5r+wT+AgADMF+c=
Date: Thu, 03 Apr 2014 07:59:37 +0000
Message-ID: <dro1b68p90h76f6aawmpjj44.1396511973109@email.android.com>
References: <7594FB04B1934943A5C02806D1A2204B1D26BE6A@ESESSMB209.ericsson.se>, <533C85D5.3060700@alum.mit.edu>
In-Reply-To: <533C85D5.3060700@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrKLMWRmVeSWpSXmKPExsUyM+Jvje4GUdtggy8npC2mLn/MYrFiwwFW ByaPv+8/MHksWfKTKYApissmJTUnsyy1SN8ugSvjyZXdbAV9AhVHzlxgbWA8xtPFyMkhIWAi cbbrPxuELSZx4d56IJuLQ0jgKKPExQdTWCCcxYwSfy7eZ+xi5OBgE7CQ6P6nDdIgIuAr8ezx bbBmYYEAiZ8b37FDxAMlPn9dzAxhW0lM2viJFcRmEVCR2LfjNCOIzSvgJnHwFURcSCBXonn5 MzCbU0BHovHbVxYQmxHooO+n1jCB2MwC4hK3nsxngjhUQGLJnvPMELaoxMvH/1ghanQkFuz+ xAZha0ssW/iaGWKXoMTJmU9YJjCKzEIyahaSlllIWmYhaVnAyLKKkaM4tTgpN93IYBMjMOgP bvltsYPx8l+bQ4zSHCxK4rwf3zoHCQmkJ5akZqemFqQWxReV5qQWH2Jk4uCUamAssc/vLhNb 8fRWVZ5+/9y5z9ZeVTo6cbuRpJ8iW6hzn/Xrz9f6H5d2OOfbpew3Y7BaOSda9zOz3L5JXPXH 3PlVXrXM64jJvch4xG3SpWLPpxMWbX/h5s6x3XHKiyes55o4XZinSrQlb2A4/me6SPaC1rk1 m8+xTej7nC0596H2aU2DKT4fNn1VYinOSDTUYi4qTgQABgcTWkgCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/i1tbY_1njqPshJuZOELf_Lh2poA
Subject: Re: [MMUSIC] Comment on SIP Trickle ICE based on INFO draft - FORKING
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Apr 2014 08:03:18 -0000

Hi,

That is what I tried to say :)

The INFO itself is not forked, but once you have multiple early dialogs you need to send INFO on all of them.

Regards,

Christer

Sent from my Sony Ericsson Xperia arc S

Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:


Just to clarify: INFOs are never forked.

An INFO isn't sent until there is an early (or confirmed) dialog. And
then each INFO is sent within a particular dialog. If the INVITE is
forked, then *separate* INFOs can be sent, each in one of the dialogs.

        Thanks,
        Paul

On 3/30/14 5:48 AM, Christer Holmberg wrote:
> Hi,
>
>> 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.
>
> Regards,
>
> Christer
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>

_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www.ietf.org/mailman/listinfo/mmusic

v2.23.0 | Report a Bug | By Email