nanog mailing list archives
Re: Update Spamhaus DROP list from Cisco CLI (TCL)
From: Jack Bates <jbates () brightok net>
Date: Thu, 20 Jan 2011 10:44:34 -0600
On 1/19/2011 8:19 PM, Jared Mauch wrote:
This was done once before, it was called MAPS at the time. Using BGP as a signaling mechanic for this stuff can obviously be useful. The challenge has always been balancing the trust with a 3rd party with the other operational requirements.
It's only useful if you want to make troubleshooting problems more difficult and require remote parties to contact you off-net. Conditionals for such blocks are more difficult (abuse@domain whitelisted isn't enough, you have to have a specific @domain which the filters don't apply to).
I agree that smaller networks are the ones more likely to participate in such things.
Jack
Current thread:
- Update Spamhaus DROP list from Cisco CLI (TCL) Thomas Magill (Jan 19)
- Re: Update Spamhaus DROP list from Cisco CLI (TCL) Jared Mauch (Jan 19)
- Re: Update Spamhaus DROP list from Cisco CLI (TCL) Jack Bates (Jan 20)
- Re: Update Spamhaus DROP list from Cisco CLI (TCL) Suresh Ramasubramanian (Jan 19)
- RE: Update Spamhaus DROP list from Cisco CLI (TCL) Thomas Magill (Jan 20)
- Re: Update Spamhaus DROP list from Cisco CLI (TCL) Peter Pauly (Jan 25)
- Re: Update Spamhaus DROP list from Cisco CLI (TCL) Jared Mauch (Jan 19)