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

Cullen Jennings <fluffy@cisco.com> Tue, 08 November 2011 23:05 UTC

Return-Path: <fluffy@cisco.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 D3B3D11E80AD for <rtcweb@ietfa.amsl.com>; Tue, 8 Nov 2011 15:05:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.442
X-Spam-Level:
X-Spam-Status: No, score=-106.442 tagged_above=-999 required=5 tests=[AWL=0.157, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 Rs3NyzrjMHw1 for <rtcweb@ietfa.amsl.com>; Tue, 8 Nov 2011 15:05:26 -0800 (PST)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id 5ECD411E80A3 for <rtcweb@ietf.org>; Tue, 8 Nov 2011 15:05:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fluffy@cisco.com; l=934; q=dns/txt; s=iport; t=1320793526; x=1322003126; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=79E0WG3qe4ANQ44Wm0TByGsCC5fH6QDzguzWYl2jw1o=; b=kIPKUAB6em/WNGyVArjelNyFewm9tGGtjCxD7+s1Pexrwf5OGseEeV7M l2otVMzSIn/i1HxrhMIfYnSq2fukxgHYRrt5LkkI+oPrj3yB1oHNtfRmX XpckK9cCI0kr/xe8TKlNEcrY0PzAGR/q9w4IEB9zvZ1bHkONYMWeVNbSB A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EANG0uU6rRDoG/2dsb2JhbABDqiOBBYFyAQEBAwESASc4BwULCzsLVwY1h2CZOAGeZohKYwSIC4wWhTGMXQ
X-IronPort-AV: E=Sophos;i="4.69,479,1315180800"; d="scan'208";a="11566862"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-1.cisco.com with ESMTP; 08 Nov 2011 23:05:26 +0000
Received: from [192.168.4.100] (sjc-fluffy-8914.cisco.com [10.20.249.165]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id pA8N5PbK001156; Tue, 8 Nov 2011 23:05:25 GMT
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <4EB14599.5000509@ericsson.com>
Date: Tue, 08 Nov 2011 16:05:25 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <6BC2ABF1-B528-4951-B50A-F74AE77A9772@cisco.com>
References: <CALiegfmvWWMf6dSikgfZqnSPuN-6UZKwAMfKu9HP2uqJxHMVCQ@mail.gmail.com> <4EB14599.5000509@ericsson.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
X-Mailer: Apple Mail (2.1084)
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Summary of 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: Tue, 08 Nov 2011 23:05:26 -0000

On Nov 2, 2011, at 7:28 AM, Magnus Westerlund wrote:

> The second piece I think the authors of the ROAP draft should take into
> consideration on their next update to clarify the purpose of the
> protocol and its relation to the API the application.

<as a roap co-author> Noted and will try to do that in the next version. I expect a future version of API draft to change to have a reference to ROAP which will make this all much easier to explain. 

The main thing I want to emphasize is that if we go down the ROAP path, it does not mandate you have to use ROAP. If you want to implement SIP in JS, or your own special protocol, that is all just fine. It's just one think you could use if you wanted and I would expect to see some Web to SIP gateways implement it.  It also does not stop the definition of a low level API. It could exist side by side with things using a low level API.