Re: [MMUSIC] BUNDLE Weekly Summary: Assumptions

Paul Kyzivat <pkyzivat@alum.mit.edu> Mon, 13 May 2013 18:46 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 02C6021F8EBD for <mmusic@ietfa.amsl.com>; Mon, 13 May 2013 11:46:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.4
X-Spam-Level:
X-Spam-Status: No, score=-0.4 tagged_above=-999 required=5 tests=[AWL=0.038, 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 WpsnRzjTeFwj for <mmusic@ietfa.amsl.com>; Mon, 13 May 2013 11:46:25 -0700 (PDT)
Received: from qmta05.westchester.pa.mail.comcast.net (qmta05.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:48]) by ietfa.amsl.com (Postfix) with ESMTP id 12FF221F8EA5 for <mmusic@ietf.org>; Mon, 13 May 2013 11:46:24 -0700 (PDT)
Received: from omta13.westchester.pa.mail.comcast.net ([76.96.62.52]) by qmta05.westchester.pa.mail.comcast.net with comcast id bPqh1l00717dt5G55WmQ02; Mon, 13 May 2013 18:46:24 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta13.westchester.pa.mail.comcast.net with comcast id bWmQ1l00D3ZTu2S3ZWmQDU; Mon, 13 May 2013 18:46:24 +0000
Message-ID: <519134FF.5010405@alum.mit.edu>
Date: Mon, 13 May 2013 14:46:23 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B1C36B485@ESESSMB209.ericsson.se> <C5E08FE080ACFD4DAE31E4BDBF944EB1134DEF4B@xmb-aln-x02.cisco.com> <CABcZeBMrgaHGXFi_NRk+znsT-AGnRS5EDLgFhZgGA+VG81BhZw@mail.gmail.com> <CABkgnnW=4zNgauXc-=pv9j9zGdVntmb=K22wcRr77wfQc-6J3w@mail.gmail.com> <CABcZeBODcyo-JXqs6EZ-F5BY_TaM94+eu+UqNApFnTNjpehUzA@mail.gmail.com> <518D73E4.4090609@alum.mit.edu> <9D12C4E8-F7C1-4D32-A8AC-570AC86ACA23@vidyo.com> <518D9361.7060301@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1C36EC03@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B1C36F1EB@ESESSMB209.ericsson.se> <5191033D.4040605@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1C36F59E@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1C36F59E@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=1368470784; bh=2T1ySvfP2ISbS9XSr6BkKZqHbab20TaSYFExw8dF9+k=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=o8t6vbQCIzvzEyXj5KBSvNsO8bWV4mJiHXmr3Tj/E0pq6MPOI9SBFX/7fvOuRKccU zovEmQuhdlczmyZytL/Iyag0yqw1V4dU2epAsVGr7FE/vPyuX9lbDuwZAinetKZcxd 9IKbUI1itUi4wx1dMUMCZA8WMbn/KPuKDkzPQs3sM0w7zp+1FOx3znitB46lr25kwj 2xh3V0V4IHlroIXiaAbklYt1fzafCfdDA0T1rv9lz146T+qiFqknPPxOBbviK99Pdq g1dGgLAeH3+NuQnGCGFySjQlMWMVV0sjmnwPAijeJYHSwjUlKETc2GF56PPheslXO4 n8erXw8ra6MQA==
Cc: Jonathan Lennox <jonathan@vidyo.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] BUNDLE Weekly Summary: Assumptions
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: Mon, 13 May 2013 18:46:31 -0000

On 5/13/13 2:26 PM, Christer Holmberg wrote:

>>> Q4:
>>>
>>> We need to keep in mind that there is always a chance that the "top-most" m- line within a bundle group is a port zero one.
>>
>> What is the question?
>
> Well, there are basically two "warm-up" questions:
>
> Q4_1: When the first offer, with DIFFERENT port numbers is sent, and the receiver accepts bundle, is the receiver expected to be able to send media/data according to that?

I hope so.

> Q4_2: IF Q4_1 THEN which m- line does the receiver use to send media/data (when the second offer comes, with identical port numbers, it is no longer an issue).

Surely the bundle draft must specify this.

My first thought is that the address/port of the *first* m-line in the 
bundle with a non-zero port will be used for the entire bundle.

(This means that when you initially offer a bundle with a bunch of 
separate ports, you not only must be prepared to use each of those for 
an unbundled m-line, you must be prepared to use any of them for the 
complete bundle.)

	Thanks,
	Paul