[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Eliminating Appendices B and C



Andy... it is more that we do not want to be perceived as
promoting some tools over others in an RFC-to-be.

Thanks,
Bert 

> -----Original Message-----
> From: Andy Bierman [mailto:abierman@cisco.com]
> Sent: woensdag 13 augustus 2003 1:18
> To: C. M. Heard
> Cc: Mreview (E-mail)
> Subject: Re: Eliminating Appendices B and C
> 
> 
> At 03:52 PM 8/12/2003, C. M. Heard wrote:
> >Folks --
> >
> >Since we have decided to eliminate mention of specific MIB compilers
> >in the guidelines document, Appendices B and C will be cut, and any
> >references to them will be replaced by a pointer to an OPS web page
> >with pertinent information.  
> 
> I guess this is being done to avoid updating the RFC in case
> additional MIB compilers are listed in the future.  This seems
> like a lot of work to be politically correct.  I would be surprised
> if other MIB compilers of the same caliber as SMICng or smilint
> are ever added to the WEB site.
> 
> Andy
> 
> 
> >I've already sent out proposed text for
> >the affected parts of the MIB review checklist;  the only other
> >thing that I found requiring change was the last paragraph of
> >Section 4.9.  So I propose to change this old text:
> >
> >   Authors and reviewers may find it helpful to use tools 
> that can list
> >   the differences between two revisions of a MIB module.  
> One such tool
> >   is smidiff;  see Appendix B for more information.
> >
> >with this new text:
> >
> >   Authors and reviewers may find it helpful to use tools 
> that can list
> >   the differences between two revisions of a MIB module.  Please see
> >   http://www.ops.ietf.org/mib-review-tools.html for more 
> information.
> >
> >Any objections?  Please send text if so.
> >
> >Mike
> 
>