Re: [MMUSIC] MMUSIC Virtual Interim Meeting dial in information

Christer Holmberg <> Wed, 22 May 2013 07:31 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D734221F8E34 for <>; Wed, 22 May 2013 00:31:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -5.985
X-Spam-Status: No, score=-5.985 tagged_above=-999 required=5 tests=[AWL=-0.036, BAYES_00=-2.599, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Uwm6FMKHgHK0 for <>; Wed, 22 May 2013 00:31:33 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 2176921F923B for <>; Wed, 22 May 2013 00:31:32 -0700 (PDT)
X-AuditID: c1b4fb2d-b7fe36d000007102-0b-519c745314f8
Received: from (Unknown_Domain []) by (Symantec Mail Security) with SMTP id F5.C7.28930.3547C915; Wed, 22 May 2013 09:31:31 +0200 (CEST)
Received: from ([]) by ([]) with mapi id 14.02.0328.009; Wed, 22 May 2013 09:31:31 +0200
From: Christer Holmberg <>
To: "Cullen Jennings (fluffy)" <>, =?iso-8859-1?Q?Ari_Ker=E4nen?= <>
Thread-Topic: [MMUSIC] MMUSIC Virtual Interim Meeting dial in information
Thread-Index: AQHOViuhx4Lx4HC4/kirmiPp0dh72ZkPj0SAgAE/0MA=
Date: Wed, 22 May 2013 07:31:30 +0000
Message-ID: <>
References: <> <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrHLMWRmVeSWpSXmKPExsUyM+JvrW5wyZxAgw1nTS3eX9C16JjMZjF1 +WMWB2aPKb83snosWfKTKYApissmJTUnsyy1SN8ugStjfn8ra8Ed9orz364wNzD+Ye1i5OSQ EDCR+LNxPSOELSZx4d56ti5GLg4hgcOMEo139jNDOEsYJSbsng6U4eBgE7CQ6P6nDdIgIpAn MXf1dmYQm1kgXmLTuzesICXCAh4S/74XQZR4SnReXMsMYVtJ7F38FWwvi4CqxIrWPjYQm1fA V+LlnVnsEKu6mSSOz+8BS3ACJf79PQTWwAh03PdTa5ggdolL3HoynwniaAGJJXvOM0PYohIv H/8Du0FCQFFieb8cRLmexI2pU9ggbG2JZQtfM0PsFZQ4OfMJywRGsVlIps5C0jILScssJC0L GFlWMbLnJmbmpJcbbmIExsnBLb91dzCeOidyiFGag0VJnLdXe2qgkEB6YklqdmpqQWpRfFFp TmrxIUYmDk6pBkZ7Bed8xTKjOB195d8z6k3UFxsUFyqqKNhtvRDB5S50L2P1TyWjm1w7Xv/w OdhgXWDTdsvAfVfZq4kVJ/kt+l7zHrV0qskNXKB9dO7zM363zuxafGFe6SZVvqtuj9judX3f qPXujtOqlI/XJu55cKMq3EZifn182HzP5Ud7+H3Me3lee5cG+ymxFGckGmoxFxUnAgDlt40H YQIAAA==
Cc: "Flemming Andreasen \(fandreas\)" <>, "" <>
Subject: Re: [MMUSIC] MMUSIC Virtual Interim Meeting dial in information
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: Wed, 22 May 2013 07:31:40 -0000


I will address Paul's input later, but a general comment.

>> 1)	How to demux RTP (and other media types, but RTP is the most critical). This is currently discussed within the "Plan A vs Plan B" context on the RTCWEB list.
> If we don't end up with the people in the call that are involved wight he proposals on this, I don't think we will be able to do this. I see it breaking into two different topics 

Well, the question is whether how-to-demux is really dependent on Plan A vs Plan B. In my opinion the demux mechanism should not be dependent. 

No matter whether we choose Plan A or Plan B, at the end of the day a client will end up receiving multiple media on a single 5-tuple, and it needs to know how to demux it.

But, if people think that we CAN NOT move forward with how-to-demux until we have made a decision regarding Plan A vs Plan B, then we should probably remove it from the Thursday agenda.