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

"Charles Eckel (eckelcu)" <eckelcu@cisco.com> Tue, 07 June 2016 17:41 UTC

Return-Path: <eckelcu@cisco.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 0C31D12D191 for <bfcpbis@ietfa.amsl.com>; Tue, 7 Jun 2016 10:41:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.947
X-Spam-Level:
X-Spam-Status: No, score=-15.947 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 6Q9snYn_xoAY for <bfcpbis@ietfa.amsl.com>; Tue, 7 Jun 2016 10:41:46 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 72AAC12B00B for <bfcpbis@ietf.org>; Tue, 7 Jun 2016 10:41:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4390; q=dns/txt; s=iport; t=1465321306; x=1466530906; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=f5qDfmj4RMd75+MGY06N2Xo+9yBDnrOwtNRVzr+tk5s=; b=dxIluCEiDbzaI0CwcK3e8qxe8q4GtPFYwASJbGQ7R9J5slnm1U2cAOx+ GandLIfNkmWqZNk1iQOAxDEFaXL0IbeTh45hNPvPFR2V/sINR5Xy/cLO1 7pF60i66QpEOr9HgdY20SvNBOvcPBeJnR4+UWfQRmyPC1wziQ0cG7if9c Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ABAgDJBldX/51dJa1dDoMwVn0GumWBe?= =?us-ascii?q?RcLhSdKAhyBJTgUAQEBAQEBAWUnhEYBAQQBAQEgETobAgEIDgoCAiYCAgIlCxU?= =?us-ascii?q?QAgQBEogvDqs/kSEBAQEBAQEBAQEBAQEBAQEBAQEBAQEcgQGHHQiCToRAgwErg?= =?us-ascii?q?i4FmEsBhgOII4FqToQEiGSGPYkhAR42gzM7bokQfwEBAQ?=
X-IronPort-AV: E=Sophos;i="5.26,434,1459814400"; d="scan'208";a="282661024"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 Jun 2016 17:41:45 +0000
Received: from XCH-RCD-016.cisco.com (xch-rcd-016.cisco.com [173.37.102.26]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id u57HfjJG022030 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 7 Jun 2016 17:41:45 GMT
Received: from xch-aln-018.cisco.com (173.36.7.28) by XCH-RCD-016.cisco.com (173.37.102.26) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Tue, 7 Jun 2016 12:41:44 -0500
Received: from xch-aln-018.cisco.com ([173.36.7.28]) by XCH-ALN-018.cisco.com ([173.36.7.28]) with mapi id 15.00.1104.009; Tue, 7 Jun 2016 12:41:44 -0500
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "bfcpbis@ietf.org" <bfcpbis@ietf.org>
Thread-Topic: [bfcpbis] I-D Action: draft-ietf-bfcpbis-bfcp-websocket-08.txt
Thread-Index: AQHRu9IUgtCM8tsKUkqkEXZGBK8P25/U/BCAgAkyewA=
Date: Tue, 7 Jun 2016 17:41:44 +0000
Message-ID: <F249579F-6200-4902-B965-3E8ADFE1BF43@cisco.com>
References: <20160601065147.20308.50318.idtracker@ietfa.amsl.com> <3b65d096-977d-9da6-aa9f-3883ec63dc4e@alum.mit.edu>
In-Reply-To: <3b65d096-977d-9da6-aa9f-3883ec63dc4e@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.15.1.160411
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.20.182.35]
Content-Type: text/plain; charset="utf-8"
Content-ID: <66D4C1F774995447BAA747FCFC26E76F@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/bfcpbis/ApRrpjU7GabeVmd1BGojhLI8gf4>
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 17:41:48 -0000

(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