<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;color:navy'>I would like to back track from my previous statement that a
unique media key seems necessary. Instead I would like to restate the
problem(s). <o:p></o:p></span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;color:navy'>1) Print jobs need to be able to uniquely or at least
unambiguously identify the size and type of media that should be used.<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;color:navy'>I&#8217;m not sure &#8220;unique&#8221; is achievable. You
listed color/type/coating, but customers could also want to specify just about
any media type attribute: weight, grain, brightness, manufacturer, content (5%
fair trade hand picked hemp fibers)&#8230;. so rather than unique, it seems we
have to decide the level to go to.<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;color:navy'>Accounting applications probably do not normally need this
same level of definition. Indeed most of our devices use just standard types
such as bond, letterhead, transparency, etc. as well as a few customizable
types. Thus, from an accounting standpoint, anything other than the standard
types is custom. So for accounting it is sufficient (and maybe more desirable) to
say &#8220;bond&#8221; rather than &#8220;white-bond-matte-24lb-89brightness&#8221;.<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;color:navy'>Another question I have is if the size is identified in &#8230;SizeName,
why should it also be included in the media key? <o:p></o:p></span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;color:navy'>A unique media key seems necessary to me. I have looked at
5100.3, and it seems it would take careful study for me to understand the
implementation of media key in this document. I just didn't get it in a quick
pass.<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:11.0pt'>Understood.
That is a problem with not prototyping, although there is no&nbsp;guarentee
that all issues will&nbsp;be found&nbsp; when prototyping. So, pending further
discoveries, perhaps we should consider an errata to the counter spec? I take
it that we would add another object, <font color=black><span style='color:black'>with
'icMediaUsedMediaInfo'&nbsp;being redefined and retyped as a media
qualifier&nbsp;and (perhaps) ''icMediaUsedMediaDescrip&quot; being added</span></font></span></font><font
size=4 color=blue><span style='font-size:13.5pt;color:blue'>&nbsp;</span></font><font
color=black><span style='color:black'>for&nbsp;user infomation?</span></font><o:p></o:p></p>

<p class=MsoNormal><font size=4 color=blue face=Arial><span style='font-size:
13.5pt;color:blue'>incompatible uses, but it isn't the MIB that did this
overloading.&nbsp; This</span></font><o:p></o:p></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:11.0pt'>The&nbsp;former
is a PWG 5101.1 defined keyword; the&nbsp;latter is freeform in that it is not
a public-spec defined keyword, but operationally should be one of&nbsp;a set of
strings&nbsp;defined for use&nbsp;in a particular environment or with&nbsp; a
particular application.<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:11.0pt'>Since
the MIB is informational only (pending prototyping), and Stuart may be doing
the prototyping, I would suggest that we collect the&nbsp;issues discovered
during this effort&nbsp;and define an updated version&nbsp;of the&nbsp;MIB for
resubmission as a candidate standard. <o:p></o:p></span></font></p>

<p class=MsoNormal><font size=4 color=blue face=Arial><span style='font-size:
13.5pt;color:blue'>PWG 5101.1, not a free form name - even a custom size name
has a</span></font><font size=3 face="Times New Roman"><span style='font-size:
12.0pt;font-family:"Times New Roman"'><o:p></o:p></span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt'>What
is the significance of icMediaUsedMediaSizeName using DisplayString and the
others using SnmpAdminString?<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt'>In
the MIB it lists all three as being localized, but it seems only
icMediaUsedMediaName should be localized. I need icMediaUsedMediaSizeName and
icMediaUsedMediaInfo to be used by our accounting apps to identify the size and
type for billing purposes. This would be hard to achieve using localized
strings. Our apps would need to read standardized names from these two objects.
Am I missing something?<o:p></o:p></span></font></p>