Peace,
On Sun, Aug 8, 2021, 1:30 PM Robert Raszuk <robert@xxxxxxxxxx> wrote:
Transport sessions cannot reliably last for 12 hours on the Internet.
That's the thing.The thing is that 1000s of people come to their desks at 8:00, they turn on their financial application - which uses TCP - and turn it off at 17:00 local time. And the single session stays up just fine for 9h. In fact session stays much longer such that in such application there is hard stop at 18 hours to kill the session. And such forced session killing does happen a lot every day.
*sigh* yes, there might be some legacy applications which don't work well with connection reestablishment. Such legacy applications won't be getting any DDoS protection except for the basic one. This is a fine trade-off for many.
I, however, don't see the point. For seemingly every network feature out there there's an application which breaks on that feature. Anycast is not an exception.
An order of magnitude more applications break when they encounter MTUs less than 1500, but we're not going to abandon the concept of MTU, right?
It is just real proof that your point is simply not true.
Not really, as you can see.
> A single BGP route announcement takes some 30 seconds to propagate, and> sometimes a route withdrawal takes more than 4 minutes.That's a pure occurance of spreading FUD.
I do recommend running your own measurements or consult those who do it well. For example Geoff. In fact his cats and data presented illustrate very well the point I was making earlier:
Kinda nothing in this article contradicts what I said before. Well, it was sort of implied it's rather box-and-whiskers than a constant reliable time, as this is a statistical process, if _this_ is your concern. Sorry if it wasn't unclear.
Whether you count not pointing out that a statistical process is, in fact, statistical as FUD or not is entirely up to you.
--
Töma
