Re: [bfcpbis] I-D Action: draft-ietf-bfcpbis-rfc4582bis-07.txt

Tom Kristensen <tomkrist@cisco.com> Fri, 04 January 2013 15:59 UTC

Return-Path: <tomkrist@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 D989321F8837 for <bfcpbis@ietfa.amsl.com>; Fri, 4 Jan 2013 07:59:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xlRNVxay-m0I for <bfcpbis@ietfa.amsl.com>; Fri, 4 Jan 2013 07:59:40 -0800 (PST)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 892D021F8830 for <bfcpbis@ietf.org>; Fri, 4 Jan 2013 07:59:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5308; q=dns/txt; s=iport; t=1357315179; x=1358524779; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=if/JKpl4zDPAuL9Aa4vip98cT0yChf3z6UieFeeV99U=; b=eI21sMAospB85P7+1PG2dt5Q3rnghEuhOoPZv6IXI+ypoi5UZ6OeeAwL 26XjwA33yZMgiNJKjy9voiK4/14oleQpRjufCkjwz+lLKpjZJ5aJaDgzz O1BBVur8qfT6fF2CqpPc7HXVqfZo3i5hP5c+eJ7Kml9fntOEHCQ3CGYIg c=;
X-IronPort-AV: E=Sophos;i="4.84,411,1355097600"; d="scan'208";a="79524007"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-2.cisco.com with ESMTP; 04 Jan 2013 15:59:38 +0000
Received: from [10.55.87.60] (dhcp-10-55-87-60.cisco.com [10.55.87.60]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r04FxbMk004067; Fri, 4 Jan 2013 15:59:37 GMT
Message-ID: <50E6FC69.4060907@cisco.com>
Date: Fri, 04 Jan 2013 16:59:37 +0100
From: Tom Kristensen <tomkrist@cisco.com>
Organization: Cisco
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.15) Gecko/20101027 Fedora/3.0.10-1.fc12 Lightning/1.0b2pre Thunderbird/3.0.10
MIME-Version: 1.0
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
References: <20121219132019.28896.3533.idtracker@ietfa.amsl.com> <50D1C4C1.5020104@cisco.com> <92B7E61ADAC1BB4F941F943788C08828046EED5E@xmb-aln-x08.cisco.com> <92B7E61ADAC1BB4F941F943788C08828046F2256@xmb-aln-x08.cisco.com>
In-Reply-To: <92B7E61ADAC1BB4F941F943788C08828046F2256@xmb-aln-x08.cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "bfcpbis@ietf.org" <bfcpbis@ietf.org>, 'Tom Kristensen' <2mkristensen@gmail.com>
Subject: Re: [bfcpbis] I-D Action: draft-ietf-bfcpbis-rfc4582bis-07.txt
X-BeenThere: bfcpbis@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Fri, 04 Jan 2013 15:59:43 -0000

On 12/27/2012 12:03 AM, Charles Eckel (eckelcu) wrote:
> Hi Tom,
>    
Thanks Charles. Fixed all but the first issue in my local version of the 
draft.

> I had a close look at the changes, and overall they look okay to me.
> During my review, I did notice a few editorial things that are worth fixing:
> 1) many of the references to [16] do not work correctly, including the first reference in section 3.2, as well as those in section 6.2.
>    
What do you mean by references not working correctly?

> 2) For the note added in section 5.1, you have an extra 'a' and are missing a comma:
> r/BFCP is designed to a achieve small message size, as explained in Section 1 and BFCP entities/BFCP is designed to achieve small message size, as explained in Section 1, and BFCP entities
>    
Right. Fixed.

> 3) Section 6.2:
> r/ security considerations in Section 6 also applies/security considerations in Section 6 also apply
>    
Indeed. Fixed.

> 4) section 6.2.3:
> r/A Denial of Service (DoS) attacks/A Denial of Service (DoS) attack
>    
Yes. Fixed.

> 5) Section 8, I think we should rework the following paragraph:
>
>     When using BFCP over unreliable transport, it is also required to
>     choose values that let the receiver distinguish the reception of the
>     next message in a sequence of BFCP messages from a retransmission of
>     a previous message.  Therefore, BFCP entities using unreliable
>     transport SHOULD use monotonically increasing values for the
>     Transaction ID.
>
> To read as follows:
>
>     When using BFCP over an unreliable transport, it is important that the initiator
>     of a transaction choose a Transaction ID value that lets the receiver distinguish
>     the reception of the next message in a sequence of BFCP messages from a retransmission of
>     a previous message.  Therefore, BFCP entities using an unreliable  transport SHOULD use
>     monotonically increasing Transaction ID values.
>    
Much better. Great with input from native English speakers ;-)

> 6) Section 8,
> r/When using BFCP over unreliable transports/When using BFCP over an unreliable transport
> Note, a similar change was made in many places in order to address comments from Gonzalo; however, a global search and replace should be done to catch numerous other places in which it still occurs.
>    
Searched through and fixed. Also for "reliable transports".

-- Tom

> Cheers,
> Charles
>
>
>    
>> -----Original Message-----
>> From: bfcpbis-bounces@ietf.org [mailto:bfcpbis-bounces@ietf.org] On
>> Behalf Of Charles Eckel (eckelcu)
>> Sent: Wednesday, December 19, 2012 2:08 PM
>> To: Tom Kristensen (tomkrist); bfcpbis@ietf.org
>> Cc: 'Tom Kristensen'
>> Subject: Re: [bfcpbis] I-D Action: draft-ietf-bfcpbis-rfc4582bis-07.txt
>>
>> Everyone who submitted WGLC comments, please confirm this version
>> addresses all your comments satisfactorily.
>> Everyone else, please review the entire draft carefully and share any
>> comment or concerns you have.
>> Thanks to Tom for incorporating all the feedback and posting this update.
>>
>> Happy Holidays!
>> Charles
>>
>>      
>>> -----Original Message-----
>>> From: bfcpbis-bounces@ietf.org [mailto:bfcpbis-bounces@ietf.org] On
>>> Behalf Of Tom Kristensen (tomkrist)
>>> Sent: Wednesday, December 19, 2012 5:45 AM
>>> To: bfcpbis@ietf.org
>>> Cc: 'Tom Kristensen'
>>> Subject: Re: [bfcpbis] I-D Action: draft-ietf-bfcpbis-rfc4582bis-07.txt
>>>
>>> On 12/19/2012 02:20 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 Binary Floor Control Protocol (BFCP)
>>>> 	Author(s)       : Gonzalo Camarillo
>>>>                             Keith Drage
>>>>                             Tom Kristensen
>>>>                             Joerg Ott
>>>>                             Charles Eckel
>>>> 	Filename        : draft-ietf-bfcpbis-rfc4582bis-07.txt
>>>> 	Pages           : 89
>>>> 	Date            : 2012-12-19
>>>>
>>>>          
>>> Changes from -06:
>>> - Language clarification - mail on list from Charles Eckel 2012-10-13
>>> - Language clarification - use "BFCP connection" across the document,
>>>     change three occurences of "BFCP association".
>>> - Resolved a lot of issues, small and large - mail on list 2012-10-24
>>>     after WGLC from Gonzalo Camarillo. Also, later mail discussion
>>>     with regard to 5 of the issues.
>>> - Added reference to RFC 5763, Section 6.7 - mail on list from Christer
>>>     Holmberg 2012-11-28.
>>>
>>>
>>> To my knowledge, in this draft version all the issues from WGLC and
>>> after are answered and fixed if appropriate.
>>>
>>>
>>> -- Tom
>>> _______________________________________________
>>> 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
>>