attachment
<div dir="ltr"><div><div><div><div><div><div><div><div><div><div><div><div><div>Hi Rick,<br><br></div>Mea culpa.<br><br></div>MFD Alerts was published the same month that I left Samsung and<br></div>I went straight to another high-pressure client and project and just<br></div>plain forgot to IANA register the Printer MIB updates.<br><br></div>There is also a pending errata update against this document for the<br></div>correct use of "-error" and "-warning" suffixes (i.e., should use them <br></div>in IPP, but I will *remove* them from the Printer MIB enums, since <br>the separate prtAlertSeverityLevel object should be used there).<br></div><br></div>The update to MFD Alerts is the highest priority editing task that I'll<br></div>start on in January 2017. It also needs to be poured into the new<br></div>PWG document template. Mike Sweet will help me with editorial<br></div>problems and the update to the very large IANA Considerations<br></div><div>section.<br><br></div><div>Cheers,<br></div><div>- Ira<br><br></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><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>Jan-April: 579 Park Place Saline, MI 48176 734-944-0094<br>May-Dec: 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></div></div></div>
<br><div class="gmail_quote">On Tue, Nov 15, 2016 at 3:43 PM, Yardumian, Rick <span dir="ltr"><<a href="mailto:RYardumian@ciis.canon.com" target="_blank">RYardumian@ciis.canon.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Smith,<br>
<br>
I got a request from Canon Japan about the Printer MIB and IPP MFD Alerts. I copied Mike and Ira in case they have a quick answer.<br>
<br>
1st question is regarding the following documents; <a href="https://ftp.pwg.org/pub/pwg/candidates/cs-pmpmfdalerts10-20120629-5107.3.pdf" rel="noreferrer" target="_blank">https://ftp.pwg.org/pub/pwg/<wbr>candidates/cs-pmpmfdalerts10-<wbr>20120629-5107.3.pdf</a><br>
Printer MIB and IPP MFD Alerts (MFD Alerts)<br>
Status: Approved<br>
29 June 2012 Candidate Standard<br>
<br>
In section "5.2 MFD and Printer Extension Subunit Alerts", it notes that "The new MFD and Printer extension subunit alerts and the associated alert values are defined in this section for registration in PrtAlertCodeTC in IANA Printer MIB [IANAPRT]."<br>
<br>
However, on the "<a href="https://www.ietf.org/assignments/ianaprinter-mib/ianaprinter-mib" rel="noreferrer" target="_blank">https://www.ietf.org/<wbr>assignments/ianaprinter-mib/<wbr>ianaprinter-mib</a>", Canon could not find additional registration for the above spec.<br>
<br>
Based on the above situation, Canon thinks;<br>
- "ianaprinter-mib" has not been updated yet.<br>
- However, the "Printer MIB and IPP MFD Alerts" have been approved.<br>
<br>
Is Canon's understanding correct?<br>
<br>
<br>
And regarding the section "5.2 MFD and Printer Extension Subunit Alerts", Canon thinks;<br>
- "Table 2 MFD and Printer Subunit Alerts" is correct.<br>
- "Table 3 IPP printer-state-reasons" and "9.2 Alert Codes" are incorrect<br>
(missing assignment)<br>
<br>
Is Canon's understanding correct?<br>
<br>
Thanks for looking into this.<br>
<br>
Best regards,<br>
Rick<br>
</blockquote></div><br></div>