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

Justin Uberti <juberti@google.com> Mon, 14 November 2011 12:09 UTC

Return-Path: <juberti@google.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 9353721F8F29 for <rtcweb@ietfa.amsl.com>; Mon, 14 Nov 2011 04:09:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.92
X-Spam-Level:
X-Spam-Status: No, score=-102.92 tagged_above=-999 required=5 tests=[AWL=0.056, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 ZKuaw1R65XK7 for <rtcweb@ietfa.amsl.com>; Mon, 14 Nov 2011 04:09:58 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 376CF21F8F26 for <rtcweb@ietf.org>; Mon, 14 Nov 2011 04:09:58 -0800 (PST)
Received: by iaeo4 with SMTP id o4so9254473iae.31 for <rtcweb@ietf.org>; Mon, 14 Nov 2011 04:09:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-system-of-record; bh=MI+3W9pru/reflJYDNlX3/IORKff8p6y7kanJu286Mo=; b=Fhv7We+N9Yd11lIQBck+dIBqMk46Gypnvmc0mv+Wmr4Q4ECaiWsDV9V0b8j7NqkPUD wHY+LVQlAZXvm3XOffLQ==
Received: by 10.231.28.106 with SMTP id l42mr5212661ibc.66.1321272597732; Mon, 14 Nov 2011 04:09:57 -0800 (PST)
MIME-Version: 1.0
Received: by 10.231.28.106 with SMTP id l42mr5212655ibc.66.1321272597578; Mon, 14 Nov 2011 04:09:57 -0800 (PST)
Received: by 10.231.194.134 with HTTP; Mon, 14 Nov 2011 04:09:57 -0800 (PST)
Received: by 10.231.194.134 with HTTP; Mon, 14 Nov 2011 04:09:57 -0800 (PST)
In-Reply-To: <CAAJUQMiyit3QvYJ3piuX26r4T5KtwLwWHX3NaC1wWL-zzeRftA@mail.gmail.com>
References: <20111031211134.8188.49554.idtracker@ietfa.amsl.com> <4EAF64FF.8020101@jesup.org> <CAAJUQMhCHHWqeUSKdn4SAS67ohF1y_QxCbc9KcgeybAe7N-5-w@mail.gmail.com> <CAOJ7v-3-2ZL5fvsXxGiwjAh3TKe__PGdU+Aw0cR-fGqzT6Ht9g@mail.gmail.com> <CAAJUQMiyit3QvYJ3piuX26r4T5KtwLwWHX3NaC1wWL-zzeRftA@mail.gmail.com>
Date: Mon, 14 Nov 2011 07:09:57 -0500
Message-ID: <CAOJ7v-3znXLq1YPJzMyekC1PAU3nF=Ctt82z7+gZqUPpJY3+JQ@mail.gmail.com>
From: Justin Uberti <juberti@google.com>
To: Wolfgang Beck <wolfgang.beck01@googlemail.com>
Content-Type: multipart/alternative; boundary=001517740adcd4842204b1b0bfac
X-System-Of-Record: true
Cc: Randell Jesup <randell-ietf@jesup.org>, "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 12:09:59 -0000

Not sure what you mean. The wire protocol is standardized, but applications
can send whatever they want over it.
On Nov 14, 2011 7:20 PM, "Wolfgang Beck" <wolfgang.beck01@googlemail.com>
wrote:

> On Mon, Nov 14, 2011 at 6:42 PM, Justin Uberti <juberti@google.com> wrote:
> > On Mon, Nov 14, 2011 at 4:35 AM, Wolfgang Beck
> > <wolfgang.beck01@googlemail.com> wrote:
> >> 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.
> >
> > The format of the data stream will be standardized.
>
> Now it gets interesting: who is responsible for the rtcweb-data content?
>
> if it is the browser:
> - every new application will have to be standardized.
> - for every new application, the browser has to be updated.
> ***whether we do server-to-server or not***
>
> It basically means every rtcweb-data application needs to get the
> approval of Firefox, Google, and Microsoft.
>
> If it is the JS client:
> - the JS client has to handle Offer/Answer. The browser doesn't know
> enough about the content to do this.
>
>
> Wolfgang Beck
>