Re: [rtcweb] [MMUSIC] FW: New Version Notification for draft-ejzak-mmusic-bundle-alternatives-00.txt

Christer Holmberg <> Wed, 20 February 2013 12:27 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B7CFA21F87CB; Wed, 20 Feb 2013 04:27:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.152
X-Spam-Status: No, score=-6.152 tagged_above=-999 required=5 tests=[AWL=-0.162, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_Z=0.259]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id N7lzB69NK3eW; Wed, 20 Feb 2013 04:27:56 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 2B51421F87D5; Wed, 20 Feb 2013 04:27:56 -0800 (PST)
X-AuditID: c1b4fb30-b7f0d6d000007e61-37-5124c14ba63b
Received: from (Unknown_Domain []) by (Symantec Mail Security) with SMTP id A0.23.32353.B41C4215; Wed, 20 Feb 2013 13:27:55 +0100 (CET)
Received: from ([]) by ([]) with mapi id 14.02.0318.004; Wed, 20 Feb 2013 13:27:54 +0100
From: Christer Holmberg <>
To: "Ejzak, Richard P (Richard)" <>, "" <>, "" <>
Thread-Topic: [MMUSIC] FW: New Version Notification for draft-ejzak-mmusic-bundle-alternatives-00.txt
Thread-Index: AQHODiLaQ3NGrbmfrEqTjL/GIyKINpiAKZHwgAJ/clA=
Date: Wed, 20 Feb 2013 12:27:54 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrMLMWRmVeSWpSXmKPExsUyM+Jvja73QZVAg44+MYupyx+zWPQ2hFus /dfO7sDs0fpsL6vHkiU/mQKYorhsUlJzMstSi/TtErgy/p0/x1QwQ6riQtMz5gbGFyJdjJwc EgImEsfP/GaHsMUkLtxbz9bFyMUhJHCIUeLj4TusEM5iRonVn08CVXFwsAlYSHT/0waJiwj0 M0p0f1vMCNItLJAmMXNSExuILSKQLvHq4gMo20rizMs1YDUsAqoSD96tAZvDK+AtcfmOFYgp JBAjMeFWFEgFp0CsxKkF71lBbEage76fWsMEYjMLiEvcejKfCeJOAYkle84zQ9iiEi8f/2OF sBUlrk5fDlWvI7Fg9yc2CFtbYtnC12D1vAKCEidnPmGZwCg6C8nYWUhaZiFpmYWkZQEjyypG 9tzEzJz0cvNNjMCIOLjlt8EOxk33xQ4xSnOwKInzhrteCBASSE8sSc1OTS1ILYovKs1JLT7E yMTBKdXAKFXFW6tztKQqa2lhgsPdaLOWiIdNNVum9ZS4beNQ45R5v7v1Q3LVlJO7NutPkrBo /bP2VLi6A4vmPaOHW65+er7AX0I7JyYkuUdMbmvodo2g/o2bQpTdfEtXVibf4EuZI9s9YUK8 /ew+s5f5Nx0uyxnflvnCzZravum8UoNKoqTBQ1PTEzeVWIozEg21mIuKEwH8jnfFVgIAAA==
Subject: Re: [rtcweb] [MMUSIC] FW: New Version Notification for draft-ejzak-mmusic-bundle-alternatives-00.txt
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 20 Feb 2013 12:27:58 -0000

Hi Richard,

It would have been good with some example messages/flows, but I'll give my comments based on my understanding of the text. Also, I'll focus on the "Unspecified address for subsequent m lines in SDP answer" alternative, as it is the one you recommend, but I believe my comments also apply to some of the other alternatives.

In general, you only focus on one single issue, but leave a number of questions unanswered.

First, as you will now have a single non-zero m- line, you still assume that entities (including intermediaries) will take information (media types, payload type mappings etc etc etc - even protocol, if we decide to also allow the data channel in the bundle) from all m- lines. Or, do you intend to put all that information into a single m- line? If so, in my opinion MMT is a much better approach.

Second, what if a user wants the disable, or reject, a specific stream, using port zero? How is it done in case the stream is already represented by a zero m- line? How is it done in case the stream is represented by the non-zero m- line which contains the port number value used for the whole bundle?



-----Original Message-----
From: [] On Behalf Of Ejzak, Richard P (Richard)
Sent: 19. helmikuuta 2013 0:09
Subject: [MMUSIC] FW: New Version Notification for draft-ejzak-mmusic-bundle-alternatives-00.txt

Please note that I have also submitted a draft on how to fix BUNDLE.  This doc is based on the modified BUNDLE proposal with different port information for each m line and compares several different additional modifications to BUNDLE.  The doc ends up recommending the use of the unspecified address for subsequent m lines in a bundle group in the SDP answer (not offer).  Please see the doc for details.

-----Original Message-----
From: [] 
Sent: Monday, February 18, 2013 3:57 PM
To: Ejzak, Richard P (Richard)
Subject: New Version Notification for draft-ejzak-mmusic-bundle-alternatives-00.txt

A new version of I-D, draft-ejzak-mmusic-bundle-alternatives-00.txt
has been successfully submitted by Richard Ejzak and posted to the IETF repository.

Filename:	 draft-ejzak-mmusic-bundle-alternatives
Revision:	 00
Title:		 Alternatives to BUNDLE
Creation date:	 2013-02-18
Group:		 Individual Submission
Number of pages: 7

   This paper discusses some potential modifications to the BUNDLE
   proposal for multiplexing of multiple media types within a single
   5-tuple to address limitations of the current proposal and
   alternatives already considered by MMUSIC.


The IETF Secretariat

mmusic mailing list