attachment
<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi Ira,<div class=""><br class=""></div><div class="">I think all 2.x levels should REQUIRE the "date-time-at-xxx" and "printer-current-time", since any printers that have an un-initialized clock can always use the 'unknown' out-of-band value, to reduce the variability between levels. Even basic printers ought to be able to do that at this point if they are implementing IPP, don't you think?</div><div class=""><br class=""><div class="">
Smith<br class=""><br class="">/**<br class=""> Smith Kennedy<br class=""> HP Inc.<br class="">*/
</div>
<div><br class=""><blockquote type="cite" class=""><div class="">On Oct 27, 2020, at 9:22 AM, Ira McDonald <<a href="mailto:blueroofmusic@gmail.com" class="">blueroofmusic@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div dir="ltr" class=""><div class="">Hi Mike,</div><div class=""><br class=""></div><div class="">About where we RECOMMEND or REQUIRE the "date-time" attributes:</div><div class=""><br class=""></div><div class="">In eventual IPP/2.x update, I suggest that IPP/2.1 (Enterprise) and</div><div class="">IPP/2.2 (Production) should REQUIRE the "date-time" attributes (since</div><div class="">this will after all be a major update to the previous PWG Standard of</div><div class="">IPP/2.x).</div><div class=""><br class=""></div><div class="">Rick Landau (Dell) and I ran up against this issue way back when we</div><div class="">were doing mappings to DMTF CIM classes (where real date-time was</div><div class="">already ubiquitous).<br class=""></div><div class=""><br class=""></div><div class="">WDYT?</div><div class=""><br class=""></div><div class="">Cheers,</div><div class="">- Ira</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><div class=""><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><i class=""><font size="1" class="">Ira McDonald (Musician / Software Architect)</font></i></div><div class=""><i class=""><font size="1" class="">Chair - SAE Trust Anchors and Authentication TF<br class=""></font></i></div><div dir="ltr" class=""><i class=""><font size="1" class="">Co-Chair - TCG Trusted Mobility Solutions WG</font></i></div><div class=""><i class=""><font size="1" class="">Co-Chair - TCG Metadata Access Protocol SG<br class=""></font></i></div><div dir="ltr" class=""><i class=""><font size="1" class="">Chair - Linux Foundation Open Printing WG<br class="">Secretary - IEEE-ISTO Printer Working Group<br class="">Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG<br class="">IETF Designated Expert - IPP & Printer MIB<br class="">Blue Roof Music / High North Inc<br class=""><a style="color:rgb(51,51,255)" href="http://sites.google.com/site/blueroofmusic" target="_blank" class="">http://sites.google.com/site/blueroofmusic</a><br class=""><a style="color:rgb(102,0,204)" href="http://sites.google.com/site/highnorthinc" target="_blank" class="">http://sites.google.com/site/highnorthinc</a><br class="">mailto: <a href="mailto:blueroofmusic@gmail.com" target="_blank" class="">blueroofmusic@gmail.com</a><br class="">(permanent) PO Box 221 Grand Marais, MI 49839 906-494-2434</font></i></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div><br class=""></div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Oct 26, 2020 at 9:09 PM Michael Sweet <<a href="mailto:msweet@msweet.org" class="">msweet@msweet.org</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Ira,<br class="">
<br class="">
> On Oct 26, 2020, at 8:34 PM, Ira McDonald <<a href="mailto:blueroofmusic@gmail.com" target="_blank" class="">blueroofmusic@gmail.com</a>> wrote:<br class="">
> <br class="">
> Hi,<br class="">
> <br class="">
> The lack of REQUIRED "printer-current-time" to populate "date-time-at-xxx"<br class="">
> attributes is an *old* problem - noticed in the first draft of IPP 2.0. In RFC<br class="">
> 8011, it's still (incorrectly) RECOMMENDED, which breaks the preferred<br class="">
> "date-time-at-xxx" attributes (the only useful ones in a Job Log) - and RFC<br class="">
> 8011 is the authoritative source definition in the IANA IPP Registry, so this<br class="">
> can't simply be fixed in a PWG 5100.x spec (I think?).<br class="">
<br class="">
So dateTime attributes were all optional in IPP/1.1 and IPP/2.0. And we updated the definition of printer-current-time to include the 'unknown' syntax since it was already explicitly allowed in RFC 2911, just not included in the syntax definition for printer-current-time...<br class="">
<br class="">
The issue for the registry is that when I updated the registrations for RFC 8011 I didn't update the printer-current-time syntax to match the document. I'll include a fix for that in my next dump for IANA.<br class="">
<br class="">
The issue for IPP Everywhere is that 1.0 didn't explicitly require it but *did* require date-time-at-xxx - clearly the intent was to require printer-current-time but we missed it. IPP Everywhere 1.1 makes it RECOMMENDED and notes that the omission from 1.0 was an error since we *did* require date-time-at-xxx. IPP Everywhere 2.0 will be able to make it REQUIRED.<br class="">
<br class="">
Anyways...<br class="">
<br class="">
________________________<br class="">
Michael Sweet<br class="">
<br class="">
<br class="">
<br class="">
</blockquote></div>
</div></blockquote></div><br class=""></div></body></html>