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

Iñaki Baz Castillo <ibc@aliax.net> Fri, 21 October 2011 16:25 UTC

Return-Path: <ibc@aliax.net>
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 08A6D21F86DD for <rtcweb@ietfa.amsl.com>; Fri, 21 Oct 2011 09:25:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.632
X-Spam-Level:
X-Spam-Status: No, score=-2.632 tagged_above=-999 required=5 tests=[AWL=0.045, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, 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 LHpRLuiBs6MC for <rtcweb@ietfa.amsl.com>; Fri, 21 Oct 2011 09:25:45 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id C61FD21F86C1 for <rtcweb@ietf.org>; Fri, 21 Oct 2011 09:25:43 -0700 (PDT)
Received: by vcbfo1 with SMTP id fo1so4193764vcb.31 for <rtcweb@ietf.org>; Fri, 21 Oct 2011 09:25:43 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.115.77 with SMTP id h13mr563185vcq.111.1319214343307; Fri, 21 Oct 2011 09:25:43 -0700 (PDT)
Received: by 10.220.118.143 with HTTP; Fri, 21 Oct 2011 09:25:43 -0700 (PDT)
Date: Fri, 21 Oct 2011 18:25:43 +0200
Message-ID: <CALiegf=gbZJgvCEy83FuS4GJ+6O-kU4MBXdPEgdz4ubSt5Y4pw@mail.gmail.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
To: rtcweb@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: [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:25:48 -0000

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?

Thanks.

-- 
Iñaki Baz Castillo
<ibc@aliax.net>