attachment
<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Lee,<div><br></div><div>These are now listed on the PWG copy of the registrations at:</div><div><br></div><div> <a href="http://www.pwg.org/ipp/ipp-registrations.xml">http://www.pwg.org/ipp/ipp-registrations.xml</a></div><div><br></div><div>Once IANA finishes processing the updates for IPP FaxOut and Transaction-Based Printing I will send another update for these...</div><div><br></div><div><br><div><div>On Dec 4, 2013, at 12:14 PM, Ira McDonald <<a href="mailto:blueroofmusic@gmail.com">blueroofmusic@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div><div><div><div><div><div>Hi Lee,<br><br></div>During Monday's PWG IPP call, we agreed to accept your proposed updates<br></div>for missing CRUs (as further clarified by Mike Sweet) - these should be applied<br>
to IPP printer-state-reasons and PrtAlertCodeTC. Mike and I have action items <br>to get these registered with IANA for IPP and Printer MIB.<br></div><br></div>Thanks very much for this good catch!<br><br></div>Cheers,<br>
</div>- Ira (co-chair of IPP WG)<br><div><br></div></div><div class="gmail_extra"><br clear="all"><div><div dir="ltr">Ira McDonald (Musician / Software Architect)<br>Co-Chair - TCG Trusted Mobility Solutions WG<br>
Chair - Linux Foundation Open Printing WG<br>Secretary - IEEE-ISTO Printer Working Group<br>Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG<br>IETF Designated Expert - IPP & Printer MIB<br>Blue Roof Music / High North Inc<br>
<a style="color:rgb(51,51,255)" href="http://sites.google.com/site/blueroofmusic" target="_blank">http://sites.google.com/site/blueroofmusic</a><br><a style="color:rgb(102,0,204)" href="http://sites.google.com/site/highnorthinc" target="_blank">http://sites.google.com/site/highnorthinc</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<br><br><div style="display:inline">
</div><div style="display:inline"></div><div style="display:inline"></div><div></div><div></div><div></div><div></div></div></div>
<br><br><div class="gmail_quote">On Thu, Nov 21, 2013 at 12:21 PM, Hills, Lee D <span dir="ltr"><<a href="mailto:Lee.Hills@xerox.com" target="_blank">Lee.Hills@xerox.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
This sounds reasonable to me.<br>
<span class="HOEnZb"><font color="#888888"><br>
Lee<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
-----Original Message-----<br>
From: Michael Sweet [mailto:<a href="mailto:msweet@apple.com">msweet@apple.com</a>]<br>
Sent: Thursday, November 21, 2013 9:17 AM<br>
To: Hills, Lee D<br>
Cc: <a href="mailto:ipp@pwg.org">ipp@pwg.org</a>; <a href="mailto:wims@pwg.org">wims@pwg.org</a><br>
Subject: Re: [IPP] printer-state-reasons Customer Replaceable Unit Missing<br>
<br>
Lee,<br>
<br>
While we haven't defined keywords for these conditions, I think that is a clear omission that needs to be addressed. The following are my suggested registrations for new "printer-state-reason" keyword values, with a preference to following the RFC 2911 naming for a few:<br>
<br>
Attributes (attribute syntax)<br>
Keyword Attribute Value Reference<br>
----------------------- ---------<br>
printer-state-reasons (1setOf type2 keyword) [RFC2911]<br>
cleaner-missing<br>
developer-missing<br>
fuser-missing<br>
marker-ink-missing<br>
marker-print-ribbon-missing<br>
marker-supply-missing<br>
marker-waste-missing<br>
marker-waste-ink-receptacle-missing<br>
marker-waste-toner-receptacle-missing<br>
opc-missing<br>
toner-missing<br>
<br>
For completeness we should also register PrtAlertCodeTC values to cover all of the RFC 2911 and new keywords above:<br>
<br>
-- Marker Supplies group<br>
markerCleanerMissing(1116), #### CAUTION, PRELIMINARY VALUES NOT REGISTERED<br>
markerDeveloperMissing(1117),<br>
markerFuserMissing(1118),<br>
markerInkMissing(1119),<br>
markerOpcMissing(1120),<br>
markerPrintRibbonMissing(1121),<br>
markerSupplyAlmostEmpty(1122),<br>
markerSupplyEmpty(1123),<br>
markerSupplyMissing(1124),<br>
markerWasteAlmostFull(1125),<br>
markerWasteFull(1126),<br>
markerWasteMissing(1127),<br>
markerWasteInkReceptacleMissing(1128),<br>
markerWasteTonerReceptacleMissing(1129),<br>
<br>
Note: it appears that PWG 5100.9 defined a few keywords with duplicate semantics for existing 2911 keywords; I think we should deprecate them as part of an errata for 5100.9 (which can correct the table errors):<br>
<br>
RFC 2911 PWG 5100.9<br>
-------------------------------------- ---------------------------------<br>
developer-low marker-developer-almost-empty<br>
developer-empty marker-developer-empty<br>
media-needed input-manual-input-request<br>
<br>
<br>
Thoughts?<br>
<br>
<br>
</div></div><div class="HOEnZb"><div class="h5">_______________________________________________<br>
ipp mailing list<br>
<a href="mailto:ipp@pwg.org">ipp@pwg.org</a><br>
<a href="https://www.pwg.org/mailman/listinfo/ipp" target="_blank">https://www.pwg.org/mailman/listinfo/ipp</a><br>
</div></div></blockquote></div><br></div>
_______________________________________________<br>ipp mailing list<br><a href="mailto:ipp@pwg.org">ipp@pwg.org</a><br>https://www.pwg.org/mailman/listinfo/ipp<br></blockquote></div><br><div>
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">_______________________________________________________________<br>Michael Sweet, Senior Printing System Engineer, PWG Chair<br></div>
</div>
<br></div></body></html>