[Gen-art] Gen-ART LC Review of draft-ietf-vrrp-unified-mib-09

Ben Campbell <ben@nostrum.com> Tue, 10 May 2011 21:57 UTC

Return-Path: <ben@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 574D6E08F9; Tue, 10 May 2011 14:57:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.445
X-Spam-Level:
X-Spam-Status: No, score=-102.445 tagged_above=-999 required=5 tests=[AWL=0.155, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rpESOFxdWkMM; Tue, 10 May 2011 14:57:07 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id D1263E06D9; Tue, 10 May 2011 14:57:06 -0700 (PDT)
Received: from [10.0.1.6] (cpe-76-183-178-106.tx.res.rr.com [76.183.178.106]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id p4ALjJ1x026758 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 10 May 2011 16:45:20 -0500 (CDT) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 10 May 2011 16:45:19 -0500
Message-Id: <2DE1D538-CD0B-4076-BAB3-85C4AB2800C0@nostrum.com>
To: draft-ietf-vrrp-unified-mib.all@tools.ietf.org
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Received-SPF: pass (nostrum.com: 76.183.178.106 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The IETF <ietf@ietf.org>
Subject: [Gen-art] Gen-ART LC Review of draft-ietf-vrrp-unified-mib-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 May 2011 21:57:08 -0000

I am the assigned Gen-ART reviewer for this draft. For background on Gen-ART, please see the FAQ at <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments you may receive.

Document: draft-ietf-vrrp-unified-mib-09
Reviewer: Ben Campbell
Review Date: 2011-05-10
IETF LC End Date:2011-05-11
IESG Telechat date: (if known)

Summary: This draft is ready for publication as a draft standard. I have a few editorial comments that might be worth considering, but probably should not block publication.

Note: I am inexpert both in MIB definitions and in VRRP. I assume this has (or will be) reviewed by experts in both.

Major issues:

None

Minor issues:

None

Nits/editorial comments:

-- idnits complains about an obsolete normative reference: Obsolete normative reference: RFC 2338 (Obsoleted by RFC 3768)

I see why you have the 2338 reference--but does it need to be normative?

-- General: 

There's some odd formatting--no space between page header and body for pages 2 on. (I reviewed the PDF version, not sure if the TXT version is the same or if this is a PDF rendering issue.)

Does it make sense to use 2119 language in MIB object descriptive text? That will often show up outside the context of the draft, and therefore without the 2119 language definitions. I don't know what the convention is--I just point it out so others more used to MIBs can think about it.

-- section 3:

You've got the 2119 boilerplate twice.

-- section 7:

Please put blank lines between list entries

-- section 9, "vrrpv3OperationsPrimaryIpAddr"

Is "primary" the correct term here? Seems like  addresses would be "master" and backup, or primary and secondary. Master and primary sounds odd.

-- "vrrpv3OperationsUpTime"

It's probably worth describing the time interval unit in the text, as you did for the previous interval in centiseconds.

-- "vrrpv3OperationsRowStatus"

The description talks about how to use the RowStatus variable, but does not describe what it represents in the first place.

--"vrrpv3StatisticsProtoErrReason"

No discontinuity comment?

-- "vrrpv3StatisticsRefreshRate"
s/milli-seconds/milliseconds

Also, You might want to mention the time interval unit in the description.