Dear Piotr, It is our understanding that ripe-563, "Abuse Contact Management in the RIPE Database", does not apply to legacy resources because they are not explicitly mentioned in the policy. For this reason, legacy resources are not part of our implementation plan. https://www.ripe.net/ripe/docs/ripe-563 Kind regards, Johan Åhlén Assistant Manager, Database RIPE NCC On 5 Dec 2013, at 08:33, Piotr Strzyzewski <Piotr.Strzyzewski@polsl.pl> wrote:
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... 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@polsl.pl