attachment-0001
<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Xerox Sans";
panose-1:2 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Xerox Sans Expert";
panose-1:2 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hi folks,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Sorry for the delayed response. Thank you for considering my proposal during your WIMS WG meeting. I do appreciate that time that was spent discussing this request. However, I still do NOT understand why our proposal to add ‘hundredthsOfInkSticks(20)’ to ‘PrtMarkerSuppliesSupplyUnitTC’ was rejected. Why does a new enum for this optional object require a new RFC in order to extend the enum definitions? The only rationale that I can loosely apply to your position is that the enums for the ‘prtMarkerSuppliesSupplyUnit’ object may be defined as Type 1 enums. Unfortunately, I cannot find anything within RFC 3805 which defines the optional ‘prtMarkerSuppliesSupplyUnit’ object as requiring type 1 enums. Therefore, can you please help me understand where this is defined and why? Until then, I will remain confused about your decision…<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Thanks,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Tom<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><b><u><span style='font-size:10.0pt;font-family:"Courier New";color:red'> </span></u></b><b><u><span style='font-size:10.0pt;font-family:"Xerox Sans";color:red'> </span></u></b><b><u><span style='font-size:10.0pt;font-family:"Xerox Sans";color:red'><o:p></o:p></span></u></b></p><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Xerox Sans";color:red'>Thomas Silver<o:p></o:p></span></b></p><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Xerox Sans";color:red'>Mgr, Device Compliance<o:p></o:p></span></b></p><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Xerox Sans";color:black'>Global Remote Services<o:p></o:p></span></b></p><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Xerox Sans";color:black'>Xerox Information Management<o:p></o:p></span></b></p><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Xerox Sans";color:black'>Xerox Corporation<o:p></o:p></span></b></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Xerox Sans";color:black'>800 Phillips Road, MS 111-04A, Webster, NY 14580<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Xerox Sans";color:black'>Office 4420</span><span style='font-size:8.0pt;font-family:"Xerox Sans Expert";color:#1F497D'><br></span><span style='font-size:8.0pt;font-family:"Xerox Sans";color:black'><a href="mailto:thomas.silver@xerox.com">thomas.silver@xerox.com</a></span><span style='font-size:8.0pt;font-family:"Xerox Sans";color:#1F497D'> <br></span><span style='font-size:8.0pt;font-family:"Xerox Sans";color:black'>585-422-7219 / 8*702-7219</span><span style='font-size:10.0pt;font-family:"Xerox Sans";color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Ira McDonald [mailto:blueroofmusic@gmail.com] <br><b>Sent:</b> Friday, October 28, 2011 5:48 PM<br><b>To:</b> Silver, Thomas; Michael R Sweet; pmp@pwg.org; wims@pwg.org; Ira McDonald<br><b>Subject:</b> Response to Xerox request for IANA Printer MIB enumerations<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Hi Thomas,<br><br>The WIMS WG discussed your request at our teleconference yesterday<br>and reached the following consensus:<br><br><br>(1) add ‘hundredthsOfInkSticks(20)’ to ‘PrtMarkerSuppliesSupplyUnitTC’<br> - rejected - rationale: TC in Printer MIB module - requires new RFC<br> - but PWG Steering Committee has asked WIMS WG to consider a<br> Printer MIB v3 (moving TCs to IANA Printer MIB) at December F2F<br> (this would require several years given IETF process delays)<br> - recommendation - use 'percent' for now<br><br>(2) add ‘standardToner(35)’ to ‘PrtMarkerSuppliesTypeTC’<br> - rejected - rationale: 'standard' is the default of any supply type (Mike S)<br> - recommendation - treat any unmodified supply type as 'standard'<br><br>(3) add ‘matteToner(35)’ to ‘PrtMarkerSuppliesTypeTC’<br> - accepted - rationale: widely used distinct toner type (Mike S)<br><br>Also:<br>(4) add 'matteInk(36)' ‘PrtMarkerSuppliesTypeTC’<br> - rationale: widely used distinct toner type (Mike S)<br><br>I will send these registrations to IANA shortly.<br><br>Cheers,<br>- Ira (one of IETF Designated Experts for Printer MIB, along w/ Mike Sweet)<br><br><br clear=all>Ira McDonald (Musician / Software Architect)<br>Chair - Linux Foundation Open Printing WG<br>Secretary - IEEE-ISTO Printer Working Group<br>Co-Chair - IEEE-ISTO PWG IPP WG<br>Chair - TCG Embedded Systems Hardcopy SG<br>IETF Designated Expert - IPP & Printer MIB<br>Blue Roof Music/High North Inc<br><a href="http://sites.google.com/site/blueroofmusic" target="_blank"><span style='color:#3333FF'>http://sites.google.com/site/blueroofmusic</span></a><br><a href="http://sites.google.com/site/highnorthinc" target="_blank"><span style='color:#6600CC'>http://sites.google.com/site/highnorthinc</span></a><br>mailto:<a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a><br>Winter 579 Park Place Saline, MI 48176 734-944-0094<br>Summer PO Box 221 Grand Marais, MI 49839 906-494-2434<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div><br />--
<br />This message has been scanned for viruses and
<br />dangerous content by
<a href="http://www.mailscanner.info/"><b>MailScanner</b></a>, and is
<br />believed to be clean.
</body></html>