Re: [bfcpbis] I-D Action: draft-ietf-bfcpbis-rfc4582bis-07.txt
"Charles Eckel (eckelcu)" <eckelcu@cisco.com> Fri, 04 January 2013 17:43 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 2850521F889D for <bfcpbis@ietfa.amsl.com>; Fri, 4 Jan 2013 09:43:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.3
X-Spam-Level:
X-Spam-Status: No, score=-9.3 tagged_above=-999 required=5 tests=[AWL=1.300, 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 qNkKVQEPNvSh for <bfcpbis@ietfa.amsl.com>; Fri, 4 Jan 2013 09:43:12 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 91C1B21F88A5 for <bfcpbis@ietf.org>; Fri, 4 Jan 2013 09:43:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6541; q=dns/txt; s=iport; t=1357321389; x=1358530989; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=mst/2Ftp+prIu66f9zl6H50654grgwB7YmkpjYaNlGk=; b=Zj/zHqRhfpoOo2Hc1OcrUiA9y083ycqg2VEnjrxHd7Ls9zJUnq3ApxoL qaM5RtbhFmd0xHfFM4jCmBSmc8QkVJOFmNNcEVYg+RLZC9tFTBAbu2CSf VJ2Ge9n7ihCq/ZKMV4UMQWWAFk7YL0x21zMvGaf9b91QV/UrHaPrxd4pn 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAGMU51CtJV2c/2dsb2JhbABFvU0Wc4IeAQEBAwEBAQE3NAsMBAIBCBEEAQEBChQJBycLFAkIAgQOBQiIBgUBDLRkjFIbg0dhA5IeOoRPjy2CdIFxNQ
X-IronPort-AV: E=Sophos;i="4.84,411,1355097600"; d="scan'208";a="158906649"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-2.cisco.com with ESMTP; 04 Jan 2013 17:42:53 +0000
Received: from xhc-aln-x06.cisco.com (xhc-aln-x06.cisco.com [173.36.12.80]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id r04HgrxO003567 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 4 Jan 2013 17:42:53 GMT
Received: from xmb-aln-x08.cisco.com ([169.254.3.169]) by xhc-aln-x06.cisco.com ([173.36.12.80]) with mapi id 14.02.0318.004; Fri, 4 Jan 2013 11:42:53 -0600
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Tom Kristensen (tomkrist)" <tomkrist@cisco.com>
Thread-Topic: [bfcpbis] I-D Action: draft-ietf-bfcpbis-rfc4582bis-07.txt
Thread-Index: AQHN3eub8/PbTNBNFU+3OIdQdkYCzZgghrKAgAAmeRCACuSB4IAOQA+A//+xUuA=
Date: Fri, 04 Jan 2013 17:42:53 +0000
Message-ID: <92B7E61ADAC1BB4F941F943788C08828046F4FBE@xmb-aln-x08.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> <50E6FC69.4060907@cisco.com>
In-Reply-To: <50E6FC69.4060907@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [171.68.16.69]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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 17:43:13 -0000
Please see inline. > -----Original Message----- > From: Tom Kristensen (tomkrist) > Sent: Friday, January 04, 2013 8:00 AM > To: Charles Eckel (eckelcu) > Cc: bfcpbis@ietf.org; 'Tom Kristensen' > Subject: Re: [bfcpbis] I-D Action: draft-ietf-bfcpbis-rfc4582bis-07.txt > > 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? Sorry for being so vague. In the html version of the draft (http://tools.ietf.org/html/draft-ietf-bfcpbis-rfc4582bis-07), clicking on any of the links for "[16]" take me to section 6.2 instead of to the appropriate reference in the references section. In fact, it takes me to another occurrence of a reference to [16] that for some reason is not displaying as a link. However, if I download the xml version of the draft and run xml2rfc on it myself, the resulting html version is fine. Perhaps it is a bug in the datatracker html file generator (e.g. it cannot handle a reference appearing at the start of a paragraph), and not an issue with your draft. Cheers, Charles > > 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 > >>
- [bfcpbis] I-D Action: draft-ietf-bfcpbis-rfc4582b… internet-drafts
- Re: [bfcpbis] I-D Action: draft-ietf-bfcpbis-rfc4… Tom Kristensen
- Re: [bfcpbis] I-D Action: draft-ietf-bfcpbis-rfc4… Charles Eckel (eckelcu)
- Re: [bfcpbis] I-D Action: draft-ietf-bfcpbis-rfc4… Charles Eckel (eckelcu)
- Re: [bfcpbis] I-D Action: draft-ietf-bfcpbis-rfc4… Tom Kristensen
- Re: [bfcpbis] I-D Action: draft-ietf-bfcpbis-rfc4… Charles Eckel (eckelcu)
- Re: [bfcpbis] I-D Action: draft-ietf-bfcpbis-rfc4… Tom Kristensen