- From: Martin Thomson <martin.thomson@gmail.com>
- Date: Mon, 11 Jul 2016 15:45:17 +1000
- To: Kari Hurtta <hurtta-ietf@elmme-mailer.org>
- Cc: HTTP working group mailing list <ietf-http-wg@w3.org>, Mark Nottingham <mnot@mnot.net>, Mike Bishop <Michael.Bishop@microsoft.com>
On 5 July 2016 at 02:04, Kari Hurtta <hurtta-ietf@elmme-mailer.org> wrote:
> Perhaps add to somewhere:
>
> Remaining lifetime of origin object is origin object lifetime
> subtracted "current_age" of response. This is also remaining
> duration for opportunistic commitment ("tls-commit").
I had a look at this, and couldn't really see that it was necessary.
The origin object is defined as being valid if the lifetime is greater
than the current age.
The best I could come up with is this:
A client SHOULD avoid sending requests via cleartext protocols or to
unauthenticated alternative
-services for the duration of the origin object lifetime, except to
discover new potential
-alternatives.
+services while the origin object lifetime remains valid (see
{{well-known}}), except to discover
+new potential alternatives.
But I'm not convinced that we need it.
Received on Monday, 11 July 2016 05:45:45 UTC