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

Hadriel Kaplan <HKaplan@acmepacket.com> Fri, 21 October 2011 17:37 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 469F01F0C91 for <rtcweb@ietfa.amsl.com>; Fri, 21 Oct 2011 10:37:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.273
X-Spam-Level:
X-Spam-Status: No, score=-2.273 tagged_above=-999 required=5 tests=[AWL=0.026, 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 own0V7YkaF9u for <rtcweb@ietfa.amsl.com>; Fri, 21 Oct 2011 10:37:08 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by ietfa.amsl.com (Postfix) with ESMTP id AB2131F0C8C for <rtcweb@ietf.org>; Fri, 21 Oct 2011 10:37:08 -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 13:37:06 -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 13:37:07 -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: AQHMkBgN2/kP8vYgo0SdE44T6C8DAQ==
Date: Fri, 21 Oct 2011 17:37:05 +0000
Message-ID: <A45E8A74-0D40-408F-A21D-6D94AC16676A@acmepacket.com>
References: <CALiegf=gbZJgvCEy83FuS4GJ+6O-kU4MBXdPEgdz4ubSt5Y4pw@mail.gmail.com> <F6C22392-95FE-4CB2-836A-5DF1B5143F8B@acmepacket.com> <CALiegfnTJVJTnNy-V_UrQtzAptQ1LUhCyaZFvsAr-L39ePBFGw@mail.gmail.com>
In-Reply-To: <CALiegfnTJVJTnNy-V_UrQtzAptQ1LUhCyaZFvsAr-L39ePBFGw@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: <DDF92C59A2234F418DC4BDA38C6DE053@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 17:37:09 -0000

You know, doing that would be awesome because then you could test it against real SIP devices, or even at Sipit, to verify we've got the legacy-SIP-compatibility-model right for more esoteric cases.

-hadriel

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

> 2011/10/21 Hadriel Kaplan <HKaplan@acmepacket.com>:
>> 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)
> 
> The question comes because my wire signaling implementation (SIP over
> WebSocket) is that: SIP. So the JS sends and receives pure SIP
> messages (with SDP) over the wire.
> 
> If ROAP includes a real SDP (as the draft currently states) then I'm
> done as I just need to create a ROAP object (in JavaScript) and pass
> it the received SDP string (and also set some session status
> variables, which can be easily mapped from the received SIP
> request/response).
> 
> Hope I'm right and I don't have to drop the work of long months.
> 
> Regards.
> 
> -- 
> Iñaki Baz Castillo
> <ibc@aliax.net>