<html><body><span style="font-family:Verdana; color:#000; font-size:12pt;"><div>This does not address black hole email addresses, nor does it validate that an email address is an abuse email address. I could put YOUR email address as my abuse contact. Because your email address is valid, it would pass your check? </div><div><br></div><div>And then an individual would have to prove that an email address is not working at all, to complain to RIPE? But your email address does work?</div><div><br></div><div>How is it that you have spent how ever many months on this garbage, and come out with exactly the same position you were in before hand?</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div>
<blockquote id="replyBlockquote" webmail="1" style="border-left: 2px solid blue; margin-left: 8px; padding-left: 8px; font-size:10pt; color:black; font-family:verdana;">
<div id="wmQuoteWrapper">
-------- Original Message --------<br>
Subject: Re: [anti-abuse-wg] Decision on Proposal 2017-02<br>
From: Marco Schmidt <<a href="mailto:mschmidt@ripe.net">mschmidt@ripe.net</a>><br>
Date: Thu, March 15, 2018 12:32 am<br>
To: <a href="mailto:anti-abuse-wg@ripe.net">anti-abuse-wg@ripe.net</a><br>
<br>
Dear colleagues,<br>
<br>
Please allow me to provide some clarification in regards to "relevant<br>
RIPE Policies and RIPE NCC procedures" for this proposal, and some<br>
details around how these have changed over time.<br>
<br>
Since 2003, the RIPE IPv4 policy has stated that the RIPE NCC can close<br>
LIRs for reasons such as policy violations and unresponsiveness. This<br>
wording has not changed in the past 15 years (section 12.0):<br>
<a href="https://www.ripe.net/publications/docs/ripe-288/at_download/pdf">https://www.ripe.net/publications/docs/ripe-288/at_download/pdf</a><br>
<br>
The RIPE Policy "Contractual Requirements for Provider Independent<br>
Resource Holders in the RIPE NCC Service Region" contains similar<br>
requirements for independent number resources since its creation in<br>
February 2009 (section 2.0):<br>
<a href="https://www.ripe.net/publications/docs/ripe-452">https://www.ripe.net/publications/docs/ripe-452</a><br>
<br>
Within this policy framework, the RIPE NCC developed the procedural<br>
document: "Closure of Members, Deregistration of Internet Resources and<br>
Legacy Internet Resources".<br>
<br>
The relevant section of this document for members, "1.2.1.1 Violation of RIPE<br>
Policies and RIPE NCC Procedures", has been active since March 2011.<br>
Over the past seven years, mostly editorial changes have been made to the<br>
wording of this section:<br>
<a href="https://www.ripe.net/publications/docs/ripe-517#a1211">https://www.ripe.net/publications/docs/ripe-517#a1211</a><br>
<br>
The most recent change to this procedure, in February 2018, was not<br>
directly related to the proposed policy change. It was primarily around<br>
suspension of the membership (i.e. voting rights) once the closure<br>
procedure has been activated.<br>
<br>
The following link shows the differences between the current document<br>
and the previous version. It shows that no significant changes were made to section<br>
1.2.1.1:<br>
<a href="https://www.ripe.net/publications/docs/ripe-676/@@diff-items?id=ripe-697#a1211">https://www.ripe.net/publications/docs/ripe-676/@@diff-items?id=ripe-697#a1211</a><br>
<br>
As outlined in the impact analysis, the RIPE NCC has been investigating<br>
reports of invalid abuse contacts under the current policy framework for<br>
several years now. The only difference made by the policy proposal is<br>
that it would cause us to proactively undertake this validation rather<br>
than waiting for reports.<br>
<br>
Until today, all of the abuse contact cases we investigated were<br>
resolved without ever needing to trigger the closure and deregistration<br>
procedure. However, making unresponsive resource holders aware of the<br>
possibility of closure as a final resort has helped to ensure their<br>
cooperation.<br>
<br>
Please let me reiterate that the RIPE NCC will not activate the<br>
closure procedure simply for failure to maintain the "abuse-mailbox:"<br>
attribute.<br>
<br>
The closure procedure could be activated if the resource holder refuses<br>
to provide correct abuse contact information or is unresponsive over a<br>
longer period (during which the RIPE NCC will have made several attemps<br>
to contact the resource holder via different channels). If the closure<br>
and deregistration procedure is triggered, the resource holder will<br>
still have an additional three months to resolve the problem.<br>
<br>
Kind regards,<br>
Marco Schmidt<br>
Policy Development Officer<br>
RIPE NCC<br>
<br>
Sent via RIPE Forum -- <a href="https://www.ripe.net/participate/mail/forum">https://www.ripe.net/participate/mail/forum</a><br>
<br>
</div>
</blockquote></span></body></html>