[Adslmib] Non-technical comments on draft-ietf-adslmib-vdsl-ext-mcm-02.txt
"Randy Presuhn" <randy_presuhn@mindspring.com> Wed, 24 March 2004 06:05 UTC
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA28981 for <adslmib-archive@odin.ietf.org>; Wed, 24 Mar 2004 01:05:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B61VX-0007hb-QL for adslmib-archive@odin.ietf.org; Wed, 24 Mar 2004 01:04:55 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i2O64tP5029603 for adslmib-archive@odin.ietf.org; Wed, 24 Mar 2004 01:04:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B61VX-0007hO-N5 for adslmib-web-archive@optimus.ietf.org; Wed, 24 Mar 2004 01:04:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA28934 for <adslmib-web-archive@ietf.org>; Wed, 24 Mar 2004 01:04:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B61VU-0002yi-00 for adslmib-web-archive@ietf.org; Wed, 24 Mar 2004 01:04:52 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B61Ua-0002mx-00 for adslmib-web-archive@ietf.org; Wed, 24 Mar 2004 01:03:56 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1B61Tf-0002cF-00 for adslmib-web-archive@ietf.org; Wed, 24 Mar 2004 01:02:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B61Th-0007Si-9t; Wed, 24 Mar 2004 01:03:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B61Td-0007SG-Ny for adslmib@optimus.ietf.org; Wed, 24 Mar 2004 01:02:57 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA28861 for <adslmib@ietf.org>; Wed, 24 Mar 2004 01:02:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B61Ta-0002bP-00 for adslmib@ietf.org; Wed, 24 Mar 2004 01:02:55 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B61Sm-0002Qh-00 for adslmib@ietf.org; Wed, 24 Mar 2004 01:02:05 -0500
Received: from avocet.mail.pas.earthlink.net ([207.217.120.50]) by ietf-mx with esmtp (Exim 4.12) id 1B61S6-0002G4-00 for adslmib@ietf.org; Wed, 24 Mar 2004 01:01:22 -0500
Received: from h-68-164-79-127.snvacaid.dynamic.covad.net ([68.164.79.127] helo=oemcomputer) by avocet.mail.pas.earthlink.net with smtp (Exim 3.33 #1) id 1B61S1-00059E-00 for adslmib@ietf.org; Tue, 23 Mar 2004 22:01:17 -0800
Message-ID: <000c01c41165$c9addbc0$7f1afea9@oemcomputer>
From: Randy Presuhn <randy_presuhn@mindspring.com>
To: adslmib@ietf.org
References: <AD2F581BD7340A4C908AF1AFB066EA3B0CA3D2@ntah901e.savan.com>
Date: Tue, 23 Mar 2004 22:03:53 -0800
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Subject: [Adslmib] Non-technical comments on draft-ietf-adslmib-vdsl-ext-mcm-02.txt
Sender: adslmib-admin@ietf.org
Errors-To: adslmib-admin@ietf.org
X-BeenThere: adslmib@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/adslmib>, <mailto:adslmib-request@ietf.org?subject=unsubscribe>
List-Id: ADSLMIB <adslmib.ietf.org>
List-Post: <mailto:adslmib@ietf.org>
List-Help: <mailto:adslmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/adslmib>, <mailto:adslmib-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Hi - A few non-technical comments on draft-ietf-adslmib-vdsl-ext-mcm-02.txt: Purely mechanical: 0x09 at line 1 position 1 trailing blanks make line 75 too long (74 characters) Editorial: - sometimes has only one space following period at the end of a sentence. should be two. - Some abbreviations not expanded on first use: ETSI, ITU, DSLF, VACM, PMD, and SCM - section 2.1: "MIBS" -> "MIBs" - section 2.3: "monitioring" -> "monitoring" - indentation oddities: section 6.1: DSLTFR057, RFC2580, RFC2586 section 7 is indented one character position more than others - the order of the following sections deviates from the order recommended in draft-rfc-editor-rfc2223bis-07.txt: |5. Security Considerations ....................................... 17 |6. References .................................................... 18 |6.1 Normative References .......................................... 18 |6.2 Informative References ........................................ 19 |7. Acknowledgements .............................................. 19 - section 6.1: punctuation is inconsistent. for example: old: [ETSI2701] ETSI TS 101 270-1 V1.2.1 "Transmission and Multiplexing new: [ETSI2701] ETSI TS 101 270-1 V1.2.1, "Transmission and Multiplexing old: [ETSI2702] ETSI TS 101 270-2 V1.1.1 "Transmission and Multiplexing new: [ETSI2702] ETSI TS 101 270-2 V1.1.1, "Transmission and Multiplexing old: [ITU9931] ITU-T G.993.1 "Very-high-speed digital subscriber line new: [ITU9931] ITU-T G.993.1, "Very-high-speed digital subscriber line old: J., Rose, M. and S. Waldbusser, "Structure of new: J., Rose, M. and S. Waldbusser, "Structure of old: J., Rose, M. and S. Waldbusser, "Textual Conventions new: J., Rose, M. and S. Waldbusser, "Textual Conventions old: [RFC2856] Bierman, A., McCloghrie, K., and R. Presuhn, "Textual new: [RFC2856] Bierman, A., McCloghrie, K. and R. Presuhn, "Textual old: [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces new: [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces old: [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An new: [RFC3411] Harrington, D., Presuhn, R. and B. Wijnen, "An old: [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, new: [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, Although the document uses "MUST NOT" , "RECOMMENDED", "NOT RECOMMENDED" and "SHOULD" , there is no reference to RFC 2119. The second "SHOULD" in section 2.4 should be "should", or, better still, the sentence should be re-phrased to remove the word. Randy _______________________________________________ Adslmib mailing list Adslmib@ietf.org https://www1.ietf.org/mailman/listinfo/adslmib
- [Adslmib] VDSL Line Code Specific Extension MIBS Menachem.Dodge
- [Adslmib] Non-technical comments on draft-ietf-ad… Randy Presuhn