Re: [MMUSIC] BUNDLE Weekly Summary: Assumptions

Jonathan Lennox <jonathan@vidyo.com> Mon, 13 May 2013 19:25 UTC

Return-Path: <jonathan@vidyo.com>
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 1737B21F93FC for <mmusic@ietfa.amsl.com>; Mon, 13 May 2013 12:25:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 vBc4V5f4JiU4 for <mmusic@ietfa.amsl.com>; Mon, 13 May 2013 12:24:54 -0700 (PDT)
Received: from mxout.myoutlookonline.com (mxout.myoutlookonline.com [64.95.72.252]) by ietfa.amsl.com (Postfix) with ESMTP id BF58621F93EA for <mmusic@ietf.org>; Mon, 13 May 2013 12:24:54 -0700 (PDT)
Received: from mxout.myoutlookonline.com (localhost [127.0.0.1]) by mxout.myoutlookonline.com (Postfix) with ESMTP id 42B3955628A; Mon, 13 May 2013 15:24:49 -0400 (EDT)
X-Virus-Scanned: by SpamTitan at mail.lan
Received: from HUB013.mail.lan (unknown [10.110.2.1]) by mxout.myoutlookonline.com (Postfix) with ESMTP id 7D777556057; Mon, 13 May 2013 15:24:48 -0400 (EDT)
Received: from BE235.mail.lan ([10.110.32.235]) by HUB013.mail.lan ([10.110.17.13]) with mapi; Mon, 13 May 2013 15:24:20 -0400
From: Jonathan Lennox <jonathan@vidyo.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Date: Mon, 13 May 2013 15:24:48 -0400
Thread-Topic: [MMUSIC] BUNDLE Weekly Summary: Assumptions
Thread-Index: Ac5QD3hQUkNe6OTvSAu+p4CH0kyx2Q==
Message-ID: <789CDEFF-5266-4F0B-8EE3-65D879840616@vidyo.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> <519134FF.5010405@alum.mit.edu>
In-Reply-To: <519134FF.5010405@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>
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 19:25:00 -0000

On May 13, 2013, at 2:46 PM, Paul Kyzivat wrote:

> 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.)

An offerer sends an initial offer with a bundle of two m-lines: one with port 20000, one with 30000.

The answerer answers, rejecting the first m-line (with port zero) but accepting the bundle.

Should the answerer send traffic to port 20000 or port 30000?

--
Jonathan Lennox
jonathan@vidyo.com