RE: DisplayString in guidelines 4.6.1.4 and Appendix D

[Andy Bierman <abierman@cisco.com>]

At 02:15 PM 2/12/2003 +0100, Wijnen, Bert (Bert) wrote:
>> I know I mentioned this before, but sometimes a lot of
>> guidelines and rules have to ignored when the MIB under
>> review is an SMIv1 to SMIv2 conversion.  I know that
>> doesn't come up in IETF reviews very often, but it
>> still happens from time to time in Cisco reviews. 
>> 
>> Since we (at Cisco) plan to enforce the guidelines
>> in this document for our Enterprise MIB reviews, I
>> think we should account for SMIv1 -> SMIv2 conversions.
>> 
>Mmmm... what a sad story. Here we are, 7 or 8 years after
>IETF made writing MIB modules SMIv2 mandatory. And we're
>still faced with "lots of" SMIv1->SMIv2 stuff?
>
>Will we ever make progress?

sure.  These aren't new MIBs in SMIv1.  As I pointed out
before, most of our MIB reviews are additions to existing
MIB modules.  When an older SMIv1 MIB gets modified, it
has to be converted to SMIv2.

On the other hand, we also publish all our MIBs in SMIv2
and SMIv1 format, because we have customers who are still
using SMIv1 tools.

>Bert
>> 
>> >Mike
>> 
>> Andy
>> 
>> 

Andy