<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div style="font-family: Arial; "><span style="font-family: Helvetica; ">[Apologies for duplicate emails]</span></div><div style="font-family: Arial; "><br style="font-family: Helvetica; "></div><div style="font-family: Arial; "><span style="font-family: Helvetica; ">Dear colleagues,</span></div><div style="font-family: Arial; "><br style="font-family: Helvetica; "></div><div style="font-family: Arial; "><span style="font-family: Helvetica; ">Phase 1 of ripe-563 "Abuse Contact Management in the RIPE Database" is </span><span style="font-family: Helvetica; ">now being implemented, as announced on 19 March 2013. </span></div><div style="font-family: Arial; "><br style="font-family: Helvetica; "></div><div style="font-family: Arial; "><span style="font-family: Helvetica; ">According to ripe-563, all resources allocated or assigned by the RIPE </span><span style="font-family: Helvetica; ">NCC will need to have an abuse contact email address included in their </span><span style="font-family: Helvetica; ">RIPE Database registration. During the first six months of </span><span style="font-family: Helvetica; ">implementation (phase 1), all Local Internet Registries (LIRs) must add </span><span style="font-family: Helvetica; ">an abuse contact attribute ("abuse-c:") to their LIR's ORGANISATION </span><span style="font-family: Helvetica; ">object to provide abuse contact information for all of the allocated </span><span style="font-family: Helvetica; ">address space under their LIR. </span></div><div style="font-family: Arial; "><br style="font-family: Helvetica; "></div><div style="font-family: Arial; "><span style="font-family: Helvetica; ">Since the initial announcement two weeks ago, we are pleased to report </span><span style="font-family: Helvetica; ">that 24.8% of the RIPE NCC's allocated IPv4 address space is already </span><span style="font-family: Helvetica; ">covered with an abuse contact. More statistics will be sent to the RIPE </span><span style="font-family: Helvetica; ">Anti-Abuse Working Group mailing list. </span></div><div style="font-family: Arial; "><br style="font-family: Helvetica; "></div><div style="font-family: Arial; "><span style="font-family: Helvetica; ">In phase 1, we will send notifications to LIRs that haven't added abuse </span><span style="font-family: Helvetica; ">contact information to their LIR's ORGANISATION object. If this </span><span style="font-family: Helvetica; ">information is not added by the LIR by the end of phase 1, we will </span><span style="font-family: Helvetica; ">automatically add the LIR's contact email address (which is already </span><span style="font-family: Helvetica; ">publicly listed at: <</span><a href="https://www.ripe.net/membership/indices/" style="font-family: Helvetica; ">https://www.ripe.net/membership/indices/</a><span style="font-family: Helvetica; ">>) as their </span><span style="font-family: Helvetica; ">abuse contact. LIRs can always change this information as needed. </span></div><div style="font-family: Arial; "><br style="font-family: Helvetica; "></div><div style="font-family: Arial; "><span style="font-family: Helvetica; ">More information on the implementation plan, including phase 2 (covering </span><span style="font-family: Helvetica; ">PI space and ASNs) is available on RIPE Labs at: </span></div><div style="font-family: Arial; "><span style="font-family: Helvetica; "><</span><a href="https://labs.ripe.net/Members/kranjbar/implementation-details-of-policy-2011-06" style="font-family: Helvetica; ">https://labs.ripe.net/Members/kranjbar/implementation-details-of-policy-2011-06</a><span style="font-family: Helvetica; ">></span></div><div style="font-family: Arial; "><br style="font-family: Helvetica; "></div><div style="font-family: Arial; "><span style="font-family: Helvetica; ">-------------------------------</span></div><div style="font-family: Arial; "><span style="font-family: Helvetica; ">How to add "abuse-c"</span></div><div style="font-family: Arial; "><span style="font-family: Helvetica; ">-------------------------------</span></div><div style="font-family: Arial; "><br style="font-family: Helvetica; "></div><div style="font-family: Arial; "><span style="font-family: Helvetica; ">An explanation of how to add "abuse-c:" to an LIR's ORGANISATION object </span><span style="font-family: Helvetica; ">as well as how to fine-tune abuse contact information for </span><span style="font-family: Helvetica; ">sub-allocations and assignments is outlined here:</span></div><div style="font-family: Arial; "><span style="font-family: Helvetica; "><</span><a href="https://labs.ripe.net/Members/denis/creating-and-finding-abuse-contacts-in-the-ripe-database" style="font-family: Helvetica; ">https://labs.ripe.net/Members/denis/creating-and-finding-abuse-contacts-in-the-ripe-database</a><span style="font-family: Helvetica; ">></span></div><div style="font-family: Arial; "><br style="font-family: Helvetica; "></div><div style="font-family: Arial; "><span style="font-family: Helvetica; ">Please kindly consider adding abuse contact information as soon as </span><span style="font-family: Helvetica; ">possible to the ORGANISATION object(s) you control or maintain in the </span><span style="font-family: Helvetica; ">RIPE Database.</span></div><div style="font-family: Arial; "><br style="font-family: Helvetica; "></div><div style="font-family: Arial; "><span style="font-family: Helvetica; ">Kind Regards,</span></div><div style="font-family: Arial; "><br style="font-family: Helvetica; "></div><div style="font-family: Arial; "><span style="font-family: Helvetica; ">Kaveh Ranjbar,</span></div><div style="font-family: Arial; "><span style="font-family: Helvetica; ">RIPE NCC Database Group Manager</span></div><div><span style="font-family: Helvetica; "><br></span></div></body></html>