Re: 2821bis consideration - New 2nd attempt Retry Strategy recommenda

On 2007-11-17 07:13:02 -0500, Hector Santos wrote:
> Also, from what I have seen, top ISPs are also well below 30 mins 2nd 
> retry. In fact for Bellsouth.net, it has a 5 minute 2nd retry. But AT&T 
> took them over, so lets see what  att.net servers are doing. ..... Yup, 
> exactly 5 mins 2nd retry which is what I saw (<30 mins) by the majority 
>  when I was looking at the time.
>
> IMO, 30 minutes is really too high and IMO, it corresponds to the good 
> old days of less reliable machines, more down systems, less reliable 
> connections, slower bandwidths, less scaled systems, etc, etc. But not 
> today. With high performance machines, multi-threading software, Virtual 
> Machines, higher bandwidths, better scaling, more challenge/response 
> systems, etc, may suggest the x821 30 minute retry "guideline" is 
> outdated.  :-)
I would agree with that. Temporary error conditions (real or simulated)
which are fixed in far less than 30 minutes are rather frequent these
days, and combining a short initial delay of a few minutes with an
exponential backoff to an upper limit of a few hours seems to be rather
common.

        hp

-- 
   _  | Peter J. Holzer    | It took a genius to create [TeX],
|_|_) | Sysadmin WSR       | and it takes a genius to maintain it.
| |   | hjp(_at_)hjp(_dot_)at         | That's not engineering, that's art.
__/   | http://www.hjp.at/ |    -- David Kastrup in comp.text.tex

signature.asc
Description: Digital signature