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

"Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com> Tue, 09 February 2016 19:50 UTC

Return-Path: <gsalguei@cisco.com>
X-Original-To: bfcpbis@ietfa.amsl.com
Delivered-To: bfcpbis@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47D7A1ACEF7 for <bfcpbis@ietfa.amsl.com>; Tue, 9 Feb 2016 11:50:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.502
X-Spam-Level:
X-Spam-Status: No, score=-14.502 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, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 o_3Pmt58Md0J for <bfcpbis@ietfa.amsl.com>; Tue, 9 Feb 2016 11:50:08 -0800 (PST)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CD2461ACEF4 for <bfcpbis@ietf.org>; Tue, 9 Feb 2016 11:50:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8282; q=dns/txt; s=iport; t=1455047407; x=1456257007; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=tu/wVy2LggpFo9CMb/stTSQsqCwjvfOUSKd/CcWYKmc=; b=X+U+h41zeUeHUpSJ3CzVuFXtCQmKgOG2/xomC+RZ1H9ipWVZrNFqDbC4 G5t4bGffoGZ3IpQaH0jCpLdkdVpXv3ia+VHJnxHGuq9qJwCUR+JLKnsry xW/a4+pQe+nq8HP7dLbWTBPEGBF6Qi55PYXxKkt+SOuB9LmkRrci7ldZJ M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AFAgD1QbpW/5BdJa1dgzpSXg8GiFaxHQENgWYXDIUgSgIcgRs4FAEBAQEBAQGBCoRBAQEBAwEBAQEgEToLBQcEAgEIEQMBAgECAiYCAgIlCxUICAIEDgWIEwgOsB6OcwEBAQEBAQEBAQEBAQEBAQEBAQEBARV7hRcBgWyCSoQwGIJqK4EPBZZ4AYVLiASBW0qDeYhVjj4BHgEBQoNkaodXfAEBAQ
X-IronPort-AV: E=Sophos;i="5.22,422,1449532800"; d="scan'208";a="236632861"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 09 Feb 2016 19:50:06 +0000
Received: from XCH-ALN-020.cisco.com (xch-aln-020.cisco.com [173.36.7.30]) by rcdn-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id u19Jo6w8012292 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 9 Feb 2016 19:50:06 GMT
Received: from xch-aln-009.cisco.com (173.36.7.19) by XCH-ALN-020.cisco.com (173.36.7.30) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Tue, 9 Feb 2016 13:50:05 -0600
Received: from xch-aln-009.cisco.com ([173.36.7.19]) by XCH-ALN-009.cisco.com ([173.36.7.19]) with mapi id 15.00.1104.009; Tue, 9 Feb 2016 13:50:06 -0600
From: "Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com>
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
Thread-Topic: [bfcpbis] I-D Action: draft-ietf-bfcpbis-bfcp-websocket-05.txt
Thread-Index: AQHRBdZW9p6Pt0dHI0G5J5gRtUWM655p+f6AgDBfdwCAAS0sAIB/icyAgAmmyoCAAIfWgA==
Date: Tue, 09 Feb 2016 19:50:06 +0000
Message-ID: <A01A06CB-BCAE-45E8-9DF2-2F2F41005143@cisco.com>
References: <20151013164348.9920.89287.idtracker@ietfa.amsl.com> <6D74D935-2204-49AD-9CDA-D432A74BD477@cisco.com> <D26B6E1C.5EAA1%eckelcu@cisco.com> <D26CBA43.490B0%rmohanr@cisco.com> <D2D7B752.501D2%rmohanr@cisco.com> <D2DF8092.663D0%eckelcu@cisco.com>
In-Reply-To: <D2DF8092.663D0%eckelcu@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.82.210.181]
Content-Type: text/plain; charset="utf-8"
Content-ID: <94DE66B8EB3FD3478D0260A9DE4BDA09@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/bfcpbis/9jSun3bC7CnhNJvpuVN1jFUNAYg>
Cc: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>, "bfcpbis@ietf.org" <bfcpbis@ietf.org>, "bfcpbis-chairs@tools.ietf.org" <bfcpbis-chairs@tools.ietf.org>, "christer.holmberg@ericsson.com" <christer.holmberg@ericsson.com>
Subject: Re: [bfcpbis] I-D Action: draft-ietf-bfcpbis-bfcp-websocket-05.txt
X-BeenThere: bfcpbis@ietf.org
X-Mailman-Version: 2.1.15
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, 09 Feb 2016 19:50:10 -0000

Thanks, Charles.

We’re awaiting sign-off from Christer that his points on both drafts are properly addressed.  Once that happens there are no more open issues.

Two comments:

- We think draft-ietf-bfcpbis-bfcp-websocket is ready for WGLC
- We’d appreciate some direction from the chairs on how to move forward the new draft (draft-ram-bfcpbis-sdp-ws-uri) that was spawned from this effort, which we also believe is ready for WGLC.

Thanks,

Gonzalo



> On Feb 9, 2016, at 2:43 PM, Charles Eckel (eckelcu) <eckelcu@cisco.com> wrote:
> 
> Ram and other draft authors,
> 
> Thanks for updating and posting the revised draft ( https://tools.ietf.org/html/draft-ietf-bfcpbis-bfcp-websocket-06 ). 
> I would like to poll the working group to see if people think this draft is now ready for WGLC.
> 
> Thanks,
> Charles
> 
> On 2/3/16, 12:20 AM, "Ram Mohan R (rmohanr)" <rmohanr@cisco.com> wrote:
> 
>> Hi Charles / WG,
>> 
>> We have published a new revision of draft-ietf-bfcpbis-bfcp-websocket and
>> also draft-ram-bfcpbis-sdp-ws-uri which addresses the comments given by
>> Christer
>> (https://mailarchive.ietf.org/arch/msg/bfcpbis/S_MlYOJz-kkE3yLu5IANL93ndmM)
>> 
>> Regards,
>> Ram
>> 
>> 
>> -----Original Message-----
>> From: bfcpbis <bfcpbis-bounces@ietf.org> on behalf of Cisco Employee
>> <rmohanr@cisco.com>
>> Date: Saturday, 14 November 2015 at 10:12 AM
>> To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "Gonzalo Salgueiro
>> (gsalguei)" <gsalguei@cisco.com>, "bfcpbis@ietf.org" <bfcpbis@ietf.org>,
>> "christer.holmberg@ericsson.com" <christer.holmberg@ericsson.com>
>> Cc: "bfcpbis-chairs@tools.ietf.org" <bfcpbis-chairs@tools.ietf.org>
>> Subject: Re: [bfcpbis] I-D Action: draft-ietf-bfcpbis-bfcp-websocket-05.txt
>> 
>>> Hi Charles,
>>> 
>>> I will get back with responses and updated diffs to
>>> draft-ram-bfcpbis-sdp-ws-uri soon. I agree that we should wait till this
>>> is resolved before looking to start WGLC.
>>> 
>>> Regards,
>>> Ram
>>> 
>>> -----Original Message-----
>>> From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
>>> Date: Saturday, 14 November 2015 12:14 am
>>> To: "Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com>,
>>> "bfcpbis@ietf.org" <bfcpbis@ietf.org>, "christer.holmberg@ericsson.com"
>>> <christer.holmberg@ericsson.com>
>>> Cc: "bfcpbis-chairs@tools.ietf.org" <bfcpbis-chairs@tools.ietf.org>, Cisco
>>> Employee <rmohanr@cisco.com>
>>> Subject: Re: [bfcpbis] I-D Action:
>>> draft-ietf-bfcpbis-bfcp-websocket-05.txt
>>> 
>>>> Christer reviewed draft-ram-bfcpbis-sdp-ws-uri and recommended
>>>> substantial
>>>> changes to it. The authors have not yet responded to that.
>>>> 
>>>> Regarding draft-ietf-bfcpbis-bfcp-websocket, I¹d like to see this
>>>> response
>>>> and potential impacts on either/both drafts before starting WGLC for
>>>> draft-ietf-bfcpbis-bfcp-websocket.
>>>> 
>>>> 
>>>> Cheers,
>>>> Charles
>>>> 
>>>> On 10/13/15, 10:02 AM, "bfcpbis on behalf of Gonzalo Salgueiro
>>>> (gsalguei)"
>>>> <bfcpbis-bounces@ietf.org on behalf of gsalguei@cisco.com> wrote:
>>>> 
>>>>> New version of the draft has been published and addresses all open
>>>>> comments raised by Christer.  At this point authors feel this is ready
>>>>> for WGLC.
>>>>> 
>>>>> There is a pending request for Christer to review the complementary
>>>>> draft
>>>>> he requested
>>>>> (draft-ram-bfcpbis-sdp-ws-uri-00) be split off from the original
>>>>> document. Once this is done, we ask the chairs for guidance on how best
>>>>> to progress this spin-off draft.
>>>>> 
>>>>> Thanks,
>>>>> 
>>>>> Gonzalo
>>>>> 
>>>>>> On Oct 13, 2015, at 12:43 PM, 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
>>>>>> Working Group 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-05.txt
>>>>>> Pages           : 14
>>>>>> Date            : 2015-10-13
>>>>>> 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.
>>>>>> 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-05
>>>>>> A diff from the previous version is available at:
>>>>>> https://www.ietf.org/rfcdiff?url2=draft-ietf-bfcpbis-bfcp-websocket-05
>>>>>> 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
>> 
>>