Re: [rtcweb] draft-sipdoc-rtcweb-open-wire-protocol-00 (Open In-The-Wire Protocol for RTC-Web)

Iñaki Baz Castillo <ibc@aliax.net> Thu, 27 October 2011 17:46 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 83BEF21F8672 for <rtcweb@ietfa.amsl.com>; Thu, 27 Oct 2011 10:46:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.641
X-Spam-Level:
X-Spam-Status: No, score=-2.641 tagged_above=-999 required=5 tests=[AWL=0.036, 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 28n9p4bpw8K7 for <rtcweb@ietfa.amsl.com>; Thu, 27 Oct 2011 10:46:25 -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 B80C921F8573 for <rtcweb@ietf.org>; Thu, 27 Oct 2011 10:46:25 -0700 (PDT)
Received: by vcbfo1 with SMTP id fo1so3228923vcb.31 for <rtcweb@ietf.org>; Thu, 27 Oct 2011 10:46:25 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.175.134 with SMTP id ba6mr494036vcb.61.1319737585258; Thu, 27 Oct 2011 10:46:25 -0700 (PDT)
Received: by 10.220.159.134 with HTTP; Thu, 27 Oct 2011 10:46:25 -0700 (PDT)
In-Reply-To: <BB3BBF12-76E5-4D6F-A2B8-836CEFF6EDDB@westhawk.co.uk>
References: <CALiegfmvWWMf6dSikgfZqnSPuN-6UZKwAMfKu9HP2uqJxHMVCQ@mail.gmail.com> <CALiegfmFE0zhBg6aZMtRMO5q-k6_jeHAn9q2XivNw8yjNVqyag@mail.gmail.com> <BB3BBF12-76E5-4D6F-A2B8-836CEFF6EDDB@westhawk.co.uk>
Date: Thu, 27 Oct 2011 19:46:25 +0200
Message-ID: <CALiegf=PcA67RC==vDvvSwaDxixa0TeoKa=BFu3np4Xs17VJrQ@mail.gmail.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
To: Tim Panton <thp@westhawk.co.uk>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] draft-sipdoc-rtcweb-open-wire-protocol-00 (Open In-The-Wire Protocol for RTC-Web)
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: Thu, 27 Oct 2011 17:46:26 -0000

2011/10/27 Tim Panton <thp@westhawk.co.uk>:
> Thank you for writing this up - before I had to ;-)
> I agree with almost all of it, but I wonder if you could add a derived requirement:
> "  4.  It MUST be possible for a website developer to make his RTC-Web
>       scenario to interoperate with a pure SIP or XMPP/Jingle network
>       without requiring a signaling protocol gateway (by using SIP over
>       WebSocket [I-D.ibc-rtcweb-sip-websocket] or XMPP over WebSocket
>       [I-D.moffitt-xmpp-over-websocket]).
>  5. It must be possible for a website developer to make his RTC-Web
>       scenario to interoperate without adding new infrastructure unless they wish to
>       interop with the wider world - i.e. if the
>       mysite.com example wished to operate as an 'island' they
>       would not need to add additional telephony or expertise
>       servers, as all the neccessary server side work could be done in php
>       by his existing web programmers.  "
>
> I think this is implied by your document, but I feel it is critically important
> so worth explicitly stating it.

Good point. IMHO it's not needed (I hope) to update the draft as I
think we all agree on the conclusions in it (including your new point
5). If not, I'll add it in a new revision.


Thanks a lot.

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