Re: [dispatch] Use of BFCP or MSRP over datachannel or websocket

Mary Barnes <mary.ietf.barnes@gmail.com> Mon, 01 April 2013 15:48 UTC

Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3839311E80C5 for <dispatch@ietfa.amsl.com>; Mon, 1 Apr 2013 08:48:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level:
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, 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 WqfEA4imOxo2 for <dispatch@ietfa.amsl.com>; Mon, 1 Apr 2013 08:48:41 -0700 (PDT)
Received: from mail-qc0-x236.google.com (mail-qc0-x236.google.com [IPv6:2607:f8b0:400d:c01::236]) by ietfa.amsl.com (Postfix) with ESMTP id 7637311E80AE for <dispatch@ietf.org>; Mon, 1 Apr 2013 08:48:41 -0700 (PDT)
Received: by mail-qc0-f182.google.com with SMTP id k19so1093847qcs.41 for <dispatch@ietf.org>; Mon, 01 Apr 2013 08:48:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=pFLSYi7F34K3bKnLneaOiqP8psRea2j0X5QxJLt6s2U=; b=fATed2jnA9e6X+aTx2WnLME5Vn3a7d9FClAnzpiLmTA6JUDPuZFUw+byanM0T0af6C TE7NtIhgq1RMVslUGky8prNaUSUfyLOpvne8HAbD9DybrSDvoVrMCo1Qt8yxEaKJiEp/ aZR3rPk7FSlmILFQBo84bunixIm+/NLYatJLc6NvtJ8D1mdBwCB13FUbklqZll8vzK0Z gqE48b56FPcjejfTyNUFS7fn3prFAt8gJ6Ida3+JwwEXIQ2zH1TU4S7CSQsnX1WuvygI gLdlSJCnzdTAMiFPdon70RM/3cdIBFdaof9rCmsPWTwSwlyHfiHBPitNYJD5WOXxS6ue oBXA==
MIME-Version: 1.0
X-Received: by 10.229.136.69 with SMTP id q5mr5050025qct.108.1364831320620; Mon, 01 Apr 2013 08:48:40 -0700 (PDT)
Received: by 10.49.94.166 with HTTP; Mon, 1 Apr 2013 08:48:40 -0700 (PDT)
In-Reply-To: <004301ce2e30$2317e700$6947b500$@co.in>
References: <949EF20990823C4C85C18D59AA11AD8B01D5F4@FR712WXCHMBA11.zeu.alcatel-lucent.com> <CAHBDyN5zZ3f6mjfXVXbvvvB7FTTKPWfDHvC9CaHQgau4_8uL1w@mail.gmail.com> <004301ce2e30$2317e700$6947b500$@co.in>
Date: Mon, 01 Apr 2013 10:48:40 -0500
Message-ID: <CAHBDyN6mBMwE2pFMh-iT4i302pqRDvBXkn+7NctrdVrVkJ+2iQ@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Parthasarathi R <partha@parthasarathi.co.in>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: DISPATCH <dispatch@ietf.org>
Subject: Re: [dispatch] Use of BFCP or MSRP over datachannel or websocket
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dispatch>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Apr 2013 15:48:42 -0000

Partha,

It's not entirely clear to me that RTCWEB is the "compelling" use case
for MSRP over websockets.  I'd be interested to hear who might think
that is the case.  I can envision other Real Time applications using
web servers to make use of this, as well.

I don't see any requirements in the RTCWEB WG (charter or
requirements) that indicate this is a compelling use case:
http://www.ietf.org/id/draft-ietf-rtcweb-use-cases-and-requirements-10.txt
There are no use cases for IM, Chat or MSRP specifically that I could
find and I couldn't find anything in the RTCWEB archives:
http://tools.ietf.org/html/draft-ietf-rtcweb-use-cases-and-requirements-10
If there has been discussion, please provide a pointer.

The discussion of MSRP over websockets should continue on this mailing
list.  Per the dispatching of IETF-86 topics, the current proposal is
to AD sponsor this document unless there are very compelling reasons
not to publish.
http://tools.ietf.org/wg/dispatch/trac/wiki

The proposal had been for the general discussion of "foo" over
websockets to happen on the RAI list.    The last I looked there are
at least 200 people subscribed to DISPATCH that are not on the RAI
area mailing list.  I strongly encourage folks with an interest in the
topic to make sure they are subscribe to the RAI area mailing list:
https://www.ietf.org/mailman/listinfo/rai

Regards,
Mary.

On Sun, Mar 31, 2013 at 11:52 AM, Parthasarathi R
<partha@parthasarathi.co.in> wrote:
> The compelling reason for this draft is RTCWeb. In case of non-RTCWeb,
> TCP Shall be used which avoids the overhead introduced due to
> WebSocket. Please clarify in case WebSocket has some specific
> advantage over TCP in non-RTCWeb environment.
>
> In case dispatch or BFCPbis are not the right WG to make recommendation,
> then let us discuss in RTCWeb WG itself. Also, Please suggest if any
> other mailing list like (rai@ietf.org) is the right place to discuss.
>
> Thanks
> Partha
>
>> -----Original Message-----
>> From: dispatch-bounces@ietf.org [mailto:dispatch-bounces@ietf.org] On
>> Behalf Of Mary Barnes
>> Sent: Thursday, March 28, 2013 8:28 PM
>> To: DRAGE, Keith (Keith)
>> Cc: dispatch@ietf.org
>> Subject: Re: [dispatch] Use of BFCP or MSRP over datachannel or
>> websocket
>>
>> I don't think it's the job of dispatch or BFCPbis WG to define or even
>> make recommendations for RTCWEB.  That choice is up to the RTCWEB WG
>> and it shouldn't be influencing this work.  There are applications
>> other than RTCWEB that can and will make use of BFCPbis over
>> websockets.  I really don't understand why we are getting so hung up
>> on this - it's the BFCP messages themselves that are important - how
>> one chooses to transport is up to the application.
>>
>> Mary.
>>
>> On Thu, Mar 28, 2013 at 7:35 AM, DRAGE, Keith (Keith)
>> <keith.drage@alcatel-lucent.com> wrote:
>> > From what I have seen of the discussion so far, there appears to be a
>> body of support that there is a use case for both BFCP and MSRP over
>> websocket, for use in a non-rtcweb environment.
>> >
>> > If when we get to the rtcweb environment we allow this, and also
>> allow a usage over datachannel version, we essentially have two
>> solutions in the market place.
>> >
>> > If that occurs, what guidance will we give to a rtcweb developer as
>> to which to implement?
>> >
>> > Or do we envisage that only one will be allowed (and if so which) in
>> an rtcweb environment?
>> >
>> >
>> >
>> > Regards
>> >
>> > Keith
>> > _______________________________________________
>> > dispatch mailing list
>> > dispatch@ietf.org
>> > https://www.ietf.org/mailman/listinfo/dispatch
>> _______________________________________________
>> dispatch mailing list
>> dispatch@ietf.org
>> https://www.ietf.org/mailman/listinfo/dispatch
>