CircleID

Here's a direct link to the paper, in pdf format - http://www.oecd.org/dataoecd/5/47/34935342.pdf

Stopping spam / virus / brute force hack attempts originating from specific IP blocks is very simple, if IP allocation agencies like ARIN, APNIC take the responsibility!

All that is needed is, when IP allocation agencies like ARIN / APNIC allocate IP blocks to ISP's they should collect a security deposit. Then provide a simple web form interface to report IP misuse - the form should contain a field for IP and to another to paste the header of spam e-mail originating from the IP or log of brute force attacks originating from the IP etc.

Abuse reports can be processed automatically with simple parse algorithms and the ISP is sent an automated e-mail to check the IP address being misused. This will enable the ISP to contact the offending IP user and ask them to secure the system and stop the spam / virus issue. If the ISP does not respond and the number of spam reports cross a set threshold then the ISP is fined $10 this is a fairly low amount and the ISP can possibly collect this amount from the offending IP user.

A small fine of even $10 will have a cascading effect, nobody like paying fines! Users will start demanding more secure software from vendors and will hire experienced system admins to secure computers connecting to the internet.

Within 18 months of implementation spam and virus spreading through the internet will become very rare occurrence, anyone listening?

Damn. I wish it were that simple.

Start with finding an abuse reporting format that is machine parseable (http://www.mipassoc.org/arf/ is a start but its still useful only for provider to provider aggregation of reports and not for general use)

Then try to introduce RIR policy in this kind of situation.  The most that RIRs can (and generally will) do is to educate people and bring them together

But they dont have nearly as big a stick as you think they do.

http://www.mipassoc.org/about.htm

Registries
Registry services, like APNIC, ARIN and RIPE, assign entries into tables. They typically specify good practice for organizations assisting in the assignment process. However their scope is limited to the operation of the registries.

------8<----------------------------------------------

The above paragraph defines the problem.....

Origin of all IP address abuse (spam / virus / dos attacks) is because the IP allocation registries do not take the responsibility to ensure that IP address are not abused by the ISP's (and their customers) to whom the IP blocks are allocated.

The only possible solution to fix IP address abuse is for the IP registries to take the responsibility.

It is *simple* for the IP registries like APNIC, ARIN and RIPE to implement a abuse reporting system and enforce compliance from ISP's. All that is required is few servers to run the abuse reporting system and few staff < 10 per registry, to co-ordinate the effort with ISP's. The cost of implementing the system can be easily added to the cost of allocating IP address blocks. The total cost will work out to be < $1 per IP address per year.

It is not as simple as you think it is.  However it is an interesting idea that you might want to take before arin / apnic at one of their meetings .. the best place to start with if you're in India, would be the apnic open policy meeting which will be held at the next apnic (perth, feb 2006).