Re: Review of draft-thomson-http-replay-latest

On 8 August 2017 at 08:07, David Benjamin <davidben@chromium.org> wrote:
> If the server is really overloaded, it can send HTTP 503. But I'm guessing
> 503 triggers a sharper client back-off than you like in this scenario.
> Perhaps you're only sort-of-overloaded and retrying at 1-RTT is fine? As you
> say, a sort-of-overloaded server could reject 0-RTT at the TLS level
> instead. Though perhaps you have GET /cheap_thing that you are still willing
> to respond to.

I think that the advice we give there is that if you *might* send a
different response from different nodes, then 503 isn't right and 4NN
(Too Early) is better, even if it means less backing off.

You could probably make a case that returning 503 is consistent - it
depends on server state that is independent of whether the request is
replayed.