attachment

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1"> <META content="MSHTML 6.00.2800.1491" name=GENERATOR></HEAD> <BODY> <DIV><SPAN class=215460016-26032005><FONT face=Arial color=#0000ff size=4>Hi Dennis,</FONT></SPAN></DIV> <DIV><SPAN class=215460016-26032005><FONT face=Arial color=#0000ff size=4></FONT></SPAN> </DIV> <DIV><SPAN class=215460016-26032005><FONT face=Arial color=#0000ff size=4>The Introduction and Background were recently added, for boilerplate reasons.</FONT></SPAN></DIV> <DIV><SPAN class=215460016-26032005><FONT face=Arial color=#0000ff size=4>They are not authoritative and in fact have not been reviewed.</FONT></SPAN></DIV> <DIV><SPAN class=215460016-26032005><FONT face=Arial color=#0000ff size=4></FONT></SPAN> </DIV> <DIV><SPAN class=215460016-26032005><FONT face=Arial color=#0000ff size=4>Microsoft is NOT using the Printer MIB for status at all in Longhorn (per Mike</FONT></SPAN></DIV> <DIV><SPAN class=215460016-26032005><FONT face=Arial color=#0000ff size=4>Fenelon).  The 'hrDeviceTable' </FONT></SPAN><SPAN class=215460016-26032005><FONT face=Arial color=#0000ff size=4>and 'hrPrinterTable' in the Host Resources MIB </FONT></SPAN></DIV> <DIV><SPAN class=215460016-26032005><FONT face=Arial color=#0000ff size=4>are the only status that will </FONT></SPAN><SPAN class=215460016-26032005><FONT face=Arial color=#0000ff size=4>be displayed by Longhorn for printer ports.</FONT></SPAN></DIV> <DIV><SPAN class=215460016-26032005><FONT face=Arial color=#0000ff size=4></FONT></SPAN> </DIV> <DIV><SPAN class=215460016-26032005><FONT face=Arial color=#0000ff size=4>If a vendor implements a single 'hrDeviceIndex' value for all ports (i.e., channels) </FONT></SPAN></DIV> <DIV><SPAN class=215460016-26032005><FONT face=Arial color=#0000ff size=4>on </FONT></SPAN><SPAN class=215460016-26032005><FONT face=Arial color=#0000ff size=4>the "same" </FONT></SPAN><SPAN class=215460016-26032005><FONT face=Arial color=#0000ff size=4>printer, then if ANY port is 'down' in 'hrDeviceStatus' they will ALL </FONT></SPAN></DIV> <DIV><SPAN class=215460016-26032005><FONT face=Arial color=#0000ff size=4>be shown </FONT></SPAN><SPAN class=215460016-26032005><FONT face=Arial color=#0000ff size=4>'down' in the MS tools.  That's not acceptable behaviour.</FONT></SPAN></DIV> <DIV><SPAN class=215460016-26032005><FONT face=Arial color=#0000ff size=4></FONT></SPAN> </DIV> <DIV><SPAN class=215460016-26032005><FONT face=Arial color=#0000ff size=4>Cheers,</FONT></SPAN></DIV> <DIV><SPAN class=215460016-26032005><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> Dennis Carney [mailto:dcarney@us.ibm.com]<BR><B>Sent:</B> Friday, March 25, 2005 2:43 PM<BR><B>To:</B> pmp@pwg.org<BR><B>Cc:</B> Adams, Charles A; McDonald, Ira; 'Bergman, Ron'; mfenelon@windows.microsoft.com<BR><B>Subject:</B> RE: PMP> Comments on Printer Port Monitor MIB 1.0 working draft d ated March 21, 2005<BR><BR></FONT></DIV> <P>Ira, My reading of the "Introduction" and the "Background" of the document seems to make it clear that the main MS model *IS* an embedded printer.<BR><BR>Mike Fenelon, is it really true that your port monitor makes it such that each port *has to* have a different ppmPortHrDeviceIndex? If a network printer implemented this MIB and advertised both an LPR and a RAW port, would you really have a problem if both ports had a ppmPortHrDeviceIndex of 1?<BR><BR>Dennis<BR><IMG height=16 alt='Inactive hide details for "McDonald, Ira" <imcdonald@sharplabs.com>' src="cid:10__=08BBE55CDFF522718f9e8a93df938@us.ibm.com" width=16>"McDonald, Ira" <imcdonald@sharplabs.com><BR><BR><BR> <TABLE cellSpacing=0 cellPadding=0 width="100%" border=0> <TBODY> <TR vAlign=top> <TD style="BACKGROUND-IMAGE: url(cid:20__=08BBE55CDFF522718f9e8a93df938@us.ibm.com); BACKGROUND-REPEAT: no-repeat" width="40%"> <UL> <UL> <UL> <UL><B><FONT size=2>"McDonald, Ira" <imcdonald@sharplabs.com></FONT></B><FONT size=2> </FONT><BR><FONT size=2>Sent by: pmp-owner@pwg.org</FONT> <P><FONT size=2>03/25/2005 09:14 AM</FONT></P></UL></UL></UL></UL></TD> <TD width="60%"> <TABLE cellSpacing=0 cellPadding=0 width="100%" border=0> <TBODY> <TR vAlign=top> <TD vAlign=center width="1%"><IMG height=1 alt="" src="cid:30__=08BBE55CDFF522718f9e8a93df938@us.ibm.com" width=58 border=0><BR> <DIV align=right><FONT size=2>To</FONT></DIV></TD> <TD width="100%"><IMG height=1 alt="" src="cid:30__=08BBE55CDFF522718f9e8a93df938@us.ibm.com" width=1 border=0><BR><FONT size=2>"'Bergman, Ron'" <Ron.Bergman@rpsa.ricoh.com>, "McDonald, Ira" <imcdonald@sharplabs.com>, "Adams, Charles A" <charles.a.adams@office.xerox.com>, pmp@pwg.org</FONT></TD></TR> <TR vAlign=top> <TD vAlign=center width="1%"><IMG height=1 alt="" src="cid:30__=08BBE55CDFF522718f9e8a93df938@us.ibm.com" width=58 border=0><BR> <DIV align=right><FONT size=2>cc</FONT></DIV></TD> <TD width="100%"><IMG height=1 alt="" src="cid:30__=08BBE55CDFF522718f9e8a93df938@us.ibm.com" width=1 border=0><BR></TD></TR> <TR vAlign=top> <TD vAlign=center width="1%"><IMG height=1 alt="" src="cid:30__=08BBE55CDFF522718f9e8a93df938@us.ibm.com" width=58 border=0><BR> <DIV align=right><FONT size=2>Subject</FONT></DIV></TD> <TD width="100%"><IMG height=1 alt="" src="cid:30__=08BBE55CDFF522718f9e8a93df938@us.ibm.com" width=1 border=0><BR><FONT size=2>RE: PMP> Comments on Printer Port Monitor MIB 1.0 working draft d ated March 21, 2005</FONT></TD></TR></TBODY></TABLE> <TABLE cellSpacing=0 cellPadding=0 border=0> <TBODY> <TR vAlign=top> <TD width=58><IMG height=1 alt="" src="cid:30__=08BBE55CDFF522718f9e8a93df938@us.ibm.com" width=1 border=0></TD> <TD width=336><IMG height=1 alt="" src="cid:30__=08BBE55CDFF522718f9e8a93df938@us.ibm.com" width=1 border=0></TD></TR></TBODY></TABLE></TD></TR></TBODY></TABLE><BR><TT>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></TT><BR></P></BODY></HTML>