Update on "abuse-c:" coverage in RIPE Database
Dear Colleagues, 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% Here are the latest stats: -------- NETWORK NUMBERS: Total number of IPv4 allocations listed: 21,605 Number of IPv4 allocations covered with "abuse-c": 14,219 or 65.8% of IPv4 allocations Total number of IPv4 PI assignments listed: 28,250 Number of IPv4 PI assignments covered with "abuse-c": 2,170 or 7.7% of IPv4 assignments Total number of IPv6 allocations listed: 6,474 Number of IPv6 allocations covered with "abuse-c": 4,282 or 66.1% of IPv6 allocations Total number of IPv6 assignments: 1,593 Number of IPv6 assignments covered with "abuse-c": 231 or 14.5% of IPv6 assignments Total number of objects: 57,922 (IPv4: 49,855 / IPv6: 8,067) Number of objects covered with "abuse-c": 20,902 or 36.1% (IPv4: 32.9% / IPv6: 55.9%) -------- IPv4 NETWORK SIZES: Total size of IPv4 allocations listed: 595,025,920 Size of IPv4 allocations covered with "abuse-c": 442,600,448 or 74.4% Total size of IPv4 PI assigned listed: 169,504,824 Size of IPv4 PI assigned covered with "abuse-c": 23,426,416 or 13.8% Total size of listed IPv4 addresses: 764,530,744 Size of listed IPv4 addresses covered with "abuse-c": 466,026,864 or 61.0% In our last update, the coverage of IPv4 allocations, by size, was 56.8%. Today it is 74.4% -------- LIR NUMBERS: LIRs with "abuse-c:": 4,243 LIRs without "abuse-c:": 5,541 If you have any questions about theses figures, please feel free to contact us. Kind regards, Johan Åhlén Assistant Manager, Database RIPE NCC
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
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
On Fri, Dec 06, 2013 at 08:28:01AM +0100, Johan ??hlén wrote: Dear Johan
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.
Is there any obstacle to contact erx resource holders and ask them politely if they are willing to voluntarily follow the procedure? Piotr -- gucio -> Piotr Strzyżewski E-mail: Piotr.Strzyzewski@polsl.pl
Dear Piotr, We will look into filtering the legacy resources out and approaching the holders as you suggested. Enforcing the policy however is another matter as the RIPE NCC currently does not have the mandate to do so. Kind regards, Johan Åhlén Assistant Manager, Database RIPE NCC On 6 Dec 2013, at 08:42, Piotr Strzyzewski <Piotr.Strzyzewski@polsl.pl> wrote:
On Fri, Dec 06, 2013 at 08:28:01AM +0100, Johan ??hlén wrote:
Dear Johan
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.
Is there any obstacle to contact erx resource holders and ask them politely if they are willing to voluntarily follow the procedure?
Piotr
-- gucio -> Piotr Strzyżewski E-mail: Piotr.Strzyzewski@polsl.pl
Dear Colleagues The RIPE NCC has now completed Phase 1 of this project. Except for a few recent new LIRs, all LIRs now have an abuse-contact set. Regards Denis Walker Business Analyst RIPE NCC Database Team On 04/12/2013 13:30, Johan Åhlén wrote:
Dear Colleagues,
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%
Here are the latest stats:
-------- NETWORK NUMBERS:
Total number of IPv4 allocations listed: 21,605 Number of IPv4 allocations covered with "abuse-c": 14,219 or 65.8% of IPv4 allocations Total number of IPv4 PI assignments listed: 28,250 Number of IPv4 PI assignments covered with "abuse-c": 2,170 or 7.7% of IPv4 assignments Total number of IPv6 allocations listed: 6,474 Number of IPv6 allocations covered with "abuse-c": 4,282 or 66.1% of IPv6 allocations Total number of IPv6 assignments: 1,593 Number of IPv6 assignments covered with "abuse-c": 231 or 14.5% of IPv6 assignments
Total number of objects: 57,922 (IPv4: 49,855 / IPv6: 8,067) Number of objects covered with "abuse-c": 20,902 or 36.1% (IPv4: 32.9% / IPv6: 55.9%)
-------- IPv4 NETWORK SIZES:
Total size of IPv4 allocations listed: 595,025,920 Size of IPv4 allocations covered with "abuse-c": 442,600,448 or 74.4% Total size of IPv4 PI assigned listed: 169,504,824 Size of IPv4 PI assigned covered with "abuse-c": 23,426,416 or 13.8%
Total size of listed IPv4 addresses: 764,530,744 Size of listed IPv4 addresses covered with "abuse-c": 466,026,864 or 61.0%
In our last update, the coverage of IPv4 allocations, by size, was 56.8%. Today it is 74.4%
-------- LIR NUMBERS:
LIRs with "abuse-c:": 4,243 LIRs without "abuse-c:": 5,541
If you have any questions about theses figures, please feel free to contact us.
Kind regards,
Johan Åhlén Assistant Manager, Database RIPE NCC
participants (3)
-
Denis Walker -
Johan Åhlén -
Piotr Strzyzewski