Re: [rtcweb] Media neg-eo-tiation and signalling archa-tecture

Harald Alvestrand <harald@alvestrand.no> Mon, 11 July 2011 13:44 UTC

Return-Path: <harald@alvestrand.no>
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 DFAB421F8BD1 for <rtcweb@ietfa.amsl.com>; Mon, 11 Jul 2011 06:44:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 4bxxYoy3RnZC for <rtcweb@ietfa.amsl.com>; Mon, 11 Jul 2011 06:44:02 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 2B28621F8BD2 for <rtcweb@ietf.org>; Mon, 11 Jul 2011 06:44:02 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id F02D539E179 for <rtcweb@ietf.org>; Mon, 11 Jul 2011 15:42:53 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XNngq59xPltX for <rtcweb@ietf.org>; Mon, 11 Jul 2011 15:42:53 +0200 (CEST)
Received: from [192.168.1.53] (162.80-203-220.nextgentel.com [80.203.220.162]) by eikenes.alvestrand.no (Postfix) with ESMTPS id 5131939E087 for <rtcweb@ietf.org>; Mon, 11 Jul 2011 15:42:53 +0200 (CEST)
Message-ID: <4E1AFE2C.4080201@alvestrand.no>
Date: Mon, 11 Jul 2011 15:44:12 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110424 Thunderbird/3.1.10
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <BLU152-w2EFC2C55649AF1665D96A935E0@phx.gbl> <DFCE8D1D-AC5F-455A-B45D-C09DB6F7D5F8@cisco.com>
In-Reply-To: <DFCE8D1D-AC5F-455A-B45D-C09DB6F7D5F8@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [rtcweb] Media neg-eo-tiation and signalling archa-tecture
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: Mon, 11 Jul 2011 13:44:03 -0000

On 07/07/11 05:43, Cullen Jennings wrote:
> On Jul 6, 2011, at 12:06 AM, Bernard Aboba wrote:
>
>>
>> * The last slide now says that WhatWG proposal is low path; this is not true. The WhatWG proposal as I read it is mute on how the SDPs are exchanged, it just hands those SDPs over to the
>>
>> application (though high path is indicated: "Communications are coordinated via a signaling channel provided by script in the page via the server, e.g. using XMLHttpRequest.")
> Hmm - my understanding was only the ICE related information was communicated that way and the SDP related information when across the channel set up by ICE but I could be totally wrong. It's pretty vague in the spec - I got that idea by talking to some of the people involved. Anyways, glad to retract that WhatWG is doing low path and just change it to not clear.
Google's current implementation of the WhatWG spec is "high path". If 
you dump the requests that the example client programs pass to the 
mediation server (which is talking fairly normal HTTP), you will see the 
JSON objects that contain the codec negotiation information.

>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>