<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hello,<div><br></div><div>Looking at each network listed in the latest version of RIPE NCC's Delegated stat file (<a href="ftp://ftp.ripe.net/ripe/stats/delegated-ripencc-extended-latest">ftp://ftp.ripe.net/ripe/stats/delegated-ripencc-extended-latest</a>) which covers all of the address space issued in the RIPE region:</div><div><br></div><div><div><br></div><div><div>-------- NETWORK NUMBERS:</div><div><br></div><div>Total Number of v4 allocations listed: 20,488</div><div> Number of v4 allocations covered with abuse-c: 4,377 or 21.3% of v4 allocations</div><div>Total Number of v4 PI assignments listed: 28,676</div><div> Number of v4 PI assignments covered with abuse-c: 516 or 1.8% of v4 assignments</div><div>Total Number of v6 allocations listed: 5,584</div><div> Number of v6 allocations covered with abuse-c: 1,104 or 19.8% of v6 allocations</div><div>Total Number of v6 assignments: 1,376</div><div> Number of v6 assignments covered with abuse-c: 56 or 4% of v6 assignments</div><div><br></div><div>Total Number of objects: 56,124 (IPv4: 49,164 IPv6: 6,960)</div><div>Number of objects covered with abuse-c: 6,053 or 10.7% (IPv4: 9.9% IPv6: 16.6%)</div><div><br></div><div><br></div><div>-------- IPv4 NETWORK SIZES:</div><div><br></div><div>Total size of v4 allocation listed: 594,421,760</div><div> Size of v4 allocations covered with abuse-c: 186,387,456 or 31.3%</div><div>Total size of v4 PI assigned listed: 169,759,544</div><div> Size of v4 PI assigned covered with abuse-c: 4,030,400 or 2.3%</div><div><br></div><div>Total size of listed v4 addresses: 764,181,304</div><div>Size of listed v4 addressed covered with abuse-c: 190,417,856 or 24.9%</div></div></div><div><br></div><div><br></div><div><br></div><div>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.</div><div><br></div><div>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). </div><div><br></div><div>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.</div><div><br></div><div>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.</div><div><br></div><div>Please let me know if you have any further questions.</div><div><br></div><div>All the best,</div><div>Kaveh.</div><div><br></div><div><br></div><div>---</div><div>Kaveh Ranjbar,</div><div>RIPE NCC Database Group Manager</div><div><br></div><div><br></div><div>On Apr 26, 2013, at 10:29 AM, Frank Gadegast <<a href="mailto:ripe-anti-spam-wg@powerweb.de">ripe-anti-spam-wg@powerweb.de</a>> wrote:</div><div><div><br class="Apple-interchange-newline"><blockquote type="cite">Kaveh Ranjbar wrote:<br><br>Hi,<br><br>now its one month later, could you please present actual stats ?<br><br><br>Because our stats do not show any real progress:<br><br>date spams from RIPE-IP without contact with contact % with contact<br>2013.04.25 1664 1064 600 36%<br>2013.04.24 1426 908 518 36%<br>2013.04.23 1110 663 447 40%<br>2013.04.22 974 607 367 37%<br>2013.04.21 826 538 288 34%<br>2013.04.20 806 499 307 38%<br>2013.04.19 918 541 377 41%<br>2013.04.18 2113 1429 684 32%<br>2013.04.17 4079 2637 1442 35%<br>2013.04.16 2310 1482 828 35%<br>2013.04.15 3192 2130 1062 33%<br>2013.04.14 1272 849 423 33%<br>2013.04.13 1195 795 400 33%<br>2013.04.12 716 462 254 35%<br>2013.04.11 1083 620 463 42%<br>2013.04.10 701 378 323 46%<br>2013.04.09 587 293 294 50%<br>2013.04.08 519 282 237 45%<br>2013.04.07 457 266 191 41%<br>2013.04.06 418 224 194 46%<br>2013.04.05 311 183 128 41%<br>2013.04.03 460 266 194 42%<br>2013.04.02 476 258 218 45%<br>2013.04.01 412 223 189 45%<br>2013.03.31 241 156 85 35%<br>2013.03.30 351 217 134 38%<br>2013.03.29 320 173 147 45%<br>2013.03.28 517 301 216 41%<br>2013.03.27 950 660 290 30%<br>2013.03.26 889 492 397 44%<br>2013.03.25 1526 1053 473 31%<br>2013.03.24 851 606 245 28%<br>2013.03.23 5051 4037 1014 20%<br>2013.03.22 1692 1259 433 25%<br>2013.03.21 1290 964 326 25%<br><br>contact is an available abuse-c contact or a contact with<br>abuse-mailbox-field as returned by "whois -b"<br><br>right column shows the percentage of spam we receive from the<br>RIPE-region which have an abuse contact<br><br><br>Kind regards, Frank<br><br><blockquote type="cite">[Apologies for duplicate emails]<br><br>Dear colleagues,<br><br>Phase 1 of ripe-563 "Abuse Contact Management in the RIPE Database" is<br>now being implemented, as announced on 19 March 2013.<br><br>According to ripe-563, all resources allocated or assigned by the RIPE<br>NCC will need to have an abuse contact email address included in their<br>RIPE Database registration. During the first six months of<br>implementation (phase 1), all Local Internet Registries (LIRs) must add<br>an abuse contact attribute ("abuse-c:") to their LIR's ORGANISATION<br>object to provide abuse contact information for all of the allocated<br>address space under their LIR.<br><br>Since the initial announcement two weeks ago, we are pleased to report<br>that 24.8% of the RIPE NCC's allocated IPv4 address space is already<br>covered with an abuse contact. More statistics will be sent to the RIPE<br>Anti-Abuse Working Group mailing list.<br><br>In phase 1, we will send notifications to LIRs that haven't added abuse<br>contact information to their LIR's ORGANISATION object. If this<br>information is not added by the LIR by the end of phase 1, we will<br>automatically add the LIR's contact email address (which is already<br>publicly listed at: <<a href="https://www.ripe.net/membership/indices/">https://www.ripe.net/membership/indices/</a>>) as their<br>abuse contact. LIRs can always change this information as needed.<br><br>More information on the implementation plan, including phase 2 (covering<br>PI space and ASNs) is available on RIPE Labs at:<br><<a href="https://labs.ripe.net/Members/kranjbar/implementation-details-of-policy-2011-06">https://labs.ripe.net/Members/kranjbar/implementation-details-of-policy-2011-06</a>><br><br>-------------------------------<br>How to add "abuse-c"<br>-------------------------------<br><br>An explanation of how to add "abuse-c:" to an LIR's ORGANISATION object<br>as well as how to fine-tune abuse contact information for<br>sub-allocations and assignments is outlined here:<br><<a href="https://labs.ripe.net/Members/denis/creating-and-finding-abuse-contacts-in-the-ripe-database">https://labs.ripe.net/Members/denis/creating-and-finding-abuse-contacts-in-the-ripe-database</a>><br><br>Please kindly consider adding abuse contact information as soon as<br>possible to the ORGANISATION object(s) you control or maintain in the<br>RIPE Database.<br><br>Kind Regards,<br><br>Kaveh Ranjbar,<br>RIPE NCC Database Group Manager<br><br></blockquote><br><br>-- <br><br>Mit freundlichen Gruessen, Frank Gadegast<br>--<br>MOTD: "have you enabled SSL on a website or mailbox today ?"<br>--<br>PHADE Software - PowerWeb <a href="http://www.powerweb.de">http://www.powerweb.de</a><br>Inh. Dipl.-Inform. Frank Gadegast <a href="mailto:frank@powerweb.de">mailto:frank@powerweb.de</a><br>Schinkelstrasse 17 fon: +49 33200 52920<br>14558 Nuthetal OT Rehbruecke, Germany fax: +49 33200 52921<br>======================================================================<br><br><br></blockquote></div><br></div></body></html>