[Gen-art] Gen-ART LC review of draft-ietf-ccamp-gmpls-segment-recovery-02
<Pasi.Eronen@nokia.com> Tue, 26 September 2006 14:07 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GSDae-0007wT-Dm; Tue, 26 Sep 2006 10:07:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GSDad-0007w2-Gg for gen-art@ietf.org; Tue, 26 Sep 2006 10:07:15 -0400
Received: from mgw-ext13.nokia.com ([131.228.20.172]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GSDWv-0002yd-03 for gen-art@ietf.org; Tue, 26 Sep 2006 10:03:26 -0400
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143]) by mgw-ext13.nokia.com (Switch-3.1.10/Switch-3.1.10) with ESMTP id k8QDr3Dr024314; Tue, 26 Sep 2006 17:02:27 +0300
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 26 Sep 2006 17:02:26 +0300
Received: from esebe105.NOE.Nokia.com ([172.21.143.53]) by esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 26 Sep 2006 17:02:25 +0300
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: Tue, 26 Sep 2006 17:02:28 +0300
Message-ID: <B356D8F434D20B40A8CEDAEC305A1F24032ECF8E@esebe105.NOE.Nokia.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Gen-ART LC review of draft-ietf-ccamp-gmpls-segment-recovery-02
Thread-Index: AcbhdGb0CTvywxPsSKu8FqxGmzEzVw==
From: Pasi.Eronen@nokia.com
To: gen-art@ietf.org, lberger@movaz.com, ibryskin@movaz.com, adrian@olddog.co.uk, dimitri.papadimitriou@alcatel.be, dbrungard@att.com, fenner@research.att.com, rcallon@juniper.net
X-OriginalArrivalTime: 26 Sep 2006 14:02:25.0548 (UTC) FILETIME=[651CCCC0:01C6E174]
X-Spam-Score: 1.3 (+)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: ccamp@ops.ietf.org
Subject: [Gen-art] Gen-ART LC review of draft-ietf-ccamp-gmpls-segment-recovery-02
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: draft-ietf-ccamp-gmpls-segment-recovery-02 Reviewer: Pasi Eronen Review Date: September 26, 2006 IETF LC Date: September 20, 2006 IESG Telechat date: not known yet Summary: This draft is basically ready for publication (as far as I can tell with my limited knowledge of GMPLS and RSVP-TE), but has nits that should be fixed before publication. First a disclaimer: I am not very familiar with GMPLS or RSVP-TE, so my comments are of rather general nature. - Since this document defines bits originally marked as "RESERVED" in [E2E-RECOVERY], it probably should be listed in "Updates:" list on the cover page. - Section 4.1 is a bit unclear on whether it's defining a new subobject or modifying something that already exists. Currently, the only explanation is "The protection subobject is not valid for use with the Explicit and Record Route objects and MUST NOT be included in those objects." It might be more understandable to start by explaining where it is valid, and where it can be included. - Section 9 (IANA considerations) is extremely unclear on what exactly IANA is supposed to do (e.g., in which registry assignments should be made, and what exactly is to be assigned there), and should be rewritten according to the guidelines in Section 5 of draft-narten-iana-considerations-rfc2434bis. Minor nits: - Section 2: "0-bit" (zero) probably should be "O-bit" (upper case O)? - Section 6.1: How will the RFC editor know what to replace "TBA" with? - References: [RFC2119] should be normative instead of informative. - References: Document cites RFC2205, but it's not listed here. - References: [FUNCT] and [TERM], [FRR] are now RFCs, so the references should be updated. - Idnits complains about long lines. Best regards, Pasi _______________________________________________ Gen-art mailing list Gen-art@ietf.org https://www1.ietf.org/mailman/listinfo/gen-art