Note that failed timestamp retrievals can be attempted again.

index.html

@@ -806,17 +806,19 @@ <h3>Validate Algorithm</h3>
       </ol>
 
       <p>
-When a `statusListCredential` URL is dereferenced, server implementations MAY provide a
-mechanism to dereference the status list as of a particular point in time. If such a
-feature is supported, and if query parameters are supported by the URL scheme,
-then the name of the query parameter MUST be `timestamp` and the value MUST be
-a valid URL-encoded [[XMLSCHEMA11-2]] dateTimeStamp string value. The result of
-dereferencing such a timestamped URL MUST be a status list credential containing
-either the status list as it existed at the given point in time, or a 
-<a href="#STATUS_RETRIEVAL_ERROR">STATUS_RETRIEVAL_ERROR</a>.
+When a `statusListCredential` URL is dereferenced, server implementations MAY
+provide a mechanism to dereference the status list as of a particular point in
+time. If such a feature is supported, and if query parameters are supported by
+the URL scheme, then the name of the query parameter MUST be `timestamp` and the
+value MUST be a valid URL-encoded [[XMLSCHEMA11-2]] dateTimeStamp string value.
+The result of dereferencing such a timestamped URL MUST be a status list
+credential containing either the status list as it existed at the given point in
+time, or a <a href="#STATUS_RETRIEVAL_ERROR">STATUS_RETRIEVAL_ERROR</a>.
+If the result is an error, implementations MAY attempt the retrieval again
+with a different timestamp value, or without a timestamp value, as long as
+the <a>verifier</a>'s validation rules permit such an action.
       </p>
 
-
       <p class="note" title="Issuer validation is use case dependent">
 It is expected that a <a>verifier</a> will ensure that it trusts the issuer
 of a <a>verifiable credential</a>, as well as the issuer of the associated