Re: [MMUSIC] BUNDLE: SDP Offer Types

Paul Kyzivat <pkyzivat@alum.mit.edu> Wed, 05 June 2013 16:29 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 120CE21F9BD1 for <mmusic@ietfa.amsl.com>; Wed, 5 Jun 2013 09:29:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.037
X-Spam-Level:
X-Spam-Status: No, score=0.037 tagged_above=-999 required=5 tests=[AWL=-0.126, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, J_CHICKENPOX_56=0.6, 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 Xb3Ho1SgULoS for <mmusic@ietfa.amsl.com>; Wed, 5 Jun 2013 09:29:20 -0700 (PDT)
Received: from qmta01.westchester.pa.mail.comcast.net (qmta01.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:16]) by ietfa.amsl.com (Postfix) with ESMTP id 1831E21F9BC0 for <mmusic@ietf.org>; Wed, 5 Jun 2013 09:29:19 -0700 (PDT)
Received: from omta05.westchester.pa.mail.comcast.net ([76.96.62.43]) by qmta01.westchester.pa.mail.comcast.net with comcast id kalB1l0030vyq2s51gVKLY; Wed, 05 Jun 2013 16:29:19 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta05.westchester.pa.mail.comcast.net with comcast id kgVK1l0083ZTu2S3RgVKnK; Wed, 05 Jun 2013 16:29:19 +0000
Message-ID: <51AF675E.5010605@alum.mit.edu>
Date: Wed, 05 Jun 2013 12:29:18 -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: Christer Holmberg <christer.holmberg@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B1C37F87C@ESESSMB209.ericsson.se>, <51A8B059.7070705@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1C38134B@ESESSMB209.ericsson.se> <51ACFB79.1080207@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1C38248B@ESESSMB209.ericsson.se> <51AE14C5.6000701@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1C382EB7@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1C382EB7@ESESSMB209.ericsson.se>
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=1370449759; bh=ZMTn7f+uxQjvThUgi0u/Jf8OVx2ZdtG4T87keEKCPHE=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=cTKNpvxIZ+M5iHGXui6TlxHWwTv0A6hjOkq95kwJ8SO9BguVnIJoxdkMXlyoQIpmR xo9LGzHD1yjqE2V+dgxViGPiqepm+mxX/oUMFkCG5lEkQTHtxIQIr1+wWGIW2KrV5Q kFkf4TsUDiIMQvbOPxqmPKGD+9XPSMvzmdpceUNPJGKPOQVa688YxJHPycP/FMT9kG 7F8rENA7PKx+77tFpdHJYxBLos3R1NCu/0DyHi9fSQ/hh4mpC3guL6Uv3ShFCQc9lO 6eNHGXdG1V8VpNqPZlMmgv2zbRHRw7ajWmbt+zLsC5tebrJAN/qdV2owy2nKELh6y8 MLhVtABTXA/DQ==
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] BUNDLE: SDP Offer Types
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: Wed, 05 Jun 2013 16:29:26 -0000

I think we are now in full agreement.
(Just need the text to say this.)

	Thanks,
	Paul

On 6/5/13 2:02 AM, Christer Holmberg wrote:
> Hi,
>
>>>>>>> I'll throw the ball out with suggesting the following ones:
>>>>>>>
>>>>>>> -*Bundle restart offer* (different port value, currently referred
>>>>>>> to as "first offer")
>>>>>>>
>>>>>>> The reason I use "restart" wording is because this is used, no
>>>>>>> matter whether in the beginning of the session or mid-session, to
>>>>>>> (re-)negotiate the usage of BUNDLE, and the bundle address
>>>>>>> information selection.
>>>>>>>
>>>>>>> -*Bundle sync offer* (identical port value, currently referred to
>>>>>>> as "second offer")
>>>>>>>
>>>>>>> The reason I used "sync" wording is because this is used to ensure
>>>>>>> that intermediaries have correct address information for each m- line.
>>>>>>>
>>>>>>> Keep in mind that we may even need to split the sync offer into
>>>>>>> more sub types, when we get into the details of adding new m-
>>>>>>> lines etc, but I'd like to agree a base to start from :)
>>>>>>
>>>>>> Above seems like a good start, but I'm still grappling with some
>>>>>> things and don't know how to talk about concisely:
>>>>>>
>>>>>> I understand that the next offer after a Bundle Restart Offer will
>>>>>> typically be a Bundle Sync Offer. But if there is another offer
>>>>>> after a Bundle Sync Offer, and it doesn't change anything about the
>>>>>> bundle, then is it still a Bundle Sync Offer?
>>>>>
>>>>> Currently, yes.
>>>>
>>>> I agree that without adjusting the terminology this is the only right choice to make. But it is a little obscure. I'm not certain this needs to be improved, but I thought I would suggest that it might.
>>>>>
>>>>>> Also, I don't believe the above are mutually exclusive. If I send
>>>>>> an offer to add a new m-line to a bundle, and I give it distinct
>>>>>> address info so that the answerer may take it out of the bundle if
>>>>>> needed, then is that a Bundle Restart Offer or a Bundle Sync Offer?
>>>>>> It seems to be a bit of each. And of course there may be multiple
>>>>>> bundles described by the SDP, and these terms apply independently to each.
>>>>>>
>>>>>> Maybe we need a couple more terms for:
>>>>>>
>>>>>> - offer that adds a new m-line to bundle using the existing bundle
>>>>>>      address info.
>>>>>
>>>>> Technically that is a Bundle Sync Offer, but I DO agree that the wording is not good in this case - as it's not only about synchronization.
>>>>>
>>>>>> - offer that adds a new m-line to an existing bundle using unique
>>>>>>      address info.
>>>>>
>>>>> I agree that doesn't fit the current definitions.
>>>>>
>>>>> However, we will have to agree on whether we allow that in the first place, or whether the offerer will have to use 1) same address information or 2) different address information for ALL m- lines (Bundle Restart Offer).
>>>>
>>>> Yes, we need to settle on whether either or both of these are permitted.
>>>>
>>>> But I can think of reasons why I might wish to use either one, and no good reason not to allow both. So allowing both is my preference.
>>>
>>> I personally think we should allow BOTH 1) and 2).
>>>
>>> The question is whether we should allow 3), which is new m- line with unique address, while the other m- lines use the bundle address.
>>
>> I agree it is a valid question to ask.
>> Again, I can see how it might be useful sometimes, and I can see no reason not to allow it. Its just a special case of the bundle restart offer.
>
> We could modify the definition of bundle restart offer, to allow that some m- lines may use the same address information.
>
> It needs to be very clear, though, that such m- lines cannot be moved out of the BUNDLE group by the Answerer, as they don't have a unique address to fallback to.
>
> However, the Answerer MAY still change the address for such m- lines to the address of the added m- line - especially if the Offerer puts the mid value associated with the new m- line first in the SDP group:BUNDLE attribute mid value list.
>
>> (Note, IMO it should be ok for the very first offer to propose a bundle with address info already shared among m-lines in the proposed bundle.
>> Using that trades off potential interop issues for speed in establishing the session.)
>
> My intention (and, that's why I appreciate all feedback I can get :) is to make the procedures very generic, and not separate between initial and subsequent offers (other than in examples).
>
> Regards,
>
> Christer
>
>