North American Network Operators Group|
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical
Re: BCP for Abuse Desk
I've found that the reserving the right to nullroute an offending host's IP address for repeated spam offenses is a good intermediate step between simple notifications and contract/circuit termination. It lets the customer know you mean business while still preserving the customer's account status; if the offender is a web hoster, it winds up being a particularly effective tool, as the threat of collateral damage from other sites hosted on the same IP is pretty compelling.
Of course, it's important to be willing to remove the nullroute as soon as the customer confirms that the problem has been dealt with, otherwise it does effectively become a partial termination of services.
[email protected] wrote:
On Tue, 30 May 2006 20:51:55 CDT, you said:Each of the ISP's I worked for had such a clause. I felt it3d) Make sure your ToS allows nuking a spamming/abusive host. 3e) Then *use* that clause in the ToS when needed.