There are many ways to get a pretty good time value. From sniffing the HTTP
traffic to using a time server. Printers can have their time set via a
console or web page. They could ask
"http://tycho.usno.navy.mil/cgi-bin/timer.pl". they could use a GPS
module...I hear they are getting pretty cheap.
I do not believe requiring dateTime attributes will be an undue burden on
printer implementations. It will be useful to IPP client applications.
Xerox Architecture Center
Email: Peter.Zehler at usa.xerox.com
Voice: (716) 265-8755
FAX: (716) 265-8792
US Mail: Peter Zehler
800 Phillips Rd.
Webster NY, 14580-9701
From: kugler at us.ibm.com [mailto:kugler at us.ibm.com]
Sent: Tuesday, April 27, 1999 11:50 AM
To: ipp at pwg.org
Subject: Re: IPP> Last Call Comment: Job and Printer time attributes
should be REQ
> However, we could write the requirement such that the IPP/1.1 Printer
> implementation had to attempt to get the time by some means, such as
> the time from a networked NTP Time server, from an incoming HTTP request
> (where it is always present),
I don't think you can count on that. From draft-ietf-http-v11-spec-rev-06,
section 14.18 Date: "If the server does not have a clock that can provide a
reasonable approximation of the current time, its responses MUST NOT
include a Date header field.