Re: New Version Notification for draft-nottingham-httpbis-retry-01.txt

[Mark Nottingham <[e-mail]>]

> On 2 Feb 2017, at 7:41 am, Tom Bergan <[e-mail]> wrote:
> 
> > Applications sometimes want requests to be retried by
> > infrastructure, but can't easily express them in a non-idempotent
> > request (such as GET).
> 
> nit: did you mean "in an idempotent request (such as GET)"?

Thanks, fixed in source.

> 
> > A client SHOULD NOT automatically retry a failed automatic retry.
> 
> Why does RFC 7230 say this? I am aware of HTTP clients that completely ignore this suggestion, and I can't offhand think of a reason why this is a good rule-of-thumb to follow.

Good question. The immediate answer is that RFC2616 said it, and RFC2068 said it before that (and apparently introduced the requirement). 

If we end up revising the text regarding retries, that's something we should consider updating too.

Cheers,



> 
> On Wed, Feb 1, 2017 at 12:26 AM, Mark Nottingham <[e-mail]> wrote:
> FYI; fairly minor update. Would love to hear what people think about the various suggested paths forward.
> 
> Cheers,
> 
> 
> 
>> Begin forwarded message:
>> 
>> From: [e-mail]
>> Subject: New Version Notification for draft-nottingham-httpbis-retry-01.txt
>> Date: 1 February 2017 at 7:25:43 pm AEDT
>> To: "Mark Nottingham" <[e-mail]>
>> 
>> 
>> A new version of I-D, draft-nottingham-httpbis-retry-01.txt
>> has been successfully submitted by Mark Nottingham and posted to the
>> IETF repository.
>> 
>> Name:		draft-nottingham-httpbis-retry
>> Revision:	01
>> Title:		Retrying HTTP Requests
>> Document date:	2017-02-01
>> Group:		Individual Submission
>> Pages:		18
>> URL:            https://www.ietf.org/internet-drafts/draft-nottingham-httpbis-retry-01.txt
>> Status:         https://datatracker.ietf.org/doc/draft-nottingham-httpbis-retry/
>> Htmlized:       https://tools.ietf.org/html/draft-nottingham-httpbis-retry-01
>> Diff:           https://www.ietf.org/rfcdiff?url2=draft-nottingham-httpbis-retry-01
>> 
>> Abstract:
>>   HTTP allows requests to be automatically retried under certain
>>   circumstances.  This draft explores how this is implemented,
>>   requirements for similar functionality from other parts of the stack,
>>   and potential future improvements.
>> 
>> 
>> 
>> 
>> Please note that it may take a couple of minutes from the time of submission
>> until the htmlized version and diff are available at tools.ietf.org.
>> 
>> The IETF Secretariat
>> 
> 
> --
> Mark Nottingham   https://www.mnot.net/
> 
> 

--
Mark Nottingham   https://www.mnot.net/