This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/anti-abuse-wg@ripe.net/
[anti-abuse-wg] Update on "abuse-c:" coverage in RIPE Database
- Previous message (by thread): [anti-abuse-wg] Update on "abuse-c:" coverage in RIPE Database
- Next message (by thread): [anti-abuse-wg] Update on "abuse-c:" coverage in RIPE Database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Piotr Strzyzewski
Piotr.Strzyzewski at polsl.pl
Thu Dec 5 08:33:25 CET 2013
On Wed, Dec 04, 2013 at 01:30:58PM +0100, Johan ?hlén wrote: Dear Johan > We have now reached the end of the extended period for Phase 1 of the > abuse-c project. This means that we will start the process of setting > the "abuse-c:" attribute automatically for members where it is > missing. For this we will use the publicly listed contact information > as described in the implementation plan: > https://labs.ripe.net/Members/kranjbar/implementation-details-of-policy-2011-06 > Currently, 65.8% of the IPv4 allocations have the "abuse-c:" > attribute, and by size the coverage is 74.4%. > > We will now move into Phase 2, where we will ask PI and ASN resource > holders to provide abuse contact information. We will have a > simplified form available as well as improved documentation on how to > do the update in the RIPE Database using the standard mechanisms. > Current IPv4 PI coverage is 7.7% of all PI assignment, and by size the > coverage is 13.8% And what about erx? Piotr -- gucio -> Piotr Strzyżewski E-mail: Piotr.Strzyzewski at polsl.pl
- Previous message (by thread): [anti-abuse-wg] Update on "abuse-c:" coverage in RIPE Database
- Next message (by thread): [anti-abuse-wg] Update on "abuse-c:" coverage in RIPE Database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]