Re: [Fwd: Re: [RMONMIB] I-D ACTION:draft-ietf-rmonmib-raqmon-pdu- 08.txt]

["Randy Presuhn" <randy_presuhn@mindspring.com>]

Hi -

> From: "David T. Perkins" <dperkins@dsperkins.com>
> To: "Randy Presuhn" <randy_presuhn@mindspring.com>
> Cc: "Mreview (E-mail)" <mreview@ops.ietf.org>
> Sent: Friday, January 14, 2005 10:30 AM
> Subject: Re: [Fwd: Re: [RMONMIB] I-D ACTION:draft-ietf-rmonmib-raqmon-pdu- 08.txt]
....
> Because only table and row objects could have access
> of not-accessible, unless MIB compilers special cased
> these two objects and any other special objects
> created for new operations, then MIB compilers
> would generate an error message. To eliminate
> this problem, the new max-access value of
> "accessible-for-notify" was added. It was not
> added so that MIB designers could create
> definitions of objects whose existance was
> only at the time a notification was reported.
...

This is where my recollection of events differs from yours.
I recall no discussion that the use of accessible-for-notify
should be limited to those two OBJECT-TYPEs, and I
*do* recall discussion of other cases where it could be
useful.

Randy