Re: [rtcweb] Does ROAP mandate the on-the-wire format?

Hadriel Kaplan <HKaplan@acmepacket.com> Fri, 21 October 2011 16:39 UTC

Return-Path: <HKaplan@acmepacket.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 9ED391F0C6F for <rtcweb@ietfa.amsl.com>; Fri, 21 Oct 2011 09:39:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.272
X-Spam-Level:
X-Spam-Status: No, score=-2.272 tagged_above=-999 required=5 tests=[AWL=0.027, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 pxbRCavGttis for <rtcweb@ietfa.amsl.com>; Fri, 21 Oct 2011 09:39:28 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by ietfa.amsl.com (Postfix) with ESMTP id 0194C1F0C6D for <rtcweb@ietf.org>; Fri, 21 Oct 2011 09:39:28 -0700 (PDT)
Received: from MAIL2.acmepacket.com (10.0.0.22) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.2.254.0; Fri, 21 Oct 2011 12:39:26 -0400
Received: from MAIL1.acmepacket.com ([169.254.1.230]) by Mail2.acmepacket.com ([169.254.2.157]) with mapi id 14.01.0270.001; Fri, 21 Oct 2011 12:39:27 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Iñaki Baz Castillo <ibc@aliax.net>
Thread-Topic: [rtcweb] Does ROAP mandate the on-the-wire format?
Thread-Index: AQHMkA//9B+N9mef2kyVTdnWzyP1pg==
Date: Fri, 21 Oct 2011 16:39:26 +0000
Message-ID: <F6C22392-95FE-4CB2-836A-5DF1B5143F8B@acmepacket.com>
References: <CALiegf=gbZJgvCEy83FuS4GJ+6O-kU4MBXdPEgdz4ubSt5Y4pw@mail.gmail.com>
In-Reply-To: <CALiegf=gbZJgvCEy83FuS4GJ+6O-kU4MBXdPEgdz4ubSt5Y4pw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [216.41.24.34]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <B58B5A1115899246A8E4A095AD186836@acmepacket.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAQAAAWE=
Cc: "<rtcweb@ietf.org>" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Does ROAP mandate the on-the-wire format?
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: Fri, 21 Oct 2011 16:39:28 -0000

On Oct 21, 2011, at 12:25 PM, Iñaki Baz Castillo wrote:

> Hi, I'm a bit afraid after listeing/reading this phrase in the conf:
> 
> -----------------
> Cullen:  I will clarify ROAP is over-the-wire protocol, add
> termination, and do some other clarifications, then re-issue.
> -----------------
> 
> I expect that ROAP does NOT mandate the format of the messages
> exchanged on-the-wire, but just the communication between the JS
> custom code and the RTCweb stack in the browser, am I right? say "yes"
> please.
> What I understand (or want to understand) is that any custom RTCweb
> on-the-wire protocol must satisfy ROAP requirements in some way, so
> when the JavaScript receives some kind of custom message it can
> interpret it and convert into the appropriate ROAP request, and then
> make a ROAP call to the browser via the RTCweb API. Am I right?

Well since the Browser will never know whether ROAP is really to another Browser vs. the Javascript, then yes it could be used that way. (it will probably be painful, but possible)

-hadriel