Re: [MMUSIC] When a bundle offer is forked

Paul Kyzivat <pkyzivat@alum.mit.edu> Thu, 23 May 2013 19:08 UTC

Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8E0C21F9737 for <mmusic@ietfa.amsl.com>; Thu, 23 May 2013 12:08:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.292
X-Spam-Level:
X-Spam-Status: No, score=-0.292 tagged_above=-999 required=5 tests=[AWL=0.145, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fTszHZp9udjr for <mmusic@ietfa.amsl.com>; Thu, 23 May 2013 12:08:27 -0700 (PDT)
Received: from qmta03.westchester.pa.mail.comcast.net (qmta03.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:32]) by ietfa.amsl.com (Postfix) with ESMTP id 2815A21F8859 for <mmusic@ietf.org>; Thu, 23 May 2013 11:44:08 -0700 (PDT)
Received: from omta12.westchester.pa.mail.comcast.net ([76.96.62.44]) by qmta03.westchester.pa.mail.comcast.net with comcast id fUWR1l0020xGWP853Wk81P; Thu, 23 May 2013 18:44:08 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta12.westchester.pa.mail.comcast.net with comcast id fWk71l01d3ZTu2S3YWk7iP; Thu, 23 May 2013 18:44:08 +0000
Message-ID: <519E6376.9020302@alum.mit.edu>
Date: Thu, 23 May 2013 14:44:06 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: mmusic@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B1C374357@ESESSMB209.ericsson.se> <519A1336.9010001@jitsi.org> <9F33F40F6F2CD847824537F3C4E37DDF1159D127@MCHP04MSX.global-ad.net> <519A229D.7090204@jitsi.org> <7594FB04B1934943A5C02806D1A2204B1C374463@ESESSMB209.ericsson.se> <519A2768.5010904@alum.mit.edu> <CAPvvaa+A=LkYp9A+wENAABwCYaQcD0HVeX4o+O_16iJRPXZfNw@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1C3744DC@ESESSMB209.ericsson.se> <CAPvvaaJsPNk1DAJXYoc8aUgZ0ZayV_8q84W=Mm7vwuRRGuwC-g@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1C374572@ESESSMB209.ericsson.se> <519A3883.8060006@jitsi.org> <519A3C8F.3040309@alum.mit.edu> <519B343A.30704@jitsi.org> <519BB598.1030909@alum.mit.edu> <519DF0F8.1070407@jitsi.org> <519E530C.60705@alum.mit.edu> <007801ce57e1$c523a9f0$4f6afdd0$@co.in>
In-Reply-To: <007801ce57e1$c523a9f0$4f6afdd0$@co.in>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1369334648; bh=xsaVdnqYKrXLpomH8lec1GN3wdGwABLMrz4qwq6AA0o=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=imaPdQkD2s5Y+wUCHslqz03ojwEaR6IJrqPtG628xEVS8u/3fj+Thxs9hWAjdCe+l o0Hsv+QUd206Jg+u//7TiXvkeXGieWpQ+5mkez06sVMM9HVcIEhEM6H/KIHqCTmDG6 ZXdLfKTqXsFHyxe60WGgh6qH339/aOx79KnZYxaKXZVxgjCrENi9OQuJ6Ttq//Lvn7 0OM9aRVIa9Xe9kPz4XHgEgDZGBB29+2zD9/9f7qXJ2CeICD9vrRscAF8/KmUipNg2H UplyhiwB7Rewzs60N4/vhI21zs3tjx7HK29H423ol5mmUz0hUJBfL3JvcusCXxWSo8 okQ+Z+OCecmBQ==
Subject: Re: [MMUSIC] When a bundle offer is forked
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.12
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, 23 May 2013 19:08:42 -0000

Partha,

On 5/23/13 2:17 PM, Parthasarathi R wrote:
> Paul,
>
> I agree with you that it takes more energy to solve bundle with forking.
> Forking is not low probability event as of now in SIP deployments. I wish to
> see the forking within the scope of this work.

If so, can you take a stab at enumerating the issues that can arise, and 
how they should be handled?

	Thanks,
	Paul

> Thanks
> Partha
>
>> -----Original Message-----
>> From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On
>> Behalf Of Paul Kyzivat
>> Sent: Thursday, May 23, 2013 11:04 PM
>> To: Emil Ivov
>> Cc: mmusic; Christer Holmberg
>> Subject: [MMUSIC] When a bundle offer is forked
>>
>> On 5/23/13 6:35 AM, Emil Ivov wrote:
>>
>>> In case a bundle offer gets forked and various answers ...
>>
>> I trimmed everything else out of Emil's reply, and changed to subject,
>> because this is a whole different can of worms!
>>
>> I think we must acknowledge that this *can* happen, though it is a low
>> probability event. It raises all sorts of ugly issues. A few:
>>
>> * if the bundle is accepted by multiple forks, does this form
>>     one RTP session or several? If so,
>>
>>     - if so, then if each fork accepts a different set of m-lines from
>>       the bundle, how can that work with a single RTP session?
>>
>> * How does ICE work in this case? (Is that already covered by ICE,
>>     since it mostly isn't specific to bundle?
>>
>> * If one fork adds/removes an m-line from the bundle, should that
>>     be mirrored to the other forks?
>>
>> * ...
>>
>> ISTM that the simplest thing we could do about this is put a statement
>> in the draft that this draft does not specify behavior in the case of
>> forking - that conforming devices are constrained to a single fork, and
>> that behavior in forking cases could be a subject of future
>> standardization.
>>
>> 	Thanks,
>> 	Paul
>>
>> _______________________________________________
>> 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
>