[Gen-art] Re: Gen ART review of draft-ietf-ccamp-gmpls-alarm-spec-03.txt

"Adrian Farrel" <adrian@olddog.co.uk> Wed, 09 August 2006 17:09 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GArYO-0002Ht-9H; Wed, 09 Aug 2006 13:09:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GArYM-0002Hm-Gf for gen-art@ietf.org; Wed, 09 Aug 2006 13:09:10 -0400
Received: from mail2.noc.data.net.uk ([80.68.34.49]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GArYJ-0003QW-VH for gen-art@ietf.org; Wed, 09 Aug 2006 13:09:10 -0400
Received: from 57-99.dsl.data.net.uk ([80.68.57.99] helo=cortex.aria-networks.com) by mail2.noc.data.net.uk with esmtp (Exim 3.36 #1) id 1GArYF-00076w-00 for gen-art@ietf.org; Wed, 09 Aug 2006 18:09:04 +0100
Received: from your029b8cecfe ([217.158.132.84] RDNS failed) by cortex.aria-networks.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 9 Aug 2006 18:09:03 +0100
Message-ID: <010601c6bbd6$7a891f00$9b849ed9@your029b8cecfe>
From: Adrian Farrel <adrian@olddog.co.uk>
To: Black_David@emc.com, gen-art@ietf.org, Lou Berger <lberger@labn.net>
References: <F222151D3323874393F83102D614E05502B67141@CORPUSMX20A.corp.emc.com>
Date: Wed, 09 Aug 2006 18:04:39 +0100
Organization: Old Dog Consulting
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="iso-8859-1"; reply-type="original"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-OriginalArrivalTime: 09 Aug 2006 17:09:05.0534 (UTC) FILETIME=[84FF09E0:01C6BBD6]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Cc: rcallon@juniper.net, Black_David@emc.com, dbrungard@att.com
Subject: [Gen-art] Re: Gen ART review of draft-ietf-ccamp-gmpls-alarm-spec-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
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

Forwarding to Lou's new email address.

Adrian
----- Original Message ----- 
From: <Black_David@emc.com>
To: <gen-art@ietf.org>; <lberger@movaz.com>
Cc: <rcallon@juniper.net>; <adrian@olddog.co.uk>; <dbrungard@att.com>; 
<Black_David@emc.com>
Sent: Wednesday, August 09, 2006 4:59 PM
Subject: Gen ART review of draft-ietf-ccamp-gmpls-alarm-spec-03.txt


> Lou,
>
> I am the assigned Gen-ART reviewer for
> draft-ietf-ccamp-gmpls-alarm-spec-03.txt .
>
> For background on Gen-ART, please see the FAQ at
> <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.
>
> This draft is basically ready for publication, but has nits
> that should be fixed before publication.
>
> The draft is generally well-written and to the point.  All
> of these comments are minor.
> - Section 3.1.  Say why the two-leading-one-bits form is used
> for ALARM_SPEC objects in this section in addition to
> Section 3.1.4.  It would be ok to move the text from Section
> 3.1.4 up into Section 3.1.  Also, if there's a good explanation
> for why C-Type 1 and 2 are Reserved, that explanation should
> be added.
> - Section 3.1.1 should give guidance for and examples of appropriate
> use of Severity values.
> - Section 3.1.2 has a number of SHOULDs and SHOULD NOTs.  There needs
> to be an explanation of why these strong recommendations are
> being made (which would imply consequences of not following
> the recommendations) and/or a description of what goes wrong
> when they're not followed.  The overall explanation appears
> to be a desire to supply enough basic information to allow
> the recipient to understand the alarm (this info can be quite
> important as the recipient may be dealing with a crisis of
> which the alarm is a part).  The "MAY" for the ref
> count TLV needs to be explained  (why would it be used?).
> - Section 3.1.2 on p10 discusses adding alarm objects to the
> "state of LSPs".  The quoted phrase needs to be defined -
> I think the addition is to the LSP state communicated by
> RSVP Path and Resv messages.
>
> 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