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

Wolfgang Beck <wolfgang.beck01@googlemail.com> Mon, 14 November 2011 13:10 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 197EA11E82C0 for <rtcweb@ietfa.amsl.com>; Mon, 14 Nov 2011 05:10:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.938
X-Spam-Level:
X-Spam-Status: No, score=-2.938 tagged_above=-999 required=5 tests=[AWL=0.039, 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 BpajcazQ2dMD for <rtcweb@ietfa.amsl.com>; Mon, 14 Nov 2011 05:10:45 -0800 (PST)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7FADC21F8B83 for <rtcweb@ietf.org>; Mon, 14 Nov 2011 05:10:45 -0800 (PST)
Received: by gye5 with SMTP id 5so5889117gye.31 for <rtcweb@ietf.org>; Mon, 14 Nov 2011 05:10:41 -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=HPSTYnu41culZv9Sjh3CkiOIUkYxF2S03bOPAHgZRIA=; b=OKrgX9/8e5+hD1WYm2qD5Gd2WFY+vH7Z1hA6JHiiFCqzNosnK/aBXVzM7cSlW0giPj vO1inumvYCxo67eV5PmenRsoQ4olVcY6rdw3xGmPvBRbOQAuVlK2efQIfYhjEb3E6KJ2 xd0cQ+lky/7DlXJ30yzI+kJjcnJRxKzPDVoJk=
MIME-Version: 1.0
Received: by 10.68.29.37 with SMTP id g5mr30645875pbh.79.1321276241220; Mon, 14 Nov 2011 05:10:41 -0800 (PST)
Received: by 10.68.64.66 with HTTP; Mon, 14 Nov 2011 05:10:41 -0800 (PST)
In-Reply-To: <5D21A34A-5C6C-4BFD-A7AD-5B8AB0C36223@acmepacket.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> <5D21A34A-5C6C-4BFD-A7AD-5B8AB0C36223@acmepacket.com>
Date: Mon, 14 Nov 2011 14:10:41 +0100
Message-ID: <CAAJUQMit9G_3Vmoe0vKz2Lsj51DRJvHQXSQWVh7WsmFEJ0nH4g@mail.gmail.com>
From: Wolfgang Beck <wolfgang.beck01@googlemail.com>
To: Hadriel Kaplan <HKaplan@acmepacket.com>
Content-Type: text/plain; charset=ISO-8859-1
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 13:10:46 -0000

On Mon, Nov 14, 2011 at 1:29 PM, Hadriel Kaplan <HKaplan@acmepacket.com>; wrote:
>
> No only the psuedo-transport layer is being standardized - i.e., SCTP/DTLS/UDP.

That's what I hoped to hear.

> What goes on top of that (i.e., what the JS actually communicates) would be whatever the JS wants and thus yes of
> course it would only truly "work" if the same JS was used on both peers or someone went and defined some specific
> application protocols for it.  That might actually happen - like if someone went and defined an IM protocol to run on the
> data-channel they could create a spec for it for other web-apps to be able to interoperate.  (or a JS library doing
> something over the data channel could become so popular as to be a defacto spec for one)

In this case, the different JS clients will have to negotiate this
protocol. In the current ROAP model, this is done by the browser, not
the JS client. It will probably get ugly if I want to negotiate a
combined rtcweb-data and A/V session.

Thanks for the clarification.


Wolfgang Beck