Re: draft-ops-endpoint-mib-06.txt example syntax?

[Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>]

>>>>> dperkins  writes:

dperkins> What I would do is the following:

dperkins> - specify an OBJECT clause naming a row

Does not work since the row is not-accessible. Same problem.

dperkins> - describe in the DESCRIPTION clause the rules
dperkins> for index values

The only thing one can do in order to be compliant with the current
SMIv2 rules is to describe things into the DESCRIPTION clause of the
compliance statement of the group statement.

dperkins> - I do not believe that any other approach can be made to
dperkins> cover all cases

Not sure I understand what you mean.

dperkins> - extending the SMI to handle a table that is indexed by an
dperkins> integer-based value only "works" for a table with a single
dperkins> index, and does not work with string-based indices, or OID
dperkins> based indices

There may be interesting combinations with variable length or implied
INDEX components. Can you give an example where a refinement would
break things?

I mean, a refinement is not allowed for OIDs (RFC 2578 section 9) and
an OctetString refinement may only "reduce" the size restrictions - I
think this does not affect the rules on how you encode the OctetString
in an instance identifier.

Maybe I am missing something. But anyway, this discussion is more
academic in nature - so its fine to leave this point open and stop
here.

/js

-- 
Juergen Schoenwaelder      Technical University Braunschweig
<schoenw@ibr.cs.tu-bs.de>  Dept. Operating Systems & Computer Networks
Phone: +49 531 391 3289    Bueltenweg 74/75, 38106 Braunschweig, Germany
Fax:   +49 531 391 5936    <URL:http://www.ibr.cs.tu-bs.de/~schoenw/>