Marty> I've seen behavior in some other managers which I really don't
Marty> understand (I think its doing scanning of the strings...if all
Marty> bytes pass isprint() and it ends in a NULL, it treats it as an
Marty> ascii string, Otherwise its displays hex bytes...
I think that guessing the format is the wrong solution. Look for
example at a MAC address in an OCTET STRING. Some of the MAC addresses
will actually come out as a character string, others will be shown as
hex bytes.
We have suitable mechanisms to define proper mappings within the
SMIv2. There is IMHO no excuse for not using them.
Marty> I understand DisplayString is deprecated, and Utf8String should
Marty> be used in future mibs...
DisplayString is not deprecated. However, an object type definition
which holds human readable strings will not be accepted by the IESG
anymore unless it supports UTF8. (There are several cases where a
DisplayString still makes sense, e.g. for DNS names.)
Juergen
-- Juergen Schoenwaelder schoenw@ibr.cs.tu-bs.de http://www.cs.tu-bs.de/~schoenw Technical University Braunschweig, Dept. Operating Systems & Computer Networks Bueltenweg 74/75, 38106 Braunschweig, Germany. (Tel. +49 531 / 391 3289)-- !! This message is brought to you via the `tkined & scotty' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <tkined-request@ibr.cs.tu-bs.de>. !! See http://wwwsnmp.cs.utwente.nl/~schoenw/scotty/ for more information.