IETF Logo Mail Archive

Re: [rtcweb] New Version Notification for draft-jesup-rtcweb-data-01.txt

Wolfgang Beck <wolfgang.beck01@googlemail.com> Mon, 14 November 2011 09:35 UTC

Return-Path: <wolfgang.beck01@googlemail.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 AD85E21F8F0C for <rtcweb@ietfa.amsl.com>; Mon, 14 Nov 2011 01:35:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.934
X-Spam-Level:
X-Spam-Status: No, score=-2.934 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uKkfFS5dHeIz for <rtcweb@ietfa.amsl.com>; Mon, 14 Nov 2011 01:35:13 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5BEAF21F8F10 for <rtcweb@ietf.org>; Mon, 14 Nov 2011 01:35:11 -0800 (PST)
Received: by ggnr5 with SMTP id r5so742755ggn.31 for <rtcweb@ietf.org>; Mon, 14 Nov 2011 01:35:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=iTu5Y+WeeRmLTYbxV/uhINl8mE/WIeTaqFP2ASrVUrQ=; b=d92nUc5RG+QY1B3fiN5ZQAtEaToZ5SlrwK7DTV1jdKdq9eDOSXKiBx80u9X0TNbGPW W2MO5CP+NH9rLmNbV7TIF4hrAQ0njRBYE9kwicwHleDYvIno2nG9UInVLgTwM+LS3E8W xZY7o+zGBPTQaxifX+LougjWQg/fO0qtbMOco=
MIME-Version: 1.0
Received: by 10.68.38.169 with SMTP id h9mr48431617pbk.113.1321263310651; Mon, 14 Nov 2011 01:35:10 -0800 (PST)
Received: by 10.68.64.66 with HTTP; Mon, 14 Nov 2011 01:35:10 -0800 (PST)
In-Reply-To: <4EAF64FF.8020101@jesup.org>
References: <20111031211134.8188.49554.idtracker@ietfa.amsl.com> <4EAF64FF.8020101@jesup.org>
Date: Mon, 14 Nov 2011 17:35:10 +0800
Message-ID: <CAAJUQMhCHHWqeUSKdn4SAS67ohF1y_QxCbc9KcgeybAe7N-5-w@mail.gmail.com>
From: Wolfgang Beck <wolfgang.beck01@googlemail.com>
To: Randell Jesup <randell-ietf@jesup.org>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] New Version Notification for draft-jesup-rtcweb-data-01.txt
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, 14 Nov 2011 09:35:19 -0000

Is rtcweb-data protocol only usable if both browsers use the same JS
client? If not, how is the content of the data stream -- the 'codec'
-- negotiated between the different JS clients? ROAP will not work as
it is the JS clients which writes to the data stream. The ROAP
component of the browser doesn't know what's in there.

rtcweb-data will only work across different servers if you have
standardized the datastream's content.

However, if we dropped the server-to-server interworking requirement,
rtcweb-data would be a good base for exciting applications.


Wolfgang Beck

v2.23.0 | Report a Bug | By Email