Hello,

Looking at each network listed in the latest version of RIPE NCC's Delegated stat file (ftp://ftp.ripe.net/ripe/stats/delegated-ripencc-extended-latest) which covers all of the address space issued in the RIPE region:


-------- NETWORK NUMBERS:

Total Number of v4 allocations listed: 20,488
        Number of v4 allocations covered with abuse-c: 4,377 or 21.3% of v4 allocations
Total Number of v4 PI assignments listed: 28,676
        Number of v4 PI assignments covered with abuse-c: 516 or 1.8% of v4 assignments
Total Number of v6 allocations listed: 5,584
        Number of v6 allocations covered with abuse-c: 1,104 or 19.8% of v6 allocations
Total Number of v6 assignments: 1,376
        Number of v6 assignments covered with abuse-c: 56 or 4% of v6 assignments

Total Number of objects: 56,124 (IPv4: 49,164 IPv6: 6,960)
Number of objects covered with abuse-c: 6,053 or 10.7% (IPv4: 9.9% IPv6: 16.6%)


-------- IPv4 NETWORK SIZES:

Total size of v4 allocation listed: 594,421,760
        Size of v4 allocations covered with abuse-c: 186,387,456 or 31.3%
Total size of v4 PI assigned listed: 169,759,544
        Size of v4 PI assigned covered with abuse-c: 4,030,400 or 2.3%

Total size of listed v4 addresses: 764,181,304
Size of listed v4 addressed covered with abuse-c: 190,417,856 or 24.9%



Taking v4 as an example, 24.9% of address space is already covered by an "abuse-c:" contact which consists of 21.3% of networks allocated by RIPE NCC to its members and 1.8% of PI assigned objects.

Please note that the current phase -which will continue until end of september- is focused on allocations (31.3% of address space is covered now). 

In the coming months, we will send multiple reminders to members who haven't added an "abuse-c:" to their LIR's organisation object and at the end of this phase, we will automatically add the public LIR email address as the abuse contact email address for that member's allocated objects. Members will always be able to change those contacts but they won't be able to remove the "abuse-c:" attribute from the LIR's organisation object.

Looking more closely at the v4 numbers, it is also visible that although 58% of the v4 networks listed are assignments they only count for 22.2% of size of addresses in the RIPE region. This might not directly correlate with abuse statistics though, as it is possible that for some reason spammers prefer one flavour of addresses over another one.

Please let me know if you have any further questions.

All the best,
Kaveh.


---
Kaveh Ranjbar,
RIPE NCC Database Group Manager


On Apr 26, 2013, at 10:29 AM, Frank Gadegast <ripe-anti-spam-wg@powerweb.de> wrote:

Kaveh Ranjbar wrote:

Hi,

now its one month later, could you please present actual stats ?


Because our stats do not show any real progress:

date        spams from RIPE-IP  without contact     with contact    % with contact
2013.04.25  1664                1064                600             36%
2013.04.24  1426                908                 518             36%
2013.04.23  1110                663                 447             40%
2013.04.22  974                 607                 367             37%
2013.04.21  826                 538                 288             34%
2013.04.20  806                 499                 307             38%
2013.04.19  918                 541                 377             41%
2013.04.18  2113                1429                684             32%
2013.04.17  4079                2637                1442            35%
2013.04.16  2310                1482                828             35%
2013.04.15  3192                2130                1062            33%
2013.04.14  1272                849                 423             33%
2013.04.13  1195                795                 400             33%
2013.04.12  716                 462                 254             35%
2013.04.11  1083                620                 463             42%
2013.04.10  701                 378                 323             46%
2013.04.09  587                 293                 294             50%
2013.04.08  519                 282                 237             45%
2013.04.07  457                 266                 191             41%
2013.04.06  418                 224                 194             46%
2013.04.05  311                 183                 128             41%
2013.04.03  460                 266                 194             42%
2013.04.02  476                 258                 218             45%
2013.04.01  412                 223                 189             45%
2013.03.31  241                 156                 85              35%
2013.03.30  351                 217                 134             38%
2013.03.29  320                 173                 147             45%
2013.03.28  517                 301                 216             41%
2013.03.27  950                 660                 290             30%
2013.03.26  889                 492                 397             44%
2013.03.25  1526                1053                473             31%
2013.03.24  851                 606                 245             28%
2013.03.23  5051                4037                1014            20%
2013.03.22  1692                1259                433             25%
2013.03.21  1290                964                 326             25%

contact is an available abuse-c contact or a contact with
abuse-mailbox-field as returned by "whois -b"

right column shows the percentage of spam we receive from the
RIPE-region which have an abuse contact


Kind regards, Frank

[Apologies for duplicate emails]

Dear colleagues,

Phase 1 of ripe-563 "Abuse Contact Management in the RIPE Database" is
now being implemented, as announced on 19 March 2013.

According to ripe-563, all resources allocated or assigned by the RIPE
NCC will need to have an abuse contact email address included in their
RIPE Database registration. During the first six months of
implementation (phase 1), all Local Internet Registries (LIRs) must add
an abuse contact attribute ("abuse-c:") to their LIR's ORGANISATION
object to provide abuse contact information for all of the allocated
address space under their LIR.

Since the initial announcement two weeks ago, we are pleased to report
that 24.8% of the RIPE NCC's allocated IPv4 address space is already
covered with an abuse contact. More statistics will be sent to the RIPE
Anti-Abuse Working Group mailing list.

In phase 1, we will send notifications to LIRs that haven't added abuse
contact information to their LIR's ORGANISATION object. If this
information is not added by the LIR by the end of phase 1, we will
automatically add the LIR's contact email address (which is already
publicly listed at: <https://www.ripe.net/membership/indices/>) as their
abuse contact. LIRs can always change this information as needed.

More information on the implementation plan, including phase 2 (covering
PI space and ASNs) is available on RIPE Labs at:
<https://labs.ripe.net/Members/kranjbar/implementation-details-of-policy-2011-06>

-------------------------------
How to add "abuse-c"
-------------------------------

An explanation of how to add "abuse-c:" to an LIR's ORGANISATION object
as well as how to fine-tune abuse contact information for
sub-allocations and assignments is outlined here:
<https://labs.ripe.net/Members/denis/creating-and-finding-abuse-contacts-in-the-ripe-database>

Please kindly consider adding abuse contact information as soon as
possible to the ORGANISATION object(s) you control or maintain in the
RIPE Database.

Kind Regards,

Kaveh Ranjbar,
RIPE NCC Database Group Manager



--

Mit freundlichen Gruessen, Frank Gadegast
--
MOTD: "have you enabled SSL on a website or mailbox today ?"
--
PHADE Software - PowerWeb                       http://www.powerweb.de
Inh. Dipl.-Inform. Frank Gadegast             mailto:frank@powerweb.de
Schinkelstrasse 17                                fon: +49 33200 52920
14558 Nuthetal OT Rehbruecke, Germany             fax: +49 33200 52921
======================================================================