[RADIR] draft-narten-radir-problem-statement-05 editorials
Alfred Hönes <ah@TR-Sys.de> Mon, 27 September 2010 16:29 UTC
Return-Path: <A.Hoenes@TR-Sys.de>
X-Original-To: radir@core3.amsl.com
Delivered-To: radir@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9E8953A6C27 for <radir@core3.amsl.com>; Mon, 27 Sep 2010 09:29:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -96.797
X-Spam-Level:
X-Spam-Status: No, score=-96.797 tagged_above=-999 required=5 tests=[AWL=-0.648, BAYES_50=0.001, CHARSET_FARAWAY_HEADER=3.2, HELO_EQ_DE=0.35, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QOkP8BxxFevd for <radir@core3.amsl.com>; Mon, 27 Sep 2010 09:29:07 -0700 (PDT)
Received: from TR-Sys.de (gateway.tr-sys.de [213.178.172.147]) by core3.amsl.com (Postfix) with ESMTP id 2D0863A6C0B for <radir@ietf.org>; Mon, 27 Sep 2010 09:29:05 -0700 (PDT)
Received: from ZEUS.TR-Sys.de by w. with ESMTP ($Revision: 1.37.109.26 $/16.3.2) id AA232514835; Mon, 27 Sep 2010 18:27:15 +0200
Received: (from ah@localhost) by z.TR-Sys.de (8.9.3 (PHNE_25183)/8.7.3) id SAA06446; Mon, 27 Sep 2010 18:27:13 +0200 (MESZ)
From: Alfred Hönes <ah@TR-Sys.de>
Message-Id: <201009271627.SAA06446@TR-Sys.de>
To: narten@us.ibm.com, radir@ietf.org
Date: Mon, 27 Sep 2010 18:27:13 +0200
X-Mailer: ELM [$Revision: 1.17.214.3 $]
Mime-Version: 1.0
Content-Type: text/plain; charset="hp-roman8"
Content-Transfer-Encoding: 8bit
X-Mailman-Approved-At: Tue, 28 Sep 2010 08:45:33 -0700
Subject: [RADIR] draft-narten-radir-problem-statement-05 editorials
X-BeenThere: radir@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Routing and Addressing Directorate <radir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/radir>, <mailto:radir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/radir>
List-Post: <mailto:radir@ietf.org>
List-Help: <mailto:radir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/radir>, <mailto:radir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Sep 2010 16:29:08 -0000
Hello, the recent submission of several drafts that came on my radar and referenced draft-narten-radir-problem-statement-05 has caused me to also review that memo, although it formally now has expired -- I guess/hope that it will be pursued further and that the below editorial comments will be still useful. (I found that likely my age-old comments on an early version have been missed, but that essentially doesn't matter.) Overall, that memo seems to be in a good shape, and I only want to mention the nits below. (1) Section 3, first bullet Apparently, "increasing" is missing in the second line and should be added as follows: o The number of individual prefixes that are being propagated into | the DFZ over time has been and continues to increase at a faster- than-linear rate. [...] --- o The number of individual prefixes that are being propagated into | the DFZ over time has been increasing and continues to increase at a faster-than-linear rate. [...] (2) Section 3, last para I see no need for the hyphen in "upper-bound". (3) Section 3.3, 1st para Missing "to" : Today's growth pattern is influenced by the scaling properties of the current routing system. If the routing system had better scaling | properties, we would be able support and enable more widespread usage of such services as multihoming and traffic engineering. [...] --- Today's growth pattern is influenced by the scaling properties of the current routing system. If the routing system had better scaling | properties, we would be able to support and enable more widespread usage of such services as multihoming and traffic engineering. [...] (4) Section 3.3, 2nd para Missing indefinite article (IMO): ... there is misalignment of incentives ... --- ... there is a misalignment of incentives ... (5) Section 4.1, 2nd para AFAICT, "IGP" stands for "Interior Gateway Protocol", so please change "internal interial gateway protocol" to this term. Maybe you might want to say: ... by internally using Interior Gateway Protocol (IGP) metrics ... (6) Section 4.1, punctuation in bullets Since all 3 bullets start with a lowercase initial, I suggest to add a trailing comma or semicolon to the first two bullets, and a trailing period to the last bullet. (7) Section 4.4, 1st para -- typo s/unaggragatable/unaggregatable/ ^ ^ (8) Section 4.5, last para This paragraph contains two spurious words, apparently unadvertently left in there during the last edit. Please correct: | In IPv6, its vast address space allows for a much a greater emphasis vvvvvvvvvvvvv ^^^^^^^^ | to be placed placed on preserving future aggregation than was possible in IPv4. --- | In IPv6, its vast address space allows for a much greater emphasis to | be placed on preserving future aggregation than was possible in IPv4. (9) Section 4.6, last para I suggest to replace the two instances of "Internet table" by "Internet routing table". (In case of a ducument update, you also might want to use more current figures from the routing table statistics, throughout the section.) (10) Section 4.7, 2nd para I suggest to use hyphenation: s/fine grained control of traffic/fine-grained control of traffic/ ^ ^ (11) Section 5.1 There is a singular/plural mismatch: As the number of possible paths increase, ... --- v As the number of possible paths increases, ... (12) Section 5.4.3, 2nd para In the last sentence, I suggest to replace the comma in front of "hence" by a semicolon: [...] Finally, leaking routes unnecessarily does not generally harm those responsible for the | misconfiguration, hence, there may be little incentive to change such behavior. --- ^ [...] Finally, leaking routes unnecessarily does not generally harm those responsible for the | misconfiguration; hence, there may be little incentive to change such behavior. (13) Section 5.5 In a similarly structured sentence, I suggest adding a comma: [...] | own prefix directly into the global routing system; instead their address block would be covered by their provider's aggregate. [...] --- v | own prefix directly into the global routing system; instead, their address block would be covered by their provider's aggregate. [...] (14) Section 6, punctuation in bullets All the bullets in Section 6 start with a capital, but only some are terminated wit a trailing period. I suggest to add trailing periods to the remaining bullets: 2A, 3, 4, 6 . (15) Section 6, last para There is another singular/plural mismatch: s/via a care-of addresses./via care-of addresses./ ^^^ ^ (16) Section 9, last line I strongly suspect that the first email addres given should _not_ be "rrg@iab.org" , but instead "rrg@irtf.org" . (17) Section 10 For completeness, I'd like to point out that RFC 3344 will soon be obsoleted by RFC 5944; so please pay attention on the RFC Editor queue output and, if appropriate, update the reference accordingly. Kind regards, Alfred Hönes. -- +------------------------+--------------------------------------------+ | TR-Sys Alfred Hoenes | Alfred Hoenes Dipl.-Math., Dipl.-Phys. | | Gerlinger Strasse 12 | Phone: (+49)7156/9635-0, Fax: -18 | | D-71254 Ditzingen | E-Mail: ah@TR-Sys.de | +------------------------+--------------------------------------------+
- [RADIR] draft-narten-radir-problem-statement-05 e… Alfred Hönes