[OPSAWG] AD review of draft-ietf-opsawg-syslog-alarm-02.txt

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Wed, 22 July 2009 14:15 UTC

Return-Path: <dromasca@avaya.com>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 016733A67EA for <opsawg@core3.amsl.com>; Wed, 22 Jul 2009 07:15:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.176
X-Spam-Level:
X-Spam-Status: No, score=-2.176 tagged_above=-999 required=5 tests=[AWL=0.423, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LCzt+k0eipeg for <opsawg@core3.amsl.com>; Wed, 22 Jul 2009 07:15:32 -0700 (PDT)
Received: from nj300815-nj-outbound.net.avaya.com (nj300815-nj-outbound.net.avaya.com [198.152.12.100]) by core3.amsl.com (Postfix) with ESMTP id C248F3A67DA for <opsawg@ietf.org>; Wed, 22 Jul 2009 07:15:31 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.43,247,1246852800"; d="scan'208";a="167898231"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by nj300815-nj-outbound.net.avaya.com with ESMTP; 22 Jul 2009 10:14:09 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by co300216-co-erhwest-out.avaya.com with ESMTP; 22 Jul 2009 10:14:09 -0400
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: Wed, 22 Jul 2009 16:13:51 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0401893038@307622ANEX5.global.avaya.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: AD review of draft-ietf-opsawg-syslog-alarm-02.txt
thread-index: AcoK1qMohVhl+Ht6RseID6w/wgIu0g==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: opsawg@ietf.org
Subject: [OPSAWG] AD review of draft-ietf-opsawg-syslog-alarm-02.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jul 2009 14:15:33 -0000

I have performed the AD review of draft-ietf-opsawg-syslog-alarm-02.txt.
I believe that this document is clear and stable enough to proceed to
the IETF Last Call. Please consider the comments below together with the
other IETF Last Call comments. 

1. Idnits complains about 

>  ** Obsolete normative reference: RFC 1738 (Obsoleted by RFC 4248, RFC
4266) 

This seems intentional as in Section 3.6 I found the following: 

> The value of this field MUST conform to the URI definition in
   [RFC1738] and its updates.

I am wondering however what is the reason for this.

2. References for RFC 3877, X.733, X.736 should be inserted at the first
occurrence in the Introduction section (it is only in Abstract it's
recommended that they are avoided)

3. in section 4 s/[syslog]/[RFC5424]/

4. readers of the IANA considerations section would appreciate to
mention that the registry which is referred is the syslog parameters
register. Thus may be obvious, but yet the word syslog does not figure
in the section. 

Thanks and Regards,

Dan