Rick,
What is the use case for this request? With IPPS basically being implemented by all current IPP printers, both the Client and Printer clocks will need to be fairly close in order for the TLS negotiation to work. So that leaves knowing the timezone for some reason, which for all of thew implementations I've worked with should be irrelevant - CUPS, for example, converts dateTime values to UTC seconds which get mapped to whatever the local timezone is.
> On Feb 19, 2020, at 7:12 PM, Rick Yardumian via ipp <ipp at pwg.org> wrote:
>> Hi,
>> For accounting purposes, Canon needs the client's job submission date and time. I cannot find an IPP client attribute that defines this. Therefore Canon is requesting a new IPP Client attribute that defines when the client submitted the job. Note that Canon wants the client's date and time, not the Printer's date and time that you could get from RFC 8011 date-time-at-creation job status attribute since that attribute gives the printer's time zone which might be different from the client's time zone. Please let us know what you think about this request.
>> Thank you,
> Rick
> _______________________________________________
> ipp mailing list
>ipp at pwg.org>https://www.pwg.org/mailman/listinfo/ipp
________________________
Michael Sweet