RE: Redundant objects

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

In general I discuourage people to create redundant MIB
objects. But ... if they have good reasons, I think we
should try to understand them and make them document it
in the MIB documents, preferebaly in the "duplicate" object
DESCRIPTION clause.

It might be good to say something about it in our guidelines 
doc as well.

Thanks,
Bert 

> -----Original Message-----
> From: Dave Thaler [mailto:dthaler@windows.microsoft.com]
> Sent: woensdag 22 oktober 2003 1:34
> To: Randy Presuhn
> Cc: Mreview (E-mail)
> Subject: RE: Redundant objects
> 
> 
> Thanks for the pointer Randy.
> 
> However that text can be read as just saying it was the
> criteria used during the design of that MIB.  It doesn't 
> really say this is the OPS-area policy for all MIBs,
> nor does it touch on the cross-MIB redundant objects
> issue.  It's better than nothing though :)
> 
> -Dave
> 
> > -----Original Message-----
> > From: owner-mreview@ops.ietf.org [mailto:owner-mreview@ops.ietf.org]
> On
> > Behalf Of Randy Presuhn
> > Sent: Tuesday, October 21, 2003 2:48 PM
> > To: Mreview (E-mail)
> > Subject: Re: Redundant objects
> > 
> > Hi -
> > 
> > > From: "Dave Thaler" <dthaler@windows.microsoft.com>
> > > To: "Mreview (E-mail)" <mreview@ops.ietf.org>
> > > Sent: Tuesday, October 21, 2003 1:30 PM
> > > Subject: Redundant objects
> > >
> > 
> > > I'm wondering if there is any "official" policy on
> > > redundant objects.  I don't see any mention in the
> > > guidelines for MIB reviewers.  I know there are
> > > published books from various folks that mention
> > > this issue, but so far I haven't found if there's
> > > some IETF doc that does.
> > ...
> > 
> > The guideline is mentioned in RFC 1066 section 3 point (5).
> > 
> > It's been around for a while.
> > 
> > Randy
>