<html><head></head><body><div style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:13px;"><div style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:13px;"><div style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:13px;"><div style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:13px;"><div><div><br></div><div><br></div><div>Hi,</div><div><br></div><div>> <span style="font-family: "Helvetica Neue", Helvetica, Arial, sans-serif;">Where in the proposed policy does it say that RIPE is going to de-register anyone?</span></div><div><br></div><div><br></div><div>Right at the end it does mention closure of memberships:</div><div><br></div><div><div><br></div><div>>b. Arguments opposing the proposal</div><div>></div><div>>The proposal would result in increased workload for RIPE NCC, especially when following up on unresponsive abuse contact >information.</div><div>>If organisations are not cooperative, the RIPE NCC ultimately has the possibility to close their RIPE NCC membership and deregister >their Internet number resources.</div></div><div><br></div><div><br></div><div>This is already somewhat in the procedure of the NCC in the form of unresponsiveness of an LIR, I don't believe that any active LIRs have ever been closed due to this though:</div><div><br></div><div><a href="https://www.ripe.net/publications/docs/ripe-676#a1211a" rel="nofollow" target="_blank">https://www.ripe.net/publications/docs/ripe-676#a1211a</a><br></div><div><br></div><div><br></div><div><br></div><div>There are some other issues that arises from this policy proposal.</div><div><br></div><div>Numbers are more what matters here.</div><div>The abuse-c is not only registered on LIR's Org Objects, but by some other type of organisations as well.</div><div><br></div><div>The total amount of unique abuse-c is around 77K.</div><div><br></div><div>We have ~16K LIRs soon to be 17K.</div><div><br></div><div>That leaves ~60k abuse-c spread on OTHER type of organisation objects.</div><div><br></div><div>How many sponsored end-user organisation holding PI/ASN are there?<br></div><div>How many organisation objects were created to delegate the responsibility of the abuse-c to the actual assignments/sub-allocation etc..?</div><div>What about Legacy space, which comes in two flavours nowadays, signed up with NCC or not, how to handle each case?</div><div>And lastly, out of region ASNs that may have added the abuse-c to their org object in the RIPE Database?</div><div><br></div><div><br></div><div>Who would be responsible for verifying what?</div><div><br></div><div>RIPE NCC verifies the LIR <span style="color: rgb(0, 0, 0); font-family: "Helvetica Neue", Helvetica, Arial, sans-serif;">abuse-mailbox</span> , seems logical?</div><div><br></div><div>But then we have sponsored resources such as PI and ASNs, Legacy that have a contract with the NCC, Legacy without contract, and possibly out of region ASNs.</div><div><br></div><div><br></div><div>Too many unknowns.</div><div>I must oppose the current form of this policy proposal.</div><div><br></div></div><div><br></div><div>Cheers,<br>David Hilario</div><div><br></div><div><br></div>
</div></div></div><div id="ydpabb9f4cayahoo_quoted_5817326310" class="ydpabb9f4cayahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Thursday, September 7, 2017, 5:06:09 PM GMT+3, Michele Neylon - Blacknight <michele@blacknight.com> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div dir="ltr">Peter<br clear="none"><br clear="none">Where in the proposed policy does it say that RIPE is going to de-register anyone?<br clear="none"><br clear="none">I can’t see any language for that. All it says is:<br clear="none"><br clear="none">“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.”<br clear="none"><br clear="none">Also, if your abuse-c email address is valid it’ll take you about 30 seconds once a year to validate it. <br clear="none"><br clear="none">Regards<br clear="none"><br clear="none">Michele<br clear="none"><br clear="none"><br clear="none">--<br clear="none">Mr Michele Neylon<br clear="none">Blacknight Solutions<br clear="none">Hosting, Colocation & Domains<br clear="none"><a shape="rect" href="https://www.blacknight.com/" rel="nofollow" target="_blank">https://www.blacknight.com/</a><br clear="none"><a shape="rect" href="http://blacknight.blog/" rel="nofollow" target="_blank">http://blacknight.blog/</a><br clear="none">Intl. +353 (0) 59 9183072<br clear="none">Direct Dial: +353 (0)59 9183090<br clear="none">Personal blog: <a shape="rect" href="https://michele.blog/" rel="nofollow" target="_blank">https://michele.blog/</a><br clear="none">Some thoughts: <a shape="rect" href="https://ceo.hosting/ " rel="nofollow" target="_blank">https://ceo.hosting/ </a><br clear="none">-------------------------------<br clear="none">Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty<br clear="none">Road,Graiguecullen,Carlow,R93 X265,Ireland Company No.: 370845<br clear="none"><div class="ydpabb9f4cayqt3516018881" id="ydpabb9f4cayqtfd37067"></div></div></div>
</div>
</div></div></body></html>