Changeset 779 for draft-ietf-httpbis/latest/p6-cache.xml

Timestamp:

09/03/10 13:11:58 (11 years ago)

Author:

julian.reschke@…

Message:

re-organize field descriptions for age calculation, preparing for work on #29.

File:

• draft-ietf-httpbis/latest/p6-cache.xml (modified) (3 diffs)

draft-ietf-httpbis/latest/p6-cache.xml

@@ -19 +19 @@
   <!ENTITY uri                         "<xref target='Part1' x:rel='#uri' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY messaging                   "<xref target='Part1' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
+  <!ENTITY clockless                   "<xref target='Part1' x:rel='#clockless.origin.server.operation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY conditional                 "<xref target='Part4' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY partial                     "<xref target='Part5' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
@@ -631 +632 @@
 </t>
 <t>
-  The term "age_value" denotes the value of the Age header, in a form appropriate for
-  arithmetic operations.
-</t>
-<t>
-  HTTP/1.1 requires origin servers to send a Date header, if possible, with every
-  response, giving the time at which the response was generated (see &header-date;).
-  The term "date_value" denotes the value of the Date header, in a form appropriate for
-  arithmetic operations.
-</t>
-<t>
-  The term "now" means "the current value of the clock at the host performing the
-  calculation." Hosts that use HTTP, but especially hosts running origin servers and
-  caches, &SHOULD; use NTP <xref target="RFC1305" /> or some similar protocol to
-  synchronize their clocks to a globally accurate time standard.
+  The following data is used for the age calculation:
+</t>
+<t>
+  <x:dfn>age_value</x:dfn>
+  <list>
+    <t>
+      The term "age_value" denotes the value of the Age header, in a form
+      appropriate for arithmetic operation; or 0, if not available.
+    </t>
+  </list>
+</t>
+<t>
+  <x:dfn>date_value</x:dfn>
+  <list>
+    <t>
+      HTTP/1.1 requires origin servers to send a Date header, if possible,
+      with every response, giving the time at which the response was generated
+      (see &header-date;). The term "date_value" denotes the value of the Date
+      header, in a form appropriate for arithmetic operations. See
+      &clockless; for requirements regarding responses without a Date
+      response header.<cref source="jre" anchor="TODO-checkref">correct reference?</cref>
+    </t>
+  </list>
+</t>
+<t>
+  <x:dfn>now</x:dfn>
+  <list>
+    <t>
+      The term "now" means "the current value of the clock at the host
+      performing the calculation". Hosts that use HTTP, but especially hosts
+      running origin servers and caches, &SHOULD; use NTP
+      (<xref target="RFC1305"/>) or some similar protocol to synchronize their
+      clocks to a globally accurate time standard.
+    </t>
+  </list>
+</t>
+<t>
+  <x:dfn>request_time</x:dfn>
+  <list>
+    <t>
+      The current value of the clock at the host at the time the request
+      resulting in the stored response was made.
+    </t>
+  </list>
+</t>
+<t>
+  <x:dfn>response_time</x:dfn>
+  <list>
+    <t>
+      The current value of the clock at the host at the time the response was
+      received.
+    </t>
+  </list>
 </t>
 <t>
@@ -675 +715 @@
   time (in seconds) since the stored response was last validated by the origin server to
   the corrected_initial_age.
-</t>
-<t>
-  In summary:
-</t>
-<t>
-  age_value
-  <list>
-    <t>Age header field-value received with the response.</t>
-  </list>
-</t>
-<t>
-  date_value
-  <list>
-    <t>Date header field-value received with the response.</t>
-  </list>
-</t>
-<t>
-  request_time
-  <list>
-    <t>Local time when the cache made the request resulting in the stored response.</t>
-  </list>
-</t>
-<t>
-  response_time
-  <list>
-    <t>Local time when the cache received the response.</t>
-  </list>
-</t>
-<t>
-  now
-  <list>
-    <t>Current local time.</t>
-  </list>
 </t>
 <figure>