comment on draft-ietf-ops-mib-review-guidelines-03.txt (fwd)

["C. M. Heard" <heard@pobox.com>]

All,

Here is a timely suggestion from Keith McCloghrie.  Comments from
other MIB doctors please.

//cmh

---------- Forwarded message ----------
Date: Fri, 7 Jan 2005 10:30:45 -0800 (PST)
From: Keith McCloghrie <kzm@cisco.com>
To: heard@pobox.com
Cc: bwijnen@lucent.com, Keith McCloghrie <kzm@cisco.com>
Subject: comment on draft-ietf-ops-mib-review-guidelines-03.txt

Hi,

Do you think that this text:

  - If dynamic row creation and/or deletion by management applications
    is supported, then:

     - There MUST be one columnar object with a SYNTAX value of
       RowStatus [RFC2579] and a MAX-ACCESS value of read-create.  This
       object is called the status column for the conceptual row.  All
       other columnar objects MUST have a MAX-ACCESS value of read-
       create, read-only, accessible-for-notify, or not-accessible;  a
       MAX-ACCESS value of read-write is not allowed.

or some other text in draft-ietf-ops-mib-review-guidelines-03.txt
should mention the situation of one table which AUGMENTS another table,
in which only one of them should have a RowStatus, i.e., this is one
circumstance where it's legitimate to get read-create objects in a
table without a RowStatus.

Keith.