attachment
Hi Mike,<br><br>About 'dateTime' - the problem is *not* in IPP/2.x (as you found)<br><br>It's in IPP Everywhere section 5.3 Table 6 "IPP Everywhere Required <br>Printer Description Attributes", where "printer-config-change-date-time" <br>and "printer-state-change-date-time" are both listed as REQUIRED.<br>But the underlying "printer-current-time (dateTime)" attribute is NOT <br>listed as REQUIRED and it's OPTIONAL in section 4.4.30 of IPP/1.1<br>Model (RFC 2911). This bug affects logging and notifications as well. <br><br>This defect was reported in September 2014 against IPP Everywhere,<br>with the suggested fix of raising "printer-current-time" to RECOMMENDED.<br>But that doesn't fix the need for Printer objects, log records, and notifications <br>to have real date-time stamps.<br><br>This bug in IPP Everywhere is marked "UNKNOWN" for status.<br><br>I think we need a hard look at the side effects of forgetting our (obvious)<br>intent to make "printer-current-time" REQUIRED in IPP Everywhere.<br><br>Cheers,<br>- Ira<br><br><br clear="all"><div><div class="gmail_signature"><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></div>
<br><div class="gmail_quote">On Thu, Jun 11, 2015 at 3:22 PM, Michael Sweet <span dir="ltr"><<a href="mailto:msweet@apple.com" target="_blank">msweet@apple.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">All,<br>
<br>
I have posted an updated stable draft of the IPP 2.0, 2.1, and 2.2 specification to:<br>
<br>
<a href="http://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipp20-20150611.docx" rel="noreferrer" target="_blank">http://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipp20-20150611.docx</a><br>
<a href="http://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipp20-20150611.pdf" rel="noreferrer" target="_blank">http://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipp20-20150611.pdf</a><br>
<a href="http://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipp20-20150611-rev.pdf" rel="noreferrer" target="_blank">http://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipp20-20150611-rev.pdf</a><br>
<br>
This update addresses all of the feedback from the June 1 IPP WG concall. I also looked into dateTime support for IPP/2.1 and /2.2, however there was never anything put into the original specification to require dateTime support, and I couldn't find anything in the mailing list archives or old minutes about it...<br>
<br>
_________________________________________________________<br>
Michael Sweet, Senior Printing System Engineer, PWG Chair<br>
<br>
_______________________________________________<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" rel="noreferrer" target="_blank">https://www.pwg.org/mailman/listinfo/ipp</a><br>
</blockquote></div><br>