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

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

>>>>> Tim Jenkins writes:

Tim> However, changing the statements to (substituting INTEGER for
Tim> InetAddressType in each)

[...]

Tim> works for both compilers.

The funny thing here is that both compilers accept

    OBJECT  peerAddress
    SYNTAX  InetAddress (SIZE(4|16))

as valid while

    OBJECT  peerAddressType
    SYNTAX  InetAddressType { ipv4(1), ipv6(2) }

is rejected as invalid. That is, you can add a size restriction for a
TC by using the TC name but you can't refine the list of enumerated
values for a TC by using the TC name. Sounds a bit odd.

Tim> I'm starting to wonder if the indirection of the SYNTAX from
Tim> INTEGER via the textual convention InetAddressType is going to be
Tim> too confusing to compilers, and it should be avoided.

Lets see if Dave Perkins has something to say about this. (I can
certainly make mosy accept it - libsmi already does.)

While writing a real MIB around the fragment in the ID, I also
discovered another interesting question. The MIB suggests to define a
refinement in a compliance statement for an INDEX object which has a
max access of not-accessible. Using SMICng I did run into some trouble
because

(a) it insists that the object to be refined is a member of an
    OBJECT-GROUP (I guess because of RFC 2580 section 5.4.3),
    and

(b) it does not allow to put a not-accessible object into an
    OBJECT-GROUP (I guess because of RFC 2580 section 3.1).

Which basically means that the SMIv2 does not allow to refine the
syntax for objects that are not-accessible because they are INDEX
objects. I do not think this was the intention of the SMIv2. Looks
like the rule in RFC 2580 section 3.1 is over ambitious.

Dave, Keith, any comments on this?

/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/>