HI,
I'm doing some cleanups of sme MIB modules. In them are many examples of tables that have a RowStatus column (with no restriction of values) and have MAX-ACCESS of "read-write" on the columns. I was expecting to see a warning that "read-create" should have been used instead of "read-write". If this warning is presently generated, I suggest that it be added.
Regards, /david t. perkins
On Mon, Nov 05, 2007 at 05:32:14PM -0800, David T. Perkins wrote:
I'm doing some cleanups of sme MIB modules. In them are many examples of tables that have a RowStatus column (with no restriction of values) and have MAX-ACCESS of "read-write" on the columns. I was expecting to see a warning that "read-create" should have been used instead of "read-write". If this warning is presently generated, I suggest that it be added.
There is no such check and I started to write code. But before continuing, I like to know that we agree what is an "illegal" combination of an access value and RowStatus enum subset. Lets try this:
- If a RowStatus column includes one of the enums 'createAndGo' or 'createAndWait', then the status must be read-create.
- If a RowStatus column includes the enum 'destroy', then it at least must be read-write.
Is this sufficient?
/js
HI,
Thanks for looking at this and parsing my broken request.
I agree with "read-create" when values can be 'createAndGo' or 'createAndWait'. I'm not sure that you need to check explicitly for 'destroy' for "read-write". That is, if the RowStatus is not "read-create", then it must be "read-write". Otherwise, I don't believe that use of RowStatus is appropriate with a "read-only", "accessible-for-notify", or "not-accessible" MAX-ACCESS value. (Note, there is a use case of value set of 'active' and 'notInService'. The value 'notReady' should only occur after 'createAndWait'. And of course, the most popular use case is the value set 'createAndGo', 'active', and 'destroy'.)
On Tue, 6 Nov 2007, Juergen Schoenwaelder wrote:
On Mon, Nov 05, 2007 at 05:32:14PM -0800, David T. Perkins wrote:
I'm doing some cleanups of sme MIB modules. In them are many examples of tables that have a RowStatus column (with no restriction of values) and have MAX-ACCESS of "read-write" on the columns. I was expecting to see a warning that "read-create" should have been used instead of "read-write". If this warning is presently generated, I suggest
^should have "not" here
that it be added.
There is no such check and I started to write code. But before continuing, I like to know that we agree what is an "illegal" combination of an access value and RowStatus enum subset. Lets try this:
- If a RowStatus column includes one of the enums 'createAndGo' or
'createAndWait', then the status must be read-create.
- If a RowStatus column includes the enum 'destroy', then it at least
must be read-write.
Is this sufficient?
/js
Regards, /david t. perkins
participants (2)
-
David T. Perkins -
Juergen Schoenwaelder