Repeated Blacklisting / IP reputation

Tue Sep 15 12:37:12 UTC 2009

Well, I haven't even had coffee yet and...

Get the removals:

curl -ls
http://lists.arin.net/pipermail/arin-issued/2009-September/000270.html |
grep Remove | grep -v "<PRE>"

Get the additions:

mahannig$ curl -ls
http://lists.arin.net/pipermail/arin-issued/2009-September/000270.html |
grep Add | grep -v "<PRE>"

I'm sure someone else could write something far more elegant, but elegance
isn't always required. :-)

Best,

Marty

On Mon, Sep 14, 2009 at 10:21 PM, Martin Hannigan
<martin at theicelandguy.com>wrote:

>
>
> On Mon, Sep 14, 2009 at 2:58 PM, Justin Shore <justin at justinshore.com>wrote:
>
>> Frank Bulk wrote:
>>
>>> With scarcity of IPv4 addresses, organizations are more desperate than
>>> ever
>>> to receive an allocation.  If anything, there's more of a disincentive
>>> than
>>> ever before for ARIN to spend time on netblock sanitization.
>>>
>>> I do think that ARIN should inform the new netblock owner if it was
>>> previously owned or not.  But if ARIN tried to start cleaning up a
>>> netblock
>>> before releasing it, there would be no end to it.  How could they check
>>> against the probably hundreds of thousands private blocklist?
>>>
>>
>> They could implement a process by which they announce to a mailing list of
>> DNSBL providers that a given assignment has been returned to the RIR and
>> that it should be cleansed from all DNSBLs.
>>
>
>
> You mean like this?
>
> http://lists.arin.net/pipermail/arin-issued/2009-September/000270.html
>
>
>
> -M<
>
>
>

-- 
Martin Hannigan                               martin at theicelandguy.com
p: +16178216079
Power, Network, and Costs Consulting for Iceland Datacenters and Occupants