RE: WG Last call announcement on draft-ietf-sming-reqs-02.txt

[Michael Kirkham <mikek@muonics.com>]

I don't think so.  It's related, but the wording of 4.1.5 only pertains to
attributes as a whole (a la MAX-ACCESS/PIB-ACCESS), with no granularity at
the refinement level (a la SMIv2 WRITE-SYNTAX, albeit this only applies to
"minimum" for conformance).  As such it pretty much just spells out a
requirement that SMIng have the same capabilities w.r.t. accessibility as
current SMI/SPPI.  This level of granularity would be a new capability,
allowing two things:

1. Specifying the applicability of certain values/ranges to certain
operations on the attribute to be specified in a parseable manner (e.g.,
those read-write/read-only/read-write semantics of RowStatus/KeyChange
etc. can currently only be specified within the non-parseable description
field).

2. Specifying such applicability within typedefs/textual conventions so
that the rules can be inherited (e.g. RowStatus/KeyChange are textual
conventions, so you'd want to be able to specify the rules there -- as
they are now, but in a parseable manner -- so that you don't need to do so
within every definition of an attribute derived from one of these types).

It's possible that it could be done as a merging of the access and syntax
fields, such that the accessibility range for an attribute could be
derived from the accessibility of the values/subranges.  Though that might
lead to needless complexity in some cases where you're wanting to apply an
access restriction to the entire set of values/ranges..  Depends on how
it's done.

On Thu, 28 Jun 2001, Jason, Jamie wrote:

> Michael,
>
> is this covered by requirement 4.1.5 (Accessibility)?
>
> Jamie
>
> > Here are just a few SNMP objects/derived types with peculiar semantics
> > about what values can be read or written.  Currently, such
> > constraints can
> > be and are only represented by text within the DESCRIPTION
> > field. The list
> > is not exclusive (there likely are and will be others).
> >
> >     *RowStatus
> >         active(1) - read-write
> >         notInService(2) - read-write
> >         notReady(3) - read-write
> >         createAndGo(4) - write-only
> >         createAndWait(5) - write-only
> >         destroy(6) - write-only
> >     tcpConnState
> >         deleteTCB(12) - write-only
> >         all others    - read-only
> >     *KeyChange
> >         SIZE(0)     - read-only
> >         SIZE(other) - write-only
>
>