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

Christer Holmberg <> Wed, 19 February 2014 08:19 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id E4E9D1A043C for <>; Wed, 19 Feb 2014 00:19:07 -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 TaBWMsK5ss43 for <>; Wed, 19 Feb 2014 00:19:06 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 4F1801A0080 for <>; Wed, 19 Feb 2014 00:19:05 -0800 (PST)
X-AuditID: c1b4fb2d-b7f5d8e000002a7b-b1-530468f58a8c
Received: from (Unknown_Domain []) by (Symantec Mail Security) with SMTP id 28.3F.10875.5F864035; Wed, 19 Feb 2014 09:19:01 +0100 (CET)
Received: from ([]) by ([]) with mapi id 14.02.0387.000; Wed, 19 Feb 2014 09:19:01 +0100
From: Christer Holmberg <>
To: 'Harald Alvestrand' <>, "" <>
Thread-Topic: [rtcweb] Stream control: [MMUSIC] msid-04 submitted
Thread-Index: AQHPKVPuF/VJzX0Fb0yVt/Xv3TzOfJq0+6GAgAAXm1SABo2kgIAAovSR
Date: Wed, 19 Feb 2014 08:19:00 +0000
Message-ID: <>
References: <>, <> <>, <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D1A9B80ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrDLMWRmVeSWpSXmKPExsUyM+Jvje7XDJZgg3PvVS2O9XWxWaz9187u wORxZcIVVo8lS34yBTBFcdmkpOZklqUW6dslcGU8+PeeuWCaRsXzz8eZGxgblLsYOTkkBEwk ZrxrZYGwxSQu3FvP1sXIxSEkcIhRYtXRmewQzhJGiUOz7jB1MXJwsAlYSHT/0wYxRQRCJRat 1AbpFRZwkLh3aCoziC0i4CgxZ+tyJgjbTWLKiZdgcRYBVYktC/vB4rwCvhKflu9hgRi/gVHi 5bqtbCAJTgFdiY7/x8AaGIEO+n5qDVgDs4C4xK0n85kgDhWQWLLnPDOELSrx8vE/VoiafInl qxpZIBYISpyc+YRlAqPwLCTts5CUzUJSBhE3kPjy/jaUrS2xbOFrZghbX6L7/WkmZPEFjOyr GNlzEzNz0ssNNzECY+Tglt+6OxhPnRM5xCjNwaIkzvvhrXOQkEB6YklqdmpqQWpRfFFpTmrx IUYmDk6pBsYpdxvOK8R5LDiyUKOxqmDRqv68LXzP2R6pxR2YxxDfNSHX1jlkYs6ee5ujQroS r3KLbbLe9af/1RoBlw3HHSzyusW8sgMrijQFbvFnNRswqa9Xr6hQ2ZQyqS7yf3/AJIma7OrH OtfbOf98uSBZqT9Nw1b1wZmkCckt/77O55LO59I2Kju2Q4mlOCPRUIu5qDgRALbkehRfAgAA
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 08:19:08 -0000


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?



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.