Re: [rtcweb] To multiplex or not!

Cullen Jennings <fluffy@cisco.com> Wed, 20 July 2011 14:40 UTC

Return-Path: <fluffy@cisco.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2A3E21F8A70 for <rtcweb@ietfa.amsl.com>; Wed, 20 Jul 2011 07:40:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.862
X-Spam-Level:
X-Spam-Status: No, score=-103.862 tagged_above=-999 required=5 tests=[AWL=-1.263, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C7XLQ45-Iqaq for <rtcweb@ietfa.amsl.com>; Wed, 20 Jul 2011 07:40:08 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 5F5EE21F85F5 for <rtcweb@ietf.org>; Wed, 20 Jul 2011 07:40:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fluffy@cisco.com; l=1790; q=dns/txt; s=iport; t=1311172808; x=1312382408; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=U+NA90Acvx5Y2N6tRhR5X565y8iAKdx/H9XXzoSjRr8=; b=SDQZ0vGmgssnefjFLSD3jhu0/NqFeVcT/KLi55xk5NLmAxeksHGG5eKC uws5tCkN9XOeePCXtiUIkXKvzW5lDTMmrtSIt0onuN0jnA2OiyaNDr6Dr s8Mabf/5O9y6eLEd7IOvfkD2DRcOk/iIY64LMck2hcp5okwDuEngmVcHs 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAKznJk6rRDoJ/2dsb2JhbABTp2N3iHyhdJ4uhV5fBIdVixmFB4t2
X-IronPort-AV: E=Sophos;i="4.67,235,1309737600"; d="scan'208";a="4740304"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by rcdn-iport-4.cisco.com with ESMTP; 20 Jul 2011 14:40:07 +0000
Received: from [10.21.74.120] ([10.21.74.120]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p6KEe6TA003050; Wed, 20 Jul 2011 14:40:07 GMT
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <BLU152-W38359A17A67825B59CD5D0934C0@phx.gbl>
Date: Wed, 20 Jul 2011 07:40:06 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <FDD88998-B6E9-4C35-ABF1-571485CB6BA4@cisco.com>
References: <4E259484.20509@ericsson.com>, <37897D97-85A9-4B21-85C3-A7E9BE1EF3E7@cisco.com>, <4E26B742.6050606@jitsi.org>, <62C71813-83B4-44D3-8E54-28262311CDB3@cisco.com> <BLU152-W38359A17A67825B59CD5D0934C0@phx.gbl>
To: Bernard Aboba <bernard_aboba@hotmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] To multiplex or not!
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
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: Wed, 20 Jul 2011 14:40:12 -0000

On Jul 20, 2011, at 7:24 , Bernard Aboba wrote:

> 
> > Ahh, I think we have come to the key issues here - perhaps I have not been explaining myself very well. So in your experience roughly how long does it take to set up a for two scenarios using ICE as is today. 
> > 
> > First scenario: I have two devices that want to set up a single audio stream and they each have the candidates from: local v4 IP address, v4 stun, v4 turn, local v6, turn v6. Obviously they could have a lot more but that seems like a reasonable starting point. 
> > 
> > Second scenario: same as first address wise but instead of a single audio stream they want to set up a single audio stream to a conference bridge plus 7 video streams for the video from the 5 people on the bridge plus a presentation stream and stream of video from active speaker. I don't really care much about the scenario other than there are 8 streams being set up. But this type of scenario is becoming very common for multi party video chat as it allows you to see perhaps small versions of everyone plus a large version of active speaker. 
> > 
> > My experience is the answer to the first scenario is not as quick as you would like and the answer to how long the second takes is about 8 times longer than the first one. You might do a bit better than that depending on how clever your implementation is but it still a lot longer. 
> 
> [BA] Yes, that is correct.  However at the moment I'd characterize that as a "high quality problem", since it isn't even clear that the current WHATWG API can handle that case, due to glare and ICE timing issues.  

Agree - but I think we need to fix that regardless of what we decide with this.