<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta name=Title content=""><meta name=Keywords content=""><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Courier New";
panose-1:2 7 3 9 2 2 5 2 4 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New",serif;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Courier",serif;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:595.0pt 842.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style></head><body bgcolor=white lang=EN-GB link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='mso-fareast-language:EN-US'>As a rough indication of the impact, how many ASNs are going to be affected by this move? Has any study been made on the number of ASNs with such invalid contact information in abuse-c, and are they concentrated anywhere in particular such as on specific ISPs?<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>If the objections to this proposal were not made on philosophical grounds, and made with loud protestations that the impact on RIPE NCC staffing resources would be too great, without actually making such assessments and seeing the data on who would actually be negatively impacted by this proposal .. <o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>TL;DR – what data do we have available?<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>--srs<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span style='font-size:12.0pt;color:black'>From: </span></b><span style='font-size:12.0pt;color:black'>anti-abuse-wg <anti-abuse-wg-bounces@ripe.net> on behalf of Andreas Worbs <anw@artfiles.de><br><b>Organization: </b>Artfiles New Media GmbH<br><b>Date: </b>Wednesday, 13 September 2017 at 3:52 PM<br><b>To: </b><anti-abuse-wg@ripe.net><br><b>Subject: </b>Re: [anti-abuse-wg] 2017-02 New Policy Proposal (Regular abuse-c Validation)<o:p></o:p></span></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><p>I support this proposal, it's a good step in the right direction. Valid contact (incl abuse-c) information is necessary for such a database.<o:p></o:p></p><p>Also a validation of the abuse-c should be made with the resource registration for new resources.<o:p></o:p></p><p>Furthermore i don't know why some guys think a resource will be deregistered right after the resource is tagged as invalid. The proposal is obviuos<o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p><i>In cases where the “abuse-mailbox:” contact attribute is invalid, the RIPE NCC will follow up with the resource holder and attempt to correct the issue.</i><o:p></o:p></p></blockquote><p>So there are some more steps before it will be deregistered, so cool down. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>Am 07.09.17 um 13:59 schrieb Marco Schmidt:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre>Dear colleagues,<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>A new RIPE Policy proposal, 2017-02, "Regular abuse-c Validation", is now available for discussion.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>The goal of this proposal is to give the RIPE NCC a mandate to regularly validate "abuse-c:" information<o:p></o:p></pre><pre>and to follow up in cases where contact information is found to be invalid.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>You can find the full proposal at:<o:p></o:p></pre><pre><a href="https://www.ripe.net/participate/policies/proposals/2017-02">https://www.ripe.net/participate/policies/proposals/2017-02</a><o:p></o:p></pre><pre><o:p> </o:p></pre><pre>As per the RIPE Policy Development Process (PDP), the purpose of this four-week Discussion Phase<o:p></o:p></pre><pre>is to discuss the proposal and provide feedback to the proposer.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>At the end of the Discussion Phase, the proposer, with the agreement of the RIPE Working Group Chairs,<o:p></o:p></pre><pre>decides how to proceed with the proposal.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>We encourage you to review this proposal and send your comments to<o:p></o:p></pre><pre><a href="mailto:anti-abuse-wg@ripe.net"><anti-abuse-wg@ripe.net></a> before 6 October 2017.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Kind regards,<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Marco Schmidt<o:p></o:p></pre><pre>Policy Development Officer<o:p></o:p></pre><pre>RIPE NCC<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Sent via RIPE Forum -- <a href="https://www.ripe.net/participate/mail/forum">https://www.ripe.net/participate/mail/forum</a><o:p></o:p></pre><pre><o:p> </o:p></pre></blockquote><p class=MsoNormal><br><br><o:p></o:p></p><pre>-- <o:p></o:p></pre><pre>Kind regards<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Artfiles New Media GmbH<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Andreas Worbs<o:p></o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre>Artfiles New Media GmbH | Zirkusweg 1 | 20359 Hamburg<o:p></o:p></pre><pre>Tel: 040 - 32 02 72 90 | Fax: 040 - 32 02 72 95<o:p></o:p></pre><pre>E-Mail: <a href="mailto:support@artfiles.de">support@artfiles.de</a> | Web: <a href="http://www.artfiles.de">http://www.artfiles.de</a><o:p></o:p></pre><pre>Geschäftsführer: Harald Oltmanns | Tim Evers<o:p></o:p></pre><pre>Eingetragen im Handelsregister Hamburg - HRB 81478<o:p></o:p></pre></div></body></html>