RE: radius dynauth client/server mibs structure

["Wijnen, Bert (Bert)" <bwijnen@lucent.com>]

Inline

> -----Original Message-----
> From: Nelson, David [mailto:dnelson@enterasys.com]
> Sent: Friday, March 03, 2006 16:45
> To: Wijnen, Bert (Bert); Nagi Reddy Jonnala (njonnala);
> j.schoenwaelder@iu-bremen.de; radiusext@ops.ietf.org
> Subject: RE: radius dynauth client/server mibs structure
> 
> 
> Bert Wijnen writes...
> 
> > The disadvantage of not doing so is in the future when 
> adding scalars
> > and thing not having grouped as nicely and so more complexity.
> 
> In practice, does this inconvenient grouping really affect any SNMP
> applications in a user-visible way, except for MIB-walk and 
> MIB-browser applications?
> 

I know from experience that it made it easier for me to implement the
MIB at the agent side. Of course that could have been caused just by my
owb design, and other may not have trouble with it at all.

I am somewhat less familiar with mgmt apps.

> > This is not a blocking comment, just another MIB-type person believing
> > that the change would be real EASY now, and it will certainly make
> > things cleaner/easier in the future.
> 
> It certainly makes the MIB _document_ neater.
> 

And rigth now (at FIRST or INITIAL version) it is EASY to make the change
to make something neat. Later you cannot correct it without possibly
deprecating/obsoleteing existing and adding new objects.

Oh well.

Bert

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>