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

Iñaki Baz Castillo <ibc@aliax.net> Fri, 21 October 2011 18:04 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 5C6551F0C91 for <rtcweb@ietfa.amsl.com>; Fri, 21 Oct 2011 11:04:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.633
X-Spam-Level:
X-Spam-Status: No, score=-2.633 tagged_above=-999 required=5 tests=[AWL=0.044, 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 cMiwAjjLOSfB for <rtcweb@ietfa.amsl.com>; Fri, 21 Oct 2011 11:04:55 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id B23301F0C8C for <rtcweb@ietf.org>; Fri, 21 Oct 2011 11:04:55 -0700 (PDT)
Received: by vws5 with SMTP id 5so3806144vws.31 for <rtcweb@ietf.org>; Fri, 21 Oct 2011 11:04:55 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.25.75 with SMTP id a11mr15269628vdg.1.1319220294919; Fri, 21 Oct 2011 11:04:54 -0700 (PDT)
Received: by 10.220.118.143 with HTTP; Fri, 21 Oct 2011 11:04:54 -0700 (PDT)
In-Reply-To: <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> <A45E8A74-0D40-408F-A21D-6D94AC16676A@acmepacket.com>
Date: Fri, 21 Oct 2011 20:04:54 +0200
Message-ID: <CALiegfms++kpSvKRoq+VdbRL0Gmjj2hMf4yXEiGg1BdxYJNmHw@mail.gmail.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
To: Hadriel Kaplan <HKaplan@acmepacket.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
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 18:04:56 -0000

2011/10/21 Hadriel Kaplan <HKaplan@acmepacket.com>:
> 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.

Oh, I already test it against real SIP devices. Even better, I can
test SIP devices against my (our) much better SIP implementation :)

http://www.youtube.com/watch?v=qfFlK1KyF6Q

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