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

Victor Pascual <victor.pascual.avila@gmail.com> Tue, 07 June 2016 18:16 UTC

Return-Path: <victor.pascual.avila@gmail.com>
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 E4B9D12D187 for <bfcpbis@ietfa.amsl.com>; Tue, 7 Jun 2016 11:16:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 dTTgwM_dHCeY for <bfcpbis@ietfa.amsl.com>; Tue, 7 Jun 2016 11:16:13 -0700 (PDT)
Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4018212D82A for <bfcpbis@ietf.org>; Tue, 7 Jun 2016 11:16:12 -0700 (PDT)
Received: by mail-wm0-x232.google.com with SMTP id n184so148978794wmn.1 for <bfcpbis@ietf.org>; Tue, 07 Jun 2016 11:16:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-transfer-encoding :message-id:cc:from:subject:date:to; bh=RZZ3eaDHO9q08YHklmx9M8Mx+tm74BYDkyobFXwqezg=; b=gt1zbJUHJd30ixfv1vQT8iCvJ4IN7Xvv0ww4OXPYjJrGF8v+ilj6i2tpwLkY4xTxoi lX9Atgyrx1k8YsOA5OzxqJre25wT//i4Y7aFB47loTWLbomnF7+i+LrrVKhNKR+pqrUC S3U4BgEJf/jXVNL7sDxH3ex0BATgGu5q1F3TWSW0zG/POWMf4eWNQ+wqMvmc0VmfMQbU WV9CJcNT780Py1tvqgk2i3weINZHmf0/YXXTWNQvCSthzLRsb+7s/2cnsy1NIbKwL9FW jlNp1jFNjWlYTKFOiu4FxISMlkDdEyqZVJmeGcXOf2lUA/Zo7z9FsFt7laqkCS54fUrn 7Fcw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:references:mime-version:in-reply-to :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=RZZ3eaDHO9q08YHklmx9M8Mx+tm74BYDkyobFXwqezg=; b=Az9T/pAPR5k/m7I2+wlnngdO7C+ebJWMLcziK8UoAF7BPWnAhdrbHm0m2ScKupl8ip zjK3SAjF/u6paZSKaGEdfjrN6BuzeVFlnKbuIqZrT+S7RkOI5CXoxXDKmCh6nEZRMbGY P9ulemXiMkLKOoTR6Xqqi0UcLpthedyi41iwhEPHLQSHoKEvwrgjfy/iYa6eSHvGRl+2 gklfX/lI0K9BJ1iU4c13dJoN+aTzeNYjf6cwYv5Nkl/Vq3WURPX/5AQSoqN0gysEJTSC sfSkENdp1JnGwC+LibPt21zhsc5U5K6xAanP3IgGAnTOhpSe+NvDaR94HEOw8CnHWzrk Anjg==
X-Gm-Message-State: ALyK8tKBaZ8HP9Ix6Uv+GvpaXvVeBoprIj2waQ6vM0Wpbt0p/TIWEueJZrp1MGVlyrhIzQ==
X-Received: by 10.28.125.18 with SMTP id y18mr947993wmc.68.1465323370657; Tue, 07 Jun 2016 11:16:10 -0700 (PDT)
Received: from [10.160.206.231] ([31.4.190.246]) by smtp.gmail.com with ESMTPSA id lr9sm26630919wjb.39.2016.06.07.11.16.08 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 07 Jun 2016 11:16:09 -0700 (PDT)
References: <20160601065147.20308.50318.idtracker@ietfa.amsl.com> <3b65d096-977d-9da6-aa9f-3883ec63dc4e@alum.mit.edu> <F249579F-6200-4902-B965-3E8ADFE1BF43@cisco.com> <75DDBE07-12A5-407E-95D3-E61F0375D672@cisco.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <75DDBE07-12A5-407E-95D3-E61F0375D672@cisco.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-Id: <F6128D14-A336-40F0-ADC6-11F558F600DE@gmail.com>
X-Mailer: iPhone Mail (12D508)
From: Victor Pascual <victor.pascual.avila@gmail.com>
Date: Tue, 7 Jun 2016 20:16:07 +0200
To: "Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/bfcpbis/m_IQ3yXzLJ8ZTADeVLm6zO6zNbk>
Cc: "bfcpbis@ietf.org" <bfcpbis@ietf.org>, "Charles Eckel \(eckelcu\)" <eckelcu@cisco.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>
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: Tue, 07 Jun 2016 18:16:15 -0000

Fine with me

> On 07 Jun 2016, at 20:12, Gonzalo Salgueiro (gsalguei) <gsalguei@cisco.com> wrote:
> 
> I’m OK with that approach.  I also agree that they are entirely too different in purpose to try and merge them.
> 
> -G
> 
> 
>> On Jun 7, 2016, at 1:41 PM, Charles Eckel (eckelcu) <eckelcu@cisco.com> wrote:
>> 
>> (As an individual)
>> 
>> Good question. I agree it seems a bit strange. But my thinking is that our use of “Updates” may not be appropriate. I view RFC 4582 and RFC 4583 as defining BFCP over TCP and over UDP. This draft takes BFCP over TCP and defines how to encapsulate it within a WebSocket and how to negotiate that encapsulation. So I think these drafts are related but separate, and that we should remove the “Updates” label and simply have RFC4582bis and RFC4583bis as normative references (as they already are). Thoughts?
>> 
>> Cheers,
>> Charles
>> 
>> 
>> 
>>> On 6/1/16, 7:14 AM, "bfcpbis on behalf of Paul Kyzivat" <bfcpbis-bounces@ietf.org on behalf of pkyzivat@alum.mit.edu> wrote:
>>> 
>>> 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
>>> 
>>> _______________________________________________
>>> bfcpbis mailing list
>>> bfcpbis@ietf.org
>>> https://www.ietf.org/mailman/listinfo/bfcpbis
>> _______________________________________________
>> bfcpbis mailing list
>> bfcpbis@ietf.org
>> https://www.ietf.org/mailman/listinfo/bfcpbis
> 
> _______________________________________________
> bfcpbis mailing list
> bfcpbis@ietf.org
> https://www.ietf.org/mailman/listinfo/bfcpbis