More on draft-ietf-ospf-mib-update-04

["Chapman, Ken" <KChapman@unispherenetworks.com>]

Folks,
I have one more issue with the OSPF-MIB.
I think it is appropriate to change MAX-ACCESS for ospfConfigErrorType,
ospfPacketType and ospfPacketSrc from "read-only" to 
"accessible-for-notify".
The reason I think it is justified is that when RFC1850 was published, it
was based on SMIv2 as defined by RFC1442 which did not have
"accessible-for-notify" as an option (wasn't introduced until RFC1902).
Therefore, this is only a "refinement", since I don't believe that any of
these attributes should/can be implemented to be accessed via a
Get/GetNext/GetBulk request.  If these are not changed then most/all
implementations will need to put something like the following in their
AGENT-CAPABILITIES statements:

    SUPPORTS        OSPF-TRAP-MIB
        INCLUDES  { ospfTrapControlGroup,
                    ospfTraps } -- group tbd
        VARIATION   ospfConfigErrorType
            SYNTAX      accessible-for-notify
            DESCRIPTION
                "Only provided within a notification."
        VARIATION   ospfPacketType
            SYNTAX      accessible-for-notify
            DESCRIPTION
                "Only provided within a notification."
        VARIATION   ospfPacketSrc
            SYNTAX      accessible-for-notify
            DESCRIPTION
                "Only provided within a notification."

Is this an acceptable change, since I don't think it will result in any
interoperability problems?

	Ken

++++++++++++++++++++++++++++++++++++++++++++++
Ken Chapman           Unisphere Networks, Inc.
Tel: +1-978-614-5322  5 Carlisle Drive
Fax: +1-978-692-9992  Westford, MA 01886
Email: KChapman@UnisphereNetworks.com
++++++++++++++++++++++++++++++++++++++++++++++