attachment-0001
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
<TITLE>RE: PMP> Comments on Printer Port Monitor MIB 1.0 working draft dated March 21, 2005</TITLE>
<META content="MSHTML 6.00.2800.1491" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=774272618-25032005><FONT face=Arial color=#0000ff size=4>Hi
Bill,</FONT></SPAN></DIV>
<DIV><SPAN class=774272618-25032005><FONT face=Arial color=#0000ff
size=4></FONT></SPAN> </DIV>
<DIV><SPAN class=774272618-25032005><FONT face=Arial color=#0000ff
size=4>Because the MS tools use the value of 'hrDeviceIndex' to find and
display</FONT></SPAN></DIV>
<DIV><SPAN class=774272618-25032005><FONT face=Arial color=#0000ff size=4>status
for each SINGLE port (one print protocol bound to one network or
</FONT></SPAN></DIV>
<DIV><SPAN class=774272618-25032005><FONT face=Arial color=#0000ff size=4>local
hardware </FONT></SPAN><SPAN class=774272618-25032005><FONT face=Arial
color=#0000ff size=4>interface).</FONT></SPAN></DIV>
<DIV><SPAN class=774272618-25032005><FONT face=Arial color=#0000ff
size=4></FONT></SPAN> </DIV>
<DIV><SPAN class=774272618-25032005><FONT face=Arial color=#0000ff
size=4>There's nothing wrong with having more than one INSTANCE of the
Printer</FONT></SPAN></DIV>
<DIV><SPAN class=774272618-25032005><FONT face=Arial color=#0000ff size=4>MIB
(with different high-order 'hrDeviceIndex') displayed on a network
system</FONT></SPAN></DIV>
<DIV><SPAN class=774272618-25032005><FONT face=Arial color=#0000ff size=4>for
this purpose.</FONT></SPAN></DIV>
<DIV><SPAN class=774272618-25032005><FONT face=Arial color=#0000ff
size=4></FONT></SPAN> </DIV>
<DIV><SPAN class=774272618-25032005><FONT face=Arial color=#0000ff
size=4>Otherwise (using a single common 'hrDeviceIndex') if any port protocol
is</FONT></SPAN></DIV>
<DIV><SPAN class=774272618-25032005><FONT face=Arial color=#0000ff size=4>down,
they'll all appear to be down. The MS tools do NOT inquire of
the</FONT></SPAN></DIV>
<DIV><SPAN class=774272618-25032005><FONT face=Arial color=#0000ff
size=4>Channel table in the Printer MIB for port-by-port status. And Mike
Fenelon</FONT></SPAN></DIV>
<DIV><SPAN class=774272618-25032005><FONT face=Arial color=#0000ff size=4>has
indicated that that's not changing any time soon.</FONT></SPAN></DIV>
<DIV><SPAN class=774272618-25032005><FONT face=Arial color=#0000ff
size=4></FONT></SPAN> </DIV>
<DIV><SPAN class=774272618-25032005><FONT face=Arial color=#0000ff size=4>Please
don't shoot the messenger - this design worked great for
outboard</FONT></SPAN></DIV>
<DIV><SPAN class=774272618-25032005><FONT face=Arial color=#0000ff
size=4>external network adaptors - it's admittedly cumbersome for a network
printer</FONT></SPAN></DIV>
<DIV><SPAN class=774272618-25032005><FONT face=Arial color=#0000ff
size=4>itself.</FONT></SPAN></DIV>
<DIV><SPAN class=774272618-25032005><FONT face=Arial color=#0000ff
size=4></FONT></SPAN> </DIV>
<DIV><SPAN class=774272618-25032005><FONT face=Arial color=#0000ff
size=4>Cheers,</FONT></SPAN></DIV>
<DIV><SPAN class=774272618-25032005><FONT face=Arial color=#0000ff size=4>-
Ira</FONT></SPAN></DIV>
<DIV> </DIV>
<P><FONT size=2>Ira McDonald (Musician / Software Architect)<BR>Blue Roof Music
/ High North Inc<BR>PO Box 221 Grand Marais, MI 49839<BR>phone:
+1-906-494-2434<BR>email: imcdonald@sharplabs.com</FONT> </P>
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> Bergman, Ron
[mailto:Ron.Bergman@rpsa.ricoh.com]<BR><B>Sent:</B> Friday, March 25, 2005 12:36
PM<BR><B>To:</B> McDonald, Ira; Adams, Charles A; pmp@pwg.org<BR><B>Subject:</B>
RE: PMP> Comments on Printer Port Monitor MIB 1.0 working draft dated March
21, 2005<BR><BR></FONT></DIV>
<DIV id=idOWAReplyText74008 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>Ira,</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>I don't understand your response. If
this is true, then this is not</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2>hrDeviceIndex as used by the printer and
must be clearly indicated</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2>as such and should not be called
hrDeviceIndex.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Why does the index for the table not
satisfy this requirement?</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2> Ron</FONT></DIV>
<DIV dir=ltr>
<HR tabIndex=-1>
</DIV>
<DIV dir=ltr><FONT face=Tahoma size=2><B>From:</B> McDonald, Ira
[mailto:imcdonald@sharplabs.com]<BR><B>Sent:</B> Fri 3/25/2005 8:14
AM<BR><B>To:</B> Bergman, Ron; McDonald, Ira; Adams, Charles A;
pmp@pwg.org<BR><B>Subject:</B> RE: PMP> Comments on Printer Port Monitor MIB
1.0 working draft dated March 21, 2005<BR></FONT><BR></DIV></DIV>
<DIV>
<P><FONT size=2>Hi Ron,<BR><BR>Going all the way back to the first Microsoft
draft and ever since,<BR>it's clear that the MS "port" entry has to have a
separate device<BR>index for each port, because the 'hr...' status objects have
to be<BR>separate for EACH port. <BR><BR>Remember the main MS model is NOT
an embedded printer. It's either<BR>an external network adaptor or a
spooler. In both of these cases,<BR>only ONE protocol is being exposed
fore each "port".<BR><BR>This isn't a new restriction.<BR><BR>In the case of an
external network adaptor, each "port" is literally<BR>a different direct-connect
printer.<BR><BR>Cheers,<BR>- Ira<BR><BR>Ira McDonald (Musician / Software
Architect)<BR>Blue Roof Music / High North Inc<BR>PO Box 221 Grand Marais,
MI 49839<BR>phone: +1-906-494-2434<BR>email:
imcdonald@sharplabs.com<BR><BR>-----Original Message-----<BR>From: Bergman, Ron
[<A
href="mailto:Ron.Bergman@rpsa.ricoh.com">mailto:Ron.Bergman@rpsa.ricoh.com</A>]<BR>Sent:
Thursday, March 24, 2005 3:03 PM<BR>To: McDonald, Ira; Adams, Charles A;
pmp@pwg.org<BR>Subject: RE: PMP> Comments on Printer Port Monitor MIB 1.0
working draft<BR>dated March 21, 2005<BR><BR><BR>Ira,<BR><BR>Regarding your
comment:<BR><BR>2. ppmPortHrDeviceIndex - This seems to imply an hrDeviceTable
entry is<BR>needed for each port on the system. Is this the expected
behavior?<BR>Or is this just the hrDeviceIndex of the printer?<BR>Or is the the
hrDeviceIndex for the network card?<BR><BR><ira> For the Microsoft
tool (TCPMon), EACH port (channel) has to<BR>have a separate 'hrDeviceIndex' -
this is different than typical<BR>Printer MIB implementations, but it's a
Microsoft tool limitation.<BR>Note that Microsoft TCPMon _only_ supports LPR and
Raw ports (no<BR>other protocol is supported or contemplated according to
co-editor<BR>Mike Fenelon from the Microsoft Longhorn printing team), so
this<BR>only means two 'hrDeviceIndex' values at most (for each
printer).<BR></ira><BR><BR>I do not recall ever hearing this. It
certainly is not clear from<BR>the MIB text (see below) that this is the
case. If this is true<BR>then it is not really hrDeviceIndex that is
indicated but is just<BR>ppmPortIndex.<BR><BR>Also, for the printers I work with
there will be a minimum of 10<BR>ports reported. If IPP is enable, there
will be a minimum of 15.<BR>The maximum number will be
192.<BR><BR> Ron<BR><BR>From the
MIB:<BR>ppmPortHrDeviceIndex OBJECT-TYPE<BR>
SYNTAX Integer32
(0..2147483647)<BR> MAX-ACCESS
read-only<BR> STATUS
current<BR> DESCRIPTION<BR>"The value of 'hrDeviceIndex' in
the IETF Host Resources MIB<BR>(RFC 1514/2790), to be used for status queries
for this port if<BR>the value of 'ppmPortSnmpStatusQueryEnabled' is
'true'.<BR><BR>If this object is zero, then monitoring applications MUST
NOT<BR>attempt status queries for this port in the IETF Host Resources<BR>MIB
(RFC 1514/2790) and/or IETF Printer MIB (RFC 1759/3805)."<BR>
REFERENCE<BR>"hrDeviceStatus, hrPrinterStatus, hrPrinterDetectedErrorState
i<BR>n IETF Host Resources MIB (RFC 1514/2790).<BR>prtChannelStatus in IETF
Printer MIB (RFC 1759/3805)."<BR>
DEFVAL { 0
}
-- no host device index<BR> ::= { ppmPortEntry 7
}<BR><BR></FONT></P></DIV></BODY></HTML>