Re: [rtcweb] Stream control: [MMUSIC] msid-04 submitted

Christer Holmberg <> Wed, 19 February 2014 20:50 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 7B7481A04C1 for <>; Wed, 19 Feb 2014 12:50:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.869
X-Spam-Status: No, score=-2.869 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, HTML_FONT_FACE_BAD=0.981, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id FlNQ3PSWV2TG for <>; Wed, 19 Feb 2014 12:50:42 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 4F5D01A0418 for <>; Wed, 19 Feb 2014 12:50:41 -0800 (PST)
X-AuditID: c1b4fb25-b7f038e000005d01-ee-5305191cf5e7
Received: from (Unknown_Domain []) by (Symantec Mail Security) with SMTP id EA.F9.23809.C1915035; Wed, 19 Feb 2014 21:50:37 +0100 (CET)
Received: from ([]) by ([]) with mapi id 14.02.0387.000; Wed, 19 Feb 2014 21:50:36 +0100
From: Christer Holmberg <>
To: Harald Alvestrand <>, "" <>
Thread-Topic: [rtcweb] Stream control: [MMUSIC] msid-04 submitted
Thread-Index: AQHPKVPuF/VJzX0Fb0yVt/Xv3TzOfJq0+6GAgAAXm1SABo2kgIAAovSRgACVFICAADzpYg==
Date: Wed, 19 Feb 2014 20:50:35 +0000
Message-ID: <>
References: <>, <> <>, <> <>, <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
Content-Type: multipart/alternative; boundary="_000_pi22myx9puvcw80lbn1s1ktu1392843033581emailandroidcom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrNLMWRmVeSWpSXmKPExsUyM+Jvja6sJGuwQeNOLotjfV1sFmv/tbM7 MHlcmXCF1WPJkp9MAUxRXDYpqTmZZalF+nYJXBm336xgKXhoULH4y1fmBsazml2MnBwSAiYS Zx9fZ4WwxSQu3FvP1sXIxSEkcIhRYsmO+4xdjBxAzhJGicv6ICabgIVE9z9tkHIRgWCJ3ufv GUFsYQEHiXuHpjJDxB0l5mxdzgRhh0lMW3kdzGYRUJW4OfkwC4jNK+Am8av9ANSqqUwS185O YANJcAroSnzcsB/sHkage76fWgPWzCwgLnHryXwmiDsFJJbsOc8MYYtKvHz8jxWiJkfi6Y// UAsEJU7OfMIygVF4FpL2WUjKZiEpg4gbSHx5fxvK1pZYtvA1M4StL9H9/jQTsvgCRvZVjOy5 iZk56eVGmxiBEXJwy2/VHYx3zokcYpTmYFES5/3w1jlISCA9sSQ1OzW1ILUovqg0J7X4ECMT B6dUA2M/+119T7OJdlnvip+LKT69XWO3yKs3g5M3+M8FWeFiqy/87YvrY9XEfoY+WMwUysJu 5pJ41FGMVept0OQOB5+asrX835cvnr+dJeXjt4pwNZ0J158/qUzb5sIqczqITesrI/uGzPIy A+9nEv7RhZ7BHdNYGuYkxH+uf3vbU/Pr9DPWnzR2KLEUZyQaajEXFScCAKHW/t1eAgAA
Subject: Re: [rtcweb] Stream control: [MMUSIC] msid-04 submitted
X-Mailman-Version: 2.1.15
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, 19 Feb 2014 20:50:48 -0000


If the indication is NOT permanent, can't we use the existing direction attributes (sendrecv, sendonly etc)?



Sent from my Sony Ericsson Xperia arc S

Harald Alvestrand <> wrote:

On 02/19/2014 09:19 AM, Christer Holmberg wrote:

If the indication is “permanent”, rather than using a new msid-control attribute, could it be indicated by NOT including some information in the Answer?

Certainly, but then you have to include some information in the answer when the indication is not permanent.

Which information were you thinking of utilizing as a signal?



Sent from Windows Mail

From: 'Harald Alvestrand'<>
Sent: ‎Wednesday‎, ‎February‎ ‎19‎, ‎2014 ‎1‎:‎35‎ ‎AM
To: Hans-Christer Holmberg<>,<>

One thing I did not add in my previous reply:

If an offerer sets the direction of an m-line to sendrecv, and the
answerer sets the direction to sendonly, the offerer will have no
indication of whether the answerer intended the suspension of traffic to
be temporary (msid-control: disable) or permanent (msid-control: reject
or msid-control: stop).

That was actually the main concern that drove the desire for a new
Once the new mechanism was in place, it seemed logical to be explicit
about the other possible actions too, rather than relying on the
sendrecv/sendonly/recvonly parameter.


Surveillance is pervasive. Go Dark.