Re: [bfcpbis] WGLC on draft-ietf-bfcpbis-bfcp-websocket-06

"Ram Mohan R (rmohanr)" <rmohanr@cisco.com> Wed, 01 June 2016 04:51 UTC

Return-Path: <rmohanr@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 1D7F112D687 for <bfcpbis@ietfa.amsl.com>; Tue, 31 May 2016 21:51:09 -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 lntmOmI7tjWQ for <bfcpbis@ietfa.amsl.com>; Tue, 31 May 2016 21:51:07 -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 DA4A212B02D for <bfcpbis@ietf.org>; Tue, 31 May 2016 21:51:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8068; q=dns/txt; s=iport; t=1464756666; x=1465966266; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=xHD/gko6c4tIcmhUCHFIZai5IwIZCCqSaDeGLLUplAU=; b=cNj5TmGzLivUFREYHMtbg0L66QskUOCxoN+jG/rszABHg8+QYRuZDyFb jpUEqWsOpPUJqaigQRQuDh1nFBhgTZC7/tyqP55oUjvwcKR7fGe12Or0m OB+mHf0Apt/UutR/TxQhbmhJdkwo2PdTKmqJxDwk9PkzGWjfsvwHMmlW2 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0D5AQAWaU5X/5RdJa1bgz1WfQa6DgENg?= =?us-ascii?q?XoXDYUjSgIcgSA4FAEBAQEBAQFlJ4RFAQEBBAEBATE6FwQCAQYCEQMBAgEEKAI?= =?us-ascii?q?CJQsdCAIEARKILw6RHJ0VBpFbAQEBAQEBAQEBAQEBAQEBAQEBARkFe4l5hzuCX?= =?us-ascii?q?wWFdo1BhQABhX+FZYI7gWmET4dJgRuGM4kYAR4BAUKDbW6JOX8BAQE?=
X-IronPort-AV: E=Sophos;i="5.26,399,1459814400"; d="scan'208";a="280011714"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 01 Jun 2016 04:51:05 +0000
Received: from XCH-RTP-008.cisco.com (xch-rtp-008.cisco.com [64.101.220.148]) by rcdn-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id u514p5f0024404 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <bfcpbis@ietf.org>; Wed, 1 Jun 2016 04:51:05 GMT
Received: from xch-rtp-017.cisco.com (64.101.220.157) by XCH-RTP-008.cisco.com (64.101.220.148) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Wed, 1 Jun 2016 00:51:04 -0400
Received: from xch-rtp-017.cisco.com ([64.101.220.157]) by XCH-RTP-017.cisco.com ([64.101.220.157]) with mapi id 15.00.1104.009; Wed, 1 Jun 2016 00:51:04 -0400
From: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com>, "bfcpbis@ietf.org" <bfcpbis@ietf.org>
Thread-Topic: [bfcpbis] WGLC on draft-ietf-bfcpbis-bfcp-websocket-06
Thread-Index: AQHRhf18DSKK8+o9DUymu+GcytQEaZ90HygAgDP2gACACXvEgIAirSEAgADXHgA=
Date: Wed, 1 Jun 2016 04:51:04 +0000
Message-ID: <D37466BF.5E3D3%rmohanr@cisco.com>
References: <D3198384.69C68%eckelcu@cisco.com> <D32302D4.6A538%eckelcu@cisco.com> <EEF58659-FBE2-401A-A857-711B9B2CE6AD@cisco.com> <D3563919.6DDF3%eckelcu@cisco.com> <D37331FB.71185%eckelcu@cisco.com>
In-Reply-To: <D37331FB.71185%eckelcu@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.6.4.160422
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.65.53.238]
Content-Type: text/plain; charset="euc-kr"
Content-ID: <B33D8370583FBC4B9F77033DCF3C634A@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/bfcpbis/bC4yJPJSFZWaoG_DRccimG3tE_E>
Subject: Re: [bfcpbis] WGLC on draft-ietf-bfcpbis-bfcp-websocket-06
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 04:51:09 -0000

Hi Charles,

Thanks for your feedback. See inline

-----Original Message-----
From: bfcpbis <bfcpbis-bounces@ietf.org> on behalf of "Charles Eckel
(eckelcu)" <eckelcu@cisco.com>
Date: Wednesday, 1 June 2016 at 3:01 AM
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>om>, "Gonzalo Salgueiro
(gsalguei)" <gsalguei@cisco.com>
Cc: "bfcpbis@ietf.org" <bfcpbis@ietf.org>
Subject: Re: [bfcpbis] WGLC on draft-ietf-bfcpbis-bfcp-websocket-06

>I preparing the document writeup, I came up with a few comments (based on
>draft-ietf-bfcpbis-bfcp-websocket-07):
>
>1) Section 4.1, Sec-WebSocket-Protocol
>The example offers indicates the sub protocol as ³bfcp²
>The example answer indicates the sub protocol as ³BFCP²
>Was this done on purpose to call attention to the field being case
>insensitive? Tracing back through RFC 6455 and RFC 2616, I believe this
>field is in fact case insensitive, but would it be helpful to clarify that
>directly in this draft?

During WGLC reviews Paul suggested to use “BFCP”. I will change to that
way in the entire draft.

>
>2) Section 6.3, the formatting of this section suffers from the way
>references were made. It currently reads as follows:
>
>The SDP attribute 'ws-uri' defined in Section 3.1
>   of [Section 3.2
><https://tools.ietf.org/html/draft-ietf-bfcpbis-bfcp-websocket-07#ref-I-D.
>i
>etf-bfcpbis-sdp-ws-uri> of [I-D.ietf-bfcpbis-sdp-ws-uri] MUST be used when
>BFCP runs on top of WSS">I-D.ietf-bfcpbis-sdp-ws-uri] MUST be used when
>BFCP runs on top
>   of WS, which in turn runs on top of TCP.  The SDP attribute 'wss-uri'
>   defined in Section 3.2 of [Section 3.2
><https://tools.ietf.org/html/draft-ietf-bfcpbis-bfcp-websocket-07#ref-I-D.
>i
>etf-bfcpbis-sdp-ws-uri> of [I-D.ietf-bfcpbis-sdp-ws-uri] MUST be used when
>BFCP runs on top of WSS">I-D.ietf-bfcpbis-sdp-ws-uri] MUST be used
>   when BFCP runs on top of WSS, which in turn runs on top of TLS and
>   TCP.
>
>
>I expect this was meant to be as follows:
>
>The SDP attribute 'ws-uri' defined in Section 3.1
>   of [I-D.ietf-bfcpbis-sdp-ws-uri] MUST be used when BFCP runs on top
>   of WS, which in turn runs on top of TCP.  The SDP attribute 'wss-uri'
>   defined in Section 3.2 of [I-D.ietf-bfcpbis-sdp-ws-uri] MUST be used
>   when BFCP runs on top of WSS, which in turn runs on top of TLS and
>   TCP.


Suggested text looks good to me. I will fix it

>
>
>3) Section 7.1 suffers a similar reference formatting issue as section
>6.3.

Will fix

>
>4) Section 12.2, RFC 2818 is indicated as a reference, but it is not
>references from within the draft.

Will remove as its not being referenced

>
>Nits
>5) ³.² missing at end of first and second paragraphs in section 5 and at
>end of first paragraph in section 6.1 and in section 6.2.
>6) Section 6.3, s/a new SDP attributes/a new SDP attribute
>7) Section 7.1, s/whichcould/which could
>8) Section 7.2, s/a endpoint/an endpoint
>9) Section 10.2, s/RFC&rfc.number/RFCXXXX (two instances)

Thanks will fix these.

I will publish a revision soon.

Regards,
Ram

>
>Please have a look at these and update the draft accordingly.
>
>Cheers,
>Charles
>
>
>
>On 5/9/16, 12:58 PM, "bfcpbis on behalf of Charles Eckel (eckelcu)"
><bfcpbis-bounces@ietf.org on behalf of eckelcu@cisco.com> wrote:
>
>>Hi Gonzalo,
>>
>>Thanks to you and your co-authors. I have move the draft status to
>>waiting
>>for document writeup. I will be the document shepherd and prepare the
>>writeup.
>>
>>Cheers,
>>Charles
>>
>>
>>On 5/3/16, 12:09 PM, "Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com>
>>wrote:
>>
>>>Hi Charles - 
>>>
>>>The draft has been updated and addresses all WGLC comments received.  It
>>>is now ready for publication request.
>>>
>>>Cheers,
>>>
>>>Gonzalo
>>>
>>>
>>>> On Apr 1, 2016, at 3:07 AM, Charles Eckel (eckelcu)
>>>><eckelcu@cisco.com>
>>>>wrote:
>>>> 
>>>> (as chair)
>>>> 
>>>> WGLC has ended. Thanks again to Paul for his valuable comments. I ask
>>>>the authors to please share their thoughts on these and any other
>>>>comments they may have received directly, and update the draft
>>>>accordingly.
>>>> 
>>>> Cheers,
>>>> Charles
>>>> 
>>>> From: bfcpbis <bfcpbis-bounces@ietf.org> on behalf of Charles Eckel
>>>><eckelcu@cisco.com>
>>>> Date: Thursday, March 24, 2016 at 11:46 AM
>>>> To: "bfcpbis@ietf.org" <bfcpbis@ietf.org>
>>>> Subject: Re: [bfcpbis] WGLC on draft-ietf-bfcpbis-bfcp-websocket-06
>>>> 
>>>>> Thanks to Paul for having already reviewed and provided comments.
>>>>> Everyone else, please do likewise by the March 28 deadline.
>>>>> 
>>>>> Cheers,
>>>>> Charles
>>>>> 
>>>>> From: bfcpbis <bfcpbis-bounces@ietf.org> on behalf of Charles Eckel
>>>>><eckelcu@cisco.com>
>>>>> Date: Sunday, March 13, 2016 at 9:55 AM
>>>>> To: "bfcpbis@ietf.org" <bfcpbis@ietf.org>
>>>>> Subject: [bfcpbis] WGLC on draft-ietf-bfcpbis-bfcp-websocket-06
>>>>> 
>>>>>> This is to announce a 2 week WGLC on the draft:
>>>>>> https://tools.ietf.org/html/draft-ietf-bfcpbis-bfcp-websocket-06
>>>>>> 
>>>>>> Please review and provide any comments by Monday, March 28, 2016.
>>>>>> Comments should be sent to the authors and the BFCPBIS WG list.
>>>>>> If you review the draft but do not have any comments, please send a
>>>>>>note to that effect as well.
>>>>>> 
>>>>>> Thanks,
>>>>>> Charles
>>>>>> 
>>>>>> 
>>>> _______________________________________________
>>>> 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