Ira,
> The rest of you lurkers, PLEASE send meaningful technical
> criticisms (and NOT unsupported 'opinions') on the updates
> to clarify localization (or any of the other dozen recent
> updates). After some version of new Printer MIB text
> is submitted to the IETF/IESG in early July, it will get
> a LOT harder for PWG members to influence changes (ie,
> strictly technical comments will be entertained by the IETF).
Sorry but some of us lurkers are also trying
to get products to market.
But here is comment about the proposal on localization.
The proposal as presented in the pmib_062597.txt
has at least one serious flaw.
prtCoverDescription is specified as:
SYNTAX PrtCurrentLocaleDisplayStringTC
MAX-ACCESS read-only
PrtCurrentLocaleDisplayStringTC says:
a) whose dynamic locale ... prtGeneralCurrentLocalization
b) whose value (when updated by an SNMP Set-Request)...
c) whose value (when returned by an SNMP Get-
Response) shall be interpreted in this locale by the
management station.
I assume under a) the user/administrator
can change the value of prtGeneralCurrentLocalization.
But the printer is going to have the
prtCoverDescription specified in the language
established by the printer vendor. Thus the
description language may not match the
current localization. Thus the management station
can not depend on a being true.
I assume b) does not apply to this description
because the description can not be set.
I assume c) does not apply because the management
station may be running a different language than
the description was encoded in by the vendor.
Have I missed something here?
How many more problems exist with changes as proposed
in pmib_062597.txt?
From my view point the entire localization proposal needs
be be throughly reviewed or dropped. Thus we have
two choices, either postpone the draft submission
and make all the needed changes or take out
PrtCurrentLocaleDisplayStringTC ... and thus revert
back to the localization as specified in:
draft-ietf-printmib-mib-info-02.txt
I vote for the later.
Chuck Adams