Re: [MMUSIC] [rtcweb] Quick comments on draft-roach-rtcweb-glareless-add-00

Paul Kyzivat <> Fri, 10 May 2013 21:20 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 5DBA621F9343 for <>; Fri, 10 May 2013 14:20:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 0.052
X-Spam-Status: No, score=0.052 tagged_above=-999 required=5 tests=[AWL=0.189, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, MIME_8BIT_HEADER=0.3, RDNS_NONE=0.1]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id TmCJjgzgz8qc for <>; Fri, 10 May 2013 14:20:04 -0700 (PDT)
Received: from ( [IPv6:2001:558:fe14:44:76:96:59:243]) by (Postfix) with ESMTP id 4D86021F90BB for <>; Fri, 10 May 2013 14:20:04 -0700 (PDT)
Received: from ([]) by with comcast id aLGy1l00216LCl05DML39H; Fri, 10 May 2013 21:20:03 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([]) by with comcast id aML31l00p3ZTu2S3SML36P; Fri, 10 May 2013 21:20:03 +0000
Message-ID: <>
Date: Fri, 10 May 2013 17:20:02 -0400
From: Paul Kyzivat <>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: =?ISO-8859-1?Q?Stefan_H=E5kansson_LK?= <>
References: <> <> <> <> <>
In-Reply-To: <>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=q20121106; t=1368220803; bh=FT8XmLPiOWIV4si8k3wBZVTlF0Bco3cgaGat0HWENTg=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=hIcGmXzc/BgRIaApuI91dME/+pAQd3vkLAMevivcuYBk/hS5sb/+nMnnZxAn24s8F yla7fAOIaAQSEunhaQFQgevTK9eZcP3dra66fqfRoqIiO9Kvh2kQeymnJYROX9Bss5 QNkvup5R2ygXCfPJ2d6XcpENc1erJi2Z2+sPWqM9+aIDCVEwGz6sQ5byZwc1I31MQ5 CnCgMjdxvgTut9DeGWOWg+xpW/eY373/+eUwbA0MYiwliSsel1Z3q8zxheGEmduBjb DBNyv2C0bYfWkviBOUVuogUgSoa65H9x7vbwb+Zp7RBtTsa7rN/T0Ag/NqvTkqRquF eyJRwYiyd1ahg==
Cc: "" <>, "" <>
Subject: Re: [MMUSIC] [rtcweb] Quick comments on draft-roach-rtcweb-glareless-add-00
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: Fri, 10 May 2013 21:20:10 -0000

On 5/10/13 2:37 AM, Stefan Håkansson LK wrote:
> But I can easily think of other situations that would lead to glare for
> Plan A.
> Just as an example, think about a conference scenario with a centralized
> node. Now, one of the participants wants to mute her/his audio, and as a
> result the audio m-line would go from sendrecv to recvonly. At roughly
> the same time the server wants to disable the high res video and enable
> the low res video (because this user will be moved, based e.g. on the
> recent audio activity, from being displayed in the main video window to
> be in a thumbnail on the screen of the other participants in the
> conference), so it wants to manipulate the direction attribute of other
> m-lines.
> So there would be two offers sent at roughly the same time, which means
> we would have glare.

What do you mean by "roughly"?

How long does it take to do an O/A exchange that doesn't require human 
input? Presumably less than a second, maybe considerably less. (Or will 
it be more with RTCWEB and web servers in the path?)

What is the probability that the other side, for independent reasons, 
decides to make a change within that interval? (And it isn't really the 
whole interval - it is only the first part of it.)

There may indeed be realistic cases for glare, but they will probably be 
because both changes are keyed to a common event.