On Dec 22 2004, Barry Shein wrote:
So, your comments are only true if the hardware and software expands
at some rate to match the request rate. It doesn't have to be linearly
expanded, but when you hit a knee in the curve you either move that
knee (i.e., expand resources) or suffer the consequences (exponential
growth in response time.)
That's true, but you aren't seriously suggesting that ISPs won't upgrade
their equipment over time? The internet hasn't finished growing yet,
and service providers are middle men, so their incoming traffic
is bound to grow.
It's perfectly reasonable (don't you think?) to expect an ISP to
deploy resources proportional to their number of users, which brings
us back to the question of the mail request rate per legitimate user
and how it can be eventually limited(*). Some real numbers have
already been offered on the list.
(*) why not (still) consider mail requests for non-users? Verifying
whether an address corresponds to a local user is cheap in principle
nevertheless. Yes, you'll be seeing very many incoming socket
connections, but you don't need to set up a full SMTP service
connection until you already know that the recipient is valid. Now
cheap connections together with Moore's law ought(comment?) to handle
the increase in requests over time at a constant upgrade cost for the
front end.
To bring this back to earth, spammers' behavior is such that, barring
response (blocking them, killing them, increasing resources, pulling
the plug on your internet connection, etc) they will find the knee in
that curve.
That's a lot of different responses, with different costs and
benefits. How can we get an overview without numbers? Or is the idea
that ASRG offers a grab bag of solutions and implementors silently
pick and choose what works for them without giving feedback? I don't
have a preference, just wondering how it's supposed to work.
--
Laird Breyer.
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg