Re: [rtcweb] ROAP Example Application

Tim Panton <> Fri, 21 October 2011 11:13 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 957A621F8AFD for <>; Fri, 21 Oct 2011 04:13:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.579
X-Spam-Status: No, score=-2.579 tagged_above=-999 required=5 tests=[AWL=0.020, BAYES_00=-2.599]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id CN4hfpvKWb9E for <>; Fri, 21 Oct 2011 04:13:27 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id EC05521F891D for <>; Fri, 21 Oct 2011 04:13:26 -0700 (PDT)
Received: from [] (unknown []) by (Postfix) with ESMTP id 07E4337A902; Fri, 21 Oct 2011 12:26:12 +0100 (BST)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset="us-ascii"
From: Tim Panton <>
In-Reply-To: <>
Date: Fri, 21 Oct 2011 12:13:20 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <>
To: Harald Alvestrand <>
X-Mailer: Apple Mail (2.1251.1)
Subject: Re: [rtcweb] ROAP Example Application
X-Mailman-Version: 2.1.12
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: Fri, 21 Oct 2011 11:13:27 -0000

On 21 Oct 2011, at 12:00, Harald Alvestrand wrote:

> As I've noted before, they are more entangled than one might like them to be; if we don't support the extension to use a single RTP session, we don't know how many ICE sessions we need to set up until we know at least how many top level media types we want to support. If we want to support multiple RTP sessions for other reasons, we need similar control of the number of ICE sessions set up.

Who is 'we' ? Surely the decision of how many top level media types to support _must_ be taken at the 
application layer. The application has to make screen real-estate available for things like video, keypads etc.

> It illustrates that while a lot of the concerns of codecs and ICE sessions are reasonably separate, the functions that manipulate RTP sessions need access to both.

And in my view the javascript needs access to _all_ 3 of them.