Re: [dispatch] FW: New Version Notification for draft-pascual-dispatch-bfcp-websocket-00.txt

Paul Kyzivat <pkyzivat@alum.mit.edu> Tue, 12 March 2013 16:51 UTC

Return-Path: <pkyzivat@alum.mit.edu>
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 C3F6711E80D2 for <dispatch@ietfa.amsl.com>; Tue, 12 Mar 2013 09:51:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.062
X-Spam-Level:
X-Spam-Status: No, score=-0.062 tagged_above=-999 required=5 tests=[AWL=0.375, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.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 yHWXFkjLhxwg for <dispatch@ietfa.amsl.com>; Tue, 12 Mar 2013 09:51:20 -0700 (PDT)
Received: from qmta03.emeryville.ca.mail.comcast.net (qmta03.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:43:76:96:30:32]) by ietfa.amsl.com (Postfix) with ESMTP id 3199C11E80D9 for <dispatch@ietf.org>; Tue, 12 Mar 2013 09:51:18 -0700 (PDT)
Received: from omta13.emeryville.ca.mail.comcast.net ([76.96.30.52]) by qmta03.emeryville.ca.mail.comcast.net with comcast id AcrY1l00417UAYkA3grDWR; Tue, 12 Mar 2013 16:51:13 +0000
Received: from dhcp-11c0.meeting.ietf.org ([IPv6:2001:df8:0:16:e4e8:37a9:96e2:16ed]) by omta13.emeryville.ca.mail.comcast.net with comcast id AgrC1l0052khnUS8ZgrCM7; Tue, 12 Mar 2013 16:51:12 +0000
Message-ID: <513F5CFF.2070608@alum.mit.edu>
Date: Wed, 13 Mar 2013 00:51:11 +0800
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130216 Thunderbird/17.0.3
MIME-Version: 1.0
To: dispatch@ietf.org
References: <20130215171708.27730.58906.idtracker@ietfa.amsl.com> <CD442C6C.B156%vpascual@acmepacket.com> <CAGTXFp-Ee_XsD0NdmrFxjqyUN9cP-+Q2XNAKV35MMTtZJxUEcA@mail.gmail.com> <CAHBDyN4zU1TEPsxViMZsCxtc7TkpqAeaudfKVzChWkWzosy25w@mail.gmail.com>
In-Reply-To: <CAHBDyN4zU1TEPsxViMZsCxtc7TkpqAeaudfKVzChWkWzosy25w@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1363107073; bh=LfCwsLrj9Pp1RQw7nl8n+5TyArLvzAvBvRf/BlaZXUE=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=pFYFEOmLoMM0uHrSszXQG01s+bsag3aHK9NepFh11aD/MI24IGK5nDuDV0KE/I8PO CVnzQpDx1+Aablctd91Oo8WSXTYXBhkIceLlQiim2otEcGrVYrCwud/SWxStZo20LN pvB4Dm5/DqzS+kQ5g9l/HTvzgdNEG3UAlP4YZa9eGocySN2LVs6tXiWqwib3NFNFbW rJzWPpbUaX94jtoxGrQlQtgkicjsPY9HeGYG8EpcbOSHJGBNtVQn7RwWF7f5ICPCk5 mPJ+v8L0bBm8Scz+JutHDp4bBork+oDN7Y0hDaMl/1C+TIBKuTWQycr3QfTTpay37C Gz2KHxiv7/WXw==
Subject: Re: [dispatch] FW: New Version Notification for draft-pascual-dispatch-bfcp-websocket-00.txt
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: Tue, 12 Mar 2013 16:51:22 -0000

I am ok with this.

*BUT* I still want to again raise the question whether we should be 
thinking in general about the porting of existing protocols to new 
transports.

The RTCWEB effort is putting a lot of emphasis on rapid session startup 
and connection establishment. In that environment it is attractive to 
think about having lots of protocols run over data channels, so they can 
take advantage of multiplexing and quick startup. This could apply to 
BFCP and MSRP that are working on websocket transports. And how many 
more will there be?

Because websockets and data channels will be similar from an API 
perspecitive, perhaps it would be possible to define a transport mapping 
that works for both. But that won't help unless both are actually 
implemented.

	Thanks,
	Paul


On 3/12/13 10:02 PM, Mary Barnes wrote:
> Hi all,
>
> As discussed in the DISPATCH WG session, we are doing an official call
> for comments/agreement to move this work item to the BFCPbis WG.  If
> folks could please respond if they support this or provide comments if
> you do not.
>
> As discussed in the meeting, if we get agreement, the chairs/ADs would
> update BFCPbis WG charter to include this work item and forward to WG
> and IESG for review/approval.  The WG would then need to decide
> whether to adopt this specific document towards that WG deliverable.
>
> Please respond no later than Friday, March 22nd, 2013.  Silence will
> be taken as agreement.
>
> Thanks,
> Mary
> DISPATCH WG co-chair
>
> On Thu, Feb 21, 2013 at 11:38 AM, Victor Pascual Avila
> <victor.pascual.avila@gmail.com> wrote:
>> Hi all,
>>
>> We have submitted a new Internet draft to describe the WebSocket
>> Protocol as a Transport for the Binary Floor Control Protocol (BFCP).
>> We are looking forward to your review comments.
>>
>> http://tools.ietf.org/html/draft-pascual-dispatch-bfcp-websocket-00
>>
>> Best regards,
>> -Victor
>>
>>
>> On 2/15/13 6:17 PM, "internet-drafts@ietf.org" <internet-drafts@ietf.org>
>> wrote:
>>
>>>
>>> A new version of I-D, draft-pascual-dispatch-bfcp-websocket-00.txt
>>> has been successfully submitted by Victor Pascual and posted to the
>>> IETF repository.
>>>
>>> Filename:       draft-pascual-dispatch-bfcp-websocket
>>> Revision:       00
>>> Title:          The WebSocket Protocol as a Transport for the Binary Floor
>>> Control Protocol (BFCP)
>>> Creation date:  2013-02-15
>>> Group:          Individual Submission
>>> Number of pages: 9
>>> URL:
>>> http://www.ietf.org/internet-drafts/draft-pascual-dispatch-bfcp-websocket-
>>> 00.txt
>>> Status:
>>> http://datatracker.ietf.org/doc/draft-pascual-dispatch-bfcp-websocket
>>> Htmlized:
>>> http://tools.ietf.org/html/draft-pascual-dispatch-bfcp-websocket-00
>>>
>>>
>>> Abstract:
>>>    The WebSocket protocol enables two-way realtime communication between
>>>    clients and servers.  This document specifies a new WebSocket sub-
>>>    protocol as a reliable transport mechanism between Binary Floor
>>>    Control Protocol (BFCP) entities to enable usage of BFCP in new
>>>    scenarios.  This document normatively updates
>>>    [I-D.draft-ietf-bfcpbis-rfc4582bis] and
>>>    [I-D.draft-ietf-bfcpbis-rfc4583bis]
>>>
>>>
>>>
>>>
>>>
>>> The IETF Secretariat
>>>
>> _______________________________________________
>> 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
>