Re: DisplayString in guidelines 4.6.1.4 and Appendix D

[Andy Bierman <abierman@cisco.com>]

At 05:54 PM 2/11/2003 -0800, C. M. Heard wrote:
>[ in reply to comments/review <draft-ietf-ops-mib-review-guidelines-00.txt> ]
>
>On Fri, 7 Feb 2003, Wijnen, Bert (Bert) wrote:
>> - sect 4.6.1.4, end of page 14
>>   Mmm... the DisplayString is still current, although we
>>   rarely want to allow people to use it anymore. We prefer
>>   UTF-8 based TCs like SnmpAdminString.
>>   Do we want to make a note of that? I think it would be
>>   good. It is a thing that I see still far too often.
>
>This escaped my radar because I tend not to be as tuned-in to i18n
>issues as I ought to be.  I propose the following remedy:
>
>(a) remove DisplayString from the list of TCs mentioned in 4.6.1.4;
>(b) remove DisplayString from the list of "Commonly Used TCs" in
>    Appendix D, and add a second note under the list of TCs from
>    SNMPv2-TC:
>
>   Note 1.  InstancePointer is obsolete and MUST NOT be used.
>   Note 2.  DisplayString does not support internationalized text.
>            New MIB modules SHOULD use SnmpAdminString instead.
>
>Changes along these lines were what I suggested in my
>reply to Harrie Hazewinkel's comments that appeared on
>the mibs@ops.ietf.org list.
>
>Do these changes adequately address the concerns?

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.


>Mike

Andy