Re: [MMUSIC] BUNDLE DECISSION: Full bundle or no bundle - there aint anything in between

Christer Holmberg <> Mon, 27 May 2013 10:05 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id ED40D21F9397 for <>; Mon, 27 May 2013 03:05:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -5.539
X-Spam-Status: No, score=-5.539 tagged_above=-999 required=5 tests=[AWL=0.109, BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, J_CHICKENPOX_47=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id e4MdOLMTNJPM for <>; Mon, 27 May 2013 03:04:57 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 11E9621F9347 for <>; Mon, 27 May 2013 03:04:51 -0700 (PDT)
X-AuditID: c1b4fb30-b7f8a6d000001a2d-be-51a32fc235f0
Received: from (Unknown_Domain []) by (Symantec Mail Security) with SMTP id 1C.10.06701.2CF23A15; Mon, 27 May 2013 12:04:51 +0200 (CEST)
Received: from ([]) by ([]) with mapi id 14.02.0328.009; Mon, 27 May 2013 12:04:50 +0200
From: Christer Holmberg <>
To: Suhas Nandakumar <>
Thread-Topic: [MMUSIC] BUNDLE DECISSION: Full bundle or no bundle - there aint anything in between
Thread-Index: Ac5YZ89eNSNKdC6FQhCoA7qw0p8XLAAUyP6AAIGn7AA=
Date: Mon, 27 May 2013 10:04:50 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1C3795A5ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrPLMWRmVeSWpSXmKPExsUyM+Jvre5h/cWBBo/7uCymLn/MYrFzbgez A5PHzll32T2WLPnJFMAUxWWTkpqTWZZapG+XwJVxdM5H9oLO6Iotu16yNTBeCuhi5OSQEDCR 2LTiBjOELSZx4d56ti5GLg4hgcOMEue+LGICSQgJLGGUmLY0rouRg4NNwEKi+582SFhEQEti 9eK5TCBhZgF1iauLg0BMYYFkiS0f8iEqUiSOL77FCmFbSTx/0cIIUsIioCrRtswLJMwr4Csx 6dJaZog9UxglDk7mArE5BQIlurddZQexGYEO+35qDdgtzALiEreezGeCOFhAYsme81DHi0q8 fPyPFWS8hICixPJ+OYjyfImpbdvZIVYJSpyc+YRlAqPoLCSTZiEpm4WkDCKuI7Fg9yc2CFtb YtnC18ww9pkDj5mQxRcwsq9iZM9NzMxJLzffxAiMpINbfhvsYNx0X+wQozQHi5I4rz7v4kAh gfTEktTs1NSC1KL4otKc1OJDjEwcnFINjKcfq4rsLxU+asq1uvcIc0rZwfirUd0hrhZijr5l TY+qHXLTuW35+vtbjVjP/mrbO22Ki+hsQUXL0/stHVfnnSkQ23eZ2bjJyJz33YNjwUd8/G5s uj5bhW3LLk7RRWZvZzXUcW86uvX9fs11lU+PP+eqvlVrubZz4cwb61njw5K5IxRK3ASeKLEU ZyQaajEXFScCAHbWR7NyAgAA
Cc: "" <>
Subject: Re: [MMUSIC] BUNDLE DECISSION: Full bundle or no bundle - there aint anything in between
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 27 May 2013 10:05:03 -0000


The text suggested by Paul is good.



From: Suhas Nandakumar []
Sent: 25. toukokuuta 2013 1:12
To: Christer Holmberg
Subject: Re: [MMUSIC] BUNDLE DECISSION: Full bundle or no bundle - there aint anything in between

Hey Christer

   This looks good ( including Paul's clarification and Martin's statement about Expectation of the following fixup to make intermediaries happy).

Also few comments inline.
On Fri, May 24, 2013 at 3:28 AM, Christer Holmberg <<>> wrote:

At the interim yesterday, we agreed that an answerer MUST always include identical ports* (usage of port zero within a bundle is a separate topic) for all m- lines within an bundle group.

If the answerer wants to use different ports* for some/all m- lines, it MUST NOT include those m- lines in a bundle group (if they already are in a bundle group, a separate offer is needed to remove them).

[Suhas] If the answerer wants to use different ports for "ALL" the m-lines then it is implicitly assumed that there was a Successful O/A exchange + Fixup and this Offer is a subsequent one.
On the other hand, changing some ports in the Answer can even happen in the first ever BUNDLE O/A as well.
Just wanted to clarify with the wordings.

WHAT IT MEANS: There is no way for an answerer to tell that the offerer, for certain m- lines, can use the same port*, eventhough the answer will use separate ports*.

I will work on some actual text proposal later, but please indicate if you OBJECT to this approach in general.



NOTE: "port" = port:address combination - we are working on coming up with better terminology :)

mmusic mailing list<>