[Gen-art] Gen-ART review of draft-ietf-ospf-cap-09.txt
Black_David@emc.com Sun, 29 October 2006 17:39 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GeEd3-0003YY-5S; Sun, 29 Oct 2006 12:39:25 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GeEd1-0003VQ-Os for gen-art@ietf.org; Sun, 29 Oct 2006 12:39:23 -0500
Received: from mexforward.lss.emc.com ([128.222.32.20]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GeEcy-0004Zv-Ej for gen-art@ietf.org; Sun, 29 Oct 2006 12:39:23 -0500
Received: from mailhub.lss.emc.com (nagas.lss.emc.com [10.254.144.11]) by mexforward.lss.emc.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id k9THcudw027186; Sun, 29 Oct 2006 12:39:03 -0500 (EST)
Received: from corpussmtp3.corp.emc.com (corpussmtp3.corp.emc.com [10.254.64.53]) by mailhub.lss.emc.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id k9THbVi0026430; Sun, 29 Oct 2006 12:38:39 -0500 (EST)
From: Black_David@emc.com
Received: from CORPUSMX20A.corp.emc.com ([128.221.62.13]) by corpussmtp3.corp.emc.com with Microsoft SMTPSVC(6.0.3790.1830); Sun, 29 Oct 2006 12:38:32 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 29 Oct 2006 12:38:31 -0500
Message-ID: <F222151D3323874393F83102D614E05502B67647@CORPUSMX20A.corp.emc.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Gen-ART review of draft-ietf-ospf-cap-09.txt
Thread-Index: Acb7gQzwNMcuARedSFeg4mcjfq2p0w==
To: gen-art@ietf.org, acee@cisco.com, naiming@cisco.com, jpv@cisco.com, rahul@juniper.net, sshafferl@bridgeport-networks.com
X-OriginalArrivalTime: 29 Oct 2006 17:38:32.0372 (UTC) FILETIME=[0D92DF40:01C6FB81]
X-PMX-Version: 4.7.1.128075, Antispam-Engine: 2.4.0.264935, Antispam-Data: 2006.10.29.91433
X-PerlMx-Spam: Gauge=, SPAM=0%, Reason='EMC_BODY_1+ -3, EMC_FROM_0+ -2, NO_REAL_NAME 0, __C230066_P5 0, __CP_NOT_1 0, __CP_URI_IN_BODY 0, __CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __IMS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0'
X-Spam-Score: 0.2 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Cc: fenner@research.att.com, dube.rohit@gmail.com, Black_David@emc.com
Subject: [Gen-art] Gen-ART review of draft-ietf-ospf-cap-09.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
Errors-To: gen-art-bounces@ietf.org
I have been selected as the General Area Review Team (Gen-ART) reviewer for this draft (for background on Gen-ART, please see http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html). Please resolve these comments along with any other Last Call comments you may receive. Document: Extensions to OSPF for Advertising Optional Router Capabilities draft-ietf-ospf-cap-09.txt Reviewer: David L. Black Review Date: October 29, 2006 IETF LC Date: Ends November 6, 2006 Summary: This draft is basically ready for publication, but has nits that should be fixed before publication. Comments: This draft describes a small addition of bits to advertise optional capabilities to OSPF. All of the items in this review are editorial in nature. Section 3 - The use of "MUST" in the following sentence is not appropriate, as this is a design requirement, not a protocol requirement: Hence, discretion and sound engineering judgment MUST be adhered to when deciding whether newly proposed TLV(s) in support of a new application are advertised in the RI LSA or warrant the creation of an application specific LSA. A lower case "must" would suffice, but a rephrasing to emphasize the importance of this design concern in work on such TLVs would be better. Section 4: The security considerations statement that this document does not create any new security issues for the OSPF protocol is too narrow. The advertisement of capabilities may provide useful information to an attacker looking for a particular feature or vulnerability to attack. No new OSPF security countermeasures should be necessary, and it may be ok to refer discussion of this issue to the existing OSPF RFCs if it is adequately covered there, but the statement that there are no security considerations in the functional content of this draft is not correct. Section 5: Please tell IANA what the content of an entry is in each of the new registries - saying that their fields are the same as an existing registry is among the ways to do this. Thanks, --David ---------------------------------------------------- David L. Black, Senior Technologist EMC Corporation, 176 South St., Hopkinton, MA 01748 +1 (508) 293-7953 FAX: +1 (508) 293-7786 black_david@emc.com Mobile: +1 (978) 394-7754 ---------------------------------------------------- _______________________________________________ Gen-art mailing list Gen-art@ietf.org https://www1.ietf.org/mailman/listinfo/gen-art
- [Gen-art] Gen-ART review of draft-ietf-ospf-cap-0… Black_David
- [Gen-art] Re: Gen-ART review of draft-ietf-ospf-c… Acee Lindem