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

Lou Berger <lberger@labn.net> Thu, 10 August 2006 14:56 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GBBxM-000146-4m; Thu, 10 Aug 2006 10:56:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GBAVl-0000Ro-3d for gen-art@ietf.org; Thu, 10 Aug 2006 09:23:45 -0400
Received: from esc71.midphase.com ([216.246.11.148]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GBAVi-0003TE-Qb for gen-art@ietf.org; Thu, 10 Aug 2006 09:23:45 -0400
Received: from esc71.midphase.com ([216.246.11.148] helo=LC1.labn.net) by esc71.midphase.com with esmtpa (Exim 4.52) id 1GBAVZ-0000Wk-0I; Thu, 10 Aug 2006 09:23:33 -0400
Message-Id: <7.0.1.0.2.20060810092200.0522d250@labn.net>
X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0
Date: Thu, 10 Aug 2006 09:23:13 -0400
To: Adrian Farrel <adrian@olddog.co.uk>
From: Lou Berger <lberger@labn.net>
In-Reply-To: <010601c6bbd6$7a891f00$9b849ed9@your029b8cecfe>
References: <F222151D3323874393F83102D614E05502B67141@CORPUSMX20A.corp.emc.com> <010601c6bbd6$7a891f00$9b849ed9@your029b8cecfe>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - esc71.midphase.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12]
X-AntiAbuse: Sender Address Domain - labn.net
X-Source:
X-Source-Args:
X-Source-Dir:
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
X-Mailman-Approved-At: Thu, 10 Aug 2006 10:56:18 -0400
Cc: rcallon@juniper.net, gen-art@ietf.org, Lou Berger <lberger@labn.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
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

Adrian,
         Thanks for the redirect.

David,
         Much thanks for the comments.  I'll review this tomorrow and 
follow up if I have any questions/issues to discuss.  (If not, I'll 
just update and submit the draft.)

Lou

At 01:04 PM 8/9/2006, Adrian Farrel wrote:

>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