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"> <META content="MSHTML 6.00.2900.2523" name=GENERATOR> <STYLE>@font-face { font-family: Helvetica; } @font-face { font-family: Tahoma; } @page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; } P.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman" } LI.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman" } DIV.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman" } H1 { FONT-WEIGHT: bold; FONT-SIZE: 16pt; MARGIN: 12pt 0in 3pt 0.3in; TEXT-INDENT: -0.3in; FONT-FAMILY: Arial } H2 { FONT-WEIGHT: bold; FONT-SIZE: 14pt; MARGIN: 12pt 0in 6pt 0.4in; TEXT-INDENT: -0.4in; FONT-FAMILY: Arial } H4 { FONT-WEIGHT: bold; FONT-SIZE: 11pt; MARGIN: 12pt 0in 3pt 0.6in; TEXT-INDENT: -0.6in; FONT-FAMILY: Arial } H5 { FONT-WEIGHT: normal; FONT-SIZE: 11pt; MARGIN: 12pt 0in 3pt 0.7in; TEXT-INDENT: -0.7in; FONT-FAMILY: Arial } H6 { FONT-WEIGHT: normal; FONT-SIZE: 11pt; MARGIN: 12pt 0in 3pt 0.8in; TEXT-INDENT: -0.8in; FONT-FAMILY: Arial } P.MsoHeading7 { FONT-SIZE: 10pt; MARGIN: 12pt 0in 3pt 0.9in; TEXT-INDENT: -0.9in; FONT-FAMILY: Arial } LI.MsoHeading7 { FONT-SIZE: 10pt; MARGIN: 12pt 0in 3pt 0.9in; TEXT-INDENT: -0.9in; FONT-FAMILY: Arial } DIV.MsoHeading7 { FONT-SIZE: 10pt; MARGIN: 12pt 0in 3pt 0.9in; TEXT-INDENT: -0.9in; FONT-FAMILY: Arial } P.MsoHeading8 { FONT-SIZE: 10pt; MARGIN: 12pt 0in 3pt 1in; TEXT-INDENT: -1in; FONT-FAMILY: Arial } LI.MsoHeading8 { FONT-SIZE: 10pt; MARGIN: 12pt 0in 3pt 1in; TEXT-INDENT: -1in; FONT-FAMILY: Arial } DIV.MsoHeading8 { FONT-SIZE: 10pt; MARGIN: 12pt 0in 3pt 1in; TEXT-INDENT: -1in; FONT-FAMILY: Arial } P.MsoHeading9 { FONT-SIZE: 9pt; MARGIN: 12pt 0in 3pt 1.1in; TEXT-INDENT: -1.1in; FONT-FAMILY: Arial } LI.MsoHeading9 { FONT-SIZE: 9pt; MARGIN: 12pt 0in 3pt 1.1in; TEXT-INDENT: -1.1in; FONT-FAMILY: Arial } DIV.MsoHeading9 { FONT-SIZE: 9pt; MARGIN: 12pt 0in 3pt 1.1in; TEXT-INDENT: -1.1in; FONT-FAMILY: Arial } A:link { COLOR: blue; TEXT-DECORATION: underline } SPAN.MsoHyperlink { COLOR: blue; TEXT-DECORATION: underline } A:visited { COLOR: purple; TEXT-DECORATION: underline } SPAN.MsoHyperlinkFollowed { COLOR: purple; TEXT-DECORATION: underline } P { FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: "Times New Roman" } P.XMLExample { FONT-SIZE: 8pt; BACKGROUND: #eeeeee; MARGIN: 0in 0in 0pt 0.5in; FONT-FAMILY: "Courier New" } LI.XMLExample { FONT-SIZE: 8pt; BACKGROUND: #eeeeee; MARGIN: 0in 0in 0pt 0.5in; FONT-FAMILY: "Courier New" } DIV.XMLExample { FONT-SIZE: 8pt; BACKGROUND: #eeeeee; MARGIN: 0in 0in 0pt 0.5in; FONT-FAMILY: "Courier New" } SPAN.EmailStyle19 { COLOR: navy; FONT-FAMILY: Arial } DIV.Section1 { page: Section1 } OL { MARGIN-BOTTOM: 0in } UL { MARGIN-BOTTOM: 0in } </STYLE> </HEAD> <BODY lang=EN-US style="WORD-WRAP: break-word; khtml-nbsp-mode: space; khtml-line-break: after-white-space" vLink=purple link=blue> <DIV>Mike,</DIV> <DIV> </DIV> <DIV>The ppmPortName object may contain a maximum of 127 characters.</DIV> <DIV>Does this meet your requirement?</DIV> <DIV> </DIV> <DIV>   Ron</DIV> <DIV> </DIV> <BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"> <DIV class=OutlookMessageHeader dir=ltr align=left>-----Original Message----- From: Mike Fenelon [mailto:mfenelon@windows.microsoft.com] Sent: Thursday, April 21, 2005 9:59 AM To: Bergman, Ron; McDonald, Ira; Paul Danbold Cc: pmp@pwg.org; Harry Lewis (E-mail); Ivan Pavicevic Subject: RE: Adding ppmPortDescription to Port Mon MIB </DIV> <DIV class=Section1> The intent of this object is to give a short, concise user-friendly name of the port. It will be presented in the User Interface for and device that advertises more than one port so the user can pick the correct port for their connected printer. The whole intent was to differentiate between multiple ports on a  device that could host multiple printers. I am concerned we will start  degrading the user experience if we add a whole bunch of ports for the same printer with slightly different names.   <DIV> Mike Fenelon Microsoft</DIV>   <DIV> <DIV class=MsoNormal style="TEXT-ALIGN: center" align=center> <HR tabIndex=-1 align=center width="100%" SIZE=2> </DIV> From: Bergman, Ron [mailto:Ron.Bergman@rpsa.ricoh.com] Sent: Thursday, April 21, 2005 9:32 AM To: McDonald, Ira; Paul Danbold Cc: pmp@pwg.org; Harry Lewis (E-mail); Mike Fenelon; Ivan Pavicevic Subject: RE: Adding ppmPortDescription to Port Mon MIB</DIV>   <DIV> Ira,</DIV> <DIV>  </DIV> <DIV> I would like to hear from Mike or Ivan on this subject, rather than rely on memory.</DIV> <DIV> Your comment does not agree with the current description clause for this object.</DIV> <DIV>  </DIV> <DIV>     Ron</DIV> <BLOCKQUOTE style="MARGIN-TOP: 5pt; MARGIN-BOTTOM: 5pt; MARGIN-RIGHT: 0in"> -----Original Message----- From: McDonald, Ira [mailto:imcdonald@sharplabs.com] Sent: Thursday, April 21, 2005 8:37 AM To: 'Paul Danbold'; Bergman, Ron Cc: pmp@pwg.org; Harry Lewis (E-mail); McDonald, Ira; MFenelon@microsoft.com; IvanP@microsoft.com Subject: RE: Adding ppmPortDescription to Port Mon MIB <DIV> Hi Ron,</DIV> <DIV>  </DIV> <DIV> Doesn't work - MS specifically said that they wanted PortName restricted</DIV> <DIV> to a _name_ that they will display in their tools and do NOT want it to</DIV> <DIV> include descriptive text.  Your memory is incorrect.</DIV> <DIV>  </DIV> <DIV> Cheers,</DIV> <DIV> - Ira</DIV> <DIV>  </DIV> Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221  Grand Marais, MI  49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com <BLOCKQUOTE style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: 5pt 0in 5pt 3.75pt; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"> -----Original Message----- From: Paul Danbold [mailto:danbold@apple.com] Sent: Wednesday, April 20, 2005 11:55 PM To: Bergman, Ron Cc: pmp@pwg.org; Harry Lewis (E-mail); Ira McDonald (E-mail 3); MFenelon@microsoft.com; IvanP@microsoft.com Subject: Re: Adding ppmPortDescription to Port Mon MIB Ron, <DIV>  </DIV> <DIV> Thanks for the clarification.  In the expectation that manufacturers will initialize ppmPortName with helpful information, I am satisfied there is no need to add an additional object.</DIV> <DIV>  </DIV> <DIV> -Paul</DIV> <DIV>  </DIV> <DIV> <DIV> ---------------------------------------------------------------</DIV> <DIV> Paul Danbold</DIV> <DIV> Imaging Technologies Evangelist, Apple Worldwide Developer Relations</DIV> <DIV> 3 Infinite Loop, MS:303-2TE, Cupertino, CA 95014</DIV> <DIV> 408-974-0050 (office)  408-425-3351 (mobile)</DIV> <DIV> ---------------------------------------------------------------</DIV></DIV> <DIV>  </DIV> <DIV>   <DIV> <DIV> On Apr 15, 2005, at 9:48 AM, Bergman, Ron wrote:</DIV> I remembered this morning why we decided, several months back, to remove this object. Since the MIB contained both a desciptive name and a description, it was agreed that the two objects were redundant.  To clarify this situation I recommend that the object ppmPortName be changed to ppmPortDescriptiveName or ppmPortDescription, rather than go back to the original redundant pair. ppPortName is a natural language string with up to 127 characters.  For Paul Danbold's example I could provide a name such as:         "Networked LPR port providing binary PostScript printing for use by marketing" This is less than 80 characters and should be more than sufficient to satisfy Paul's requirement. Also, in addition to a possible name change, it must be noted that this object is expected to be administratively configured using an out-of-band method. Paul, please indicate if this is sufficient.         Ron Bergman         Ricoh Printing Systems America </DIV>  </DIV>   <DIV>  </DIV></BLOCKQUOTE></BLOCKQUOTE></DIV></BLOCKQUOTE></BODY></HTML>