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

Harald Alvestrand <harald@alvestrand.no> Thu, 20 February 2014 00:22 UTC

Return-Path: <harald@alvestrand.no>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F2B71A05D2 for <rtcweb@ietfa.amsl.com>; Wed, 19 Feb 2014 16:22:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.466
X-Spam-Level:
X-Spam-Status: No, score=-1.466 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_FONT_FACE_BAD=0.981, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 37zDtcFPxqLp for <rtcweb@ietfa.amsl.com>; Wed, 19 Feb 2014 16:22:47 -0800 (PST)
Received: from mork.alvestrand.no (mork.alvestrand.no [158.38.152.117]) by ietfa.amsl.com (Postfix) with ESMTP id D86821A0538 for <rtcweb@ietf.org>; Wed, 19 Feb 2014 16:22:46 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id 9067C7C4E79; Thu, 20 Feb 2014 01:22:42 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at alvestrand.no
Received: from mork.alvestrand.no ([127.0.0.1]) by localhost (mork.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FP-t5Wf3R8c8; Thu, 20 Feb 2014 01:22:41 +0100 (CET)
Received: from [172.19.7.58] (unknown [216.239.45.90]) by mork.alvestrand.no (Postfix) with ESMTPSA id 293887C4DB5; Thu, 20 Feb 2014 01:22:40 +0100 (CET)
Message-ID: <53054ACF.6030601@alvestrand.no>
Date: Thu, 20 Feb 2014 01:22:39 +0100
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>
References: <52FDC17E.8070708@alvestrand.no>, <52FE5B37.80409@alvestrand.no> <7594FB04B1934943A5C02806D1A2204B1D1735EE@ESESSMB209.ericsson.se>, <5303EE53.1010405@alvestrand.no> <7594FB04B1934943A5C02806D1A2204B1D1A9B80@ESESSMB209.ericsson.se>, <5304F413.1080208@alvestrand.no> <pi22myx9puvcw80lbn1s1ktu.1392843033581@email.android.com>
In-Reply-To: <pi22myx9puvcw80lbn1s1ktu.1392843033581@email.android.com>
X-Enigmail-Version: 1.6
Content-Type: multipart/alternative; boundary="------------030909010605010002060504"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/LB1ib24f9xaZQzUGC6wzpEh3RL8
Subject: Re: [rtcweb] Stream control: [MMUSIC] msid-04 submitted
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Feb 2014 00:22:51 -0000

On 02/19/2014 09:50 PM, Christer Holmberg wrote:
> Hi,
>
> If the indication is NOT permanent, can't we use the existing direction attributes (sendrecv, sendonly etc)?

We could - but how would we then indicate "permanent"?

Omitting the direction attribute means the same as "sendrecv", if I'm
not mistaken. So you can't have meant omitting that.

So what were you suggesting?


> Regards,
>
> Christer
>
> Sent from my Sony Ericsson Xperia arc S
>
> Harald Alvestrand <harald@alvestrand.no> wrote:
>
> On 02/19/2014 09:19 AM, Christer Holmberg wrote:
>> Hi,
>>
>> 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?
>
>
>>
>> Regards,
>>
>> Christer
>>
>> Sent from Windows Mail
>>
>> *From:* 'Harald Alvestrand' <mailto:harald@alvestrand.no>
>> *Sent:* ‎Wednesday‎, ‎February‎ ‎19‎, ‎2014 ‎1‎:‎35‎ ‎AM
>> *To:* Hans-Christer Holmberg <mailto:christer.holmberg@ericsson.com>,
>> rtcweb@ietf.org <mailto:rtcweb@ietf.org>
>>
>> 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
>> mechanism.
>> 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.
>>
>>           Harald
>>
>
>
> -- 
> Surveillance is pervasive. Go Dark.


-- 
Surveillance is pervasive. Go Dark.