Re: [bfcpbis] I-D Action: draft-ietf-bfcpbis-bfcp-websocket-08.txt

Paul Kyzivat <pkyzivat@alum.mit.edu> Wed, 01 June 2016 14:14 UTC

Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: bfcpbis@ietfa.amsl.com
Delivered-To: bfcpbis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E975912D587 for <bfcpbis@ietfa.amsl.com>; Wed, 1 Jun 2016 07:14:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level:
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D_QD2QKBIpvd for <bfcpbis@ietfa.amsl.com>; Wed, 1 Jun 2016 07:14:45 -0700 (PDT)
Received: from resqmta-ch2-12v.sys.comcast.net (resqmta-ch2-12v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:44]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5795B12D511 for <bfcpbis@ietf.org>; Wed, 1 Jun 2016 07:14:45 -0700 (PDT)
Received: from resomta-ch2-19v.sys.comcast.net ([69.252.207.115]) by comcast with SMTP id 86qmbPGUFgEHv86uybzvUT; Wed, 01 Jun 2016 14:14:44 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1464790484; bh=kIGWR9D0LMMZM0ARVFjyxa46NOZctsx0GtU/PzYMjZU=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=dxZ+T775FnL4uZRoqmxjnNI1yOHrGaWD7hQqmOi+yEG6CbDCvEYGeUEAqTq+3Uuyf nhJPE+TE/veIVsXV5ZoF28ILFWGoWdKsF7WSu85kGGIchsIF9TCGhCv+NNDqZM9KJw ogvDwPPF/7gtaqQ7BSUeoMLicEq9EcZUf6QDCW5ZPboWH5F8qyKduukoUoap8ACXdU wMF8u79YS9FLdzsLk1XiSgaGP2IRZwL/qnEAMv0lFPavB2ZegFT2us0CRqD1xmiP5X 3r5k97cOB+sNcWnecJ4J1WEYYFYOguDKBPkqUP+cv5iosBMX6jftKEyOBFwXzTilGa ZmArNPw9hDXGw==
Received: from Paul-Kyzivats-MacBook-Pro.local ([73.218.51.154]) by resomta-ch2-19v.sys.comcast.net with comcast id 1SEj1t00t3KdFy101SEkx5; Wed, 01 Jun 2016 14:14:44 +0000
To: bfcpbis@ietf.org
References: <20160601065147.20308.50318.idtracker@ietfa.amsl.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <3b65d096-977d-9da6-aa9f-3883ec63dc4e@alum.mit.edu>
Date: Wed, 1 Jun 2016 10:14:43 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <20160601065147.20308.50318.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/bfcpbis/3IuA1KrlRI5pH16AM7VKBJtM-7g>
Subject: Re: [bfcpbis] I-D Action: draft-ietf-bfcpbis-bfcp-websocket-08.txt
X-BeenThere: bfcpbis@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: BFCPBIS working group discussion list <bfcpbis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bfcpbis/>
List-Post: <mailto:bfcpbis@ietf.org>
List-Help: <mailto:bfcpbis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jun 2016 14:14:47 -0000

I have a question.

> This document updates RFC4582bis and RFC4583bis.

Those documents are *drafts*. Does it really make sense to handle the 
changes this way? I guess that means that this document will need to be 
held until they become RFCs, and then it can update them.

Wouldn't it make more sense to simply make the changes in those drafts 
now, before they become RFCs?

	Thanks,
	Paul

On 6/1/16 2:51 AM, internet-drafts@ietf.org wrote:
>
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Binary Floor Control Protocol Bis  of the IETF.
>
>         Title           : The WebSocket Protocol as a Transport for the Binary Floor Control Protocol (BFCP)
>         Authors         : Victor Pascual
>                           Antón Román
>                           Stéphane Cazeaux
>                           Gonzalo Salgueiro
>                           Ram Mohan Ravindranath
>                           Sergio Garcia Murillo
> 	Filename        : draft-ietf-bfcpbis-bfcp-websocket-08.txt
> 	Pages           : 13
> 	Date            : 2016-05-31
>
> 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 updates RFC4582bis and RFC4583bis.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-bfcpbis-bfcp-websocket/
>
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-bfcpbis-bfcp-websocket-08
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-bfcpbis-bfcp-websocket-08
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> bfcpbis mailing list
> bfcpbis@ietf.org
> https://www.ietf.org/mailman/listinfo/bfcpbis
>