HTTP/1.1 Operation without a Clock
draft-lawrence-http-noclock-00

Document Type Expired Internet-Draft (individual)
Authors Jeffrey Mogul  , Richard Gray  , Scott Lawrence 
Last updated 1997-04-22
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-lawrence-http-noclock-00.txt

Abstract

This memo describes a problem with the current Proposed Standard for HTTP/1.1 found as a result of implementation experience. A web server may be implemented in an embedded system as a network user interface. Often the embedded system is one which has no other use for a real-time clock, and/or the web interface is being added to an existing device which has no clock. Without a clock, no accurate HTTP Date header can be generated. This memo examines the implications of this situation for the operation of HTTP/1.1 origin servers, proxies, and clients, and proposes changes to the HTTP/1.1 specification to permit compliant operation in such systems.

Authors

Jeffrey Mogul (JeffMogul@acm.org)
Richard Gray (rlgray@us.ibm.com)
Scott Lawrence (slawrence@pingtel.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)