"Chris Lewis" <clewis(_at_)nortelnetworks(_dot_)com> wrote:
- spam is a behaviour, not a content. You're trying to identify the
sender behaving that way, not the material per-se.
One glaring difference in behaviour is volume. But the net isn't
currently set up to even be *aware* of volume.
e.g. The "slashdot effect". DDoS attacks. Ping floods.
e.g. The misconfigured open relay which tries to deliver spam 10x
per second, and ignores any reject messages. The sysadmin of that
machine may not even notice any problem, if he's over-built his
system.
While DDoS attacks aren't part of this groups charter, they are, in
my opinion, a large part of the spam problem.
Is the IETF going to decide that traffic/protocol attacks on the
network infrastructure are outside of the scope of technical
solutions? Are there not existing technical methods which can address
the problem?
Alan DeKok.
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg