[anti-abuse-wg] oppose 2017-02 "Regular abuse-c Validation"
- Previous message (by thread): [anti-abuse-wg] oppose 2017-02 "Regular abuse-c Validation"
- Next message (by thread): [anti-abuse-wg] oppose 2017-02 "Regular abuse-c Validation"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
David Hilario
fransossen at yahoo.com
Fri Sep 8 12:09:27 CEST 2017
Hi, > Where in the proposed policy does it say that RIPE is going to de-register anyone? Right at the end it does mention closure of memberships: >b. Arguments opposing the proposal>>The proposal would result in increased workload for RIPE NCC, especially when following up on unresponsive abuse contact >information.>If organisations are not cooperative, the RIPE NCC ultimately has the possibility to close their RIPE NCC membership and deregister >their Internet number resources. 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: https://www.ripe.net/publications/docs/ripe-676#a1211a There are some other issues that arises from this policy proposal. Numbers are more what matters here.The abuse-c is not only registered on LIR's Org Objects, but by some other type of organisations as well. The total amount of unique abuse-c is around 77K. We have ~16K LIRs soon to be 17K. That leaves ~60k abuse-c spread on OTHER type of organisation objects. How many sponsored end-user organisation holding PI/ASN are there? How many organisation objects were created to delegate the responsibility of the abuse-c to the actual assignments/sub-allocation etc..?What about Legacy space, which comes in two flavours nowadays, signed up with NCC or not, how to handle each case?And lastly, out of region ASNs that may have added the abuse-c to their org object in the RIPE Database? Who would be responsible for verifying what? RIPE NCC verifies the LIR abuse-mailbox , seems logical? 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. Too many unknowns.I must oppose the current form of this policy proposal. Cheers, David Hilario On Thursday, September 7, 2017, 5:06:09 PM GMT+3, Michele Neylon - Blacknight <michele at blacknight.com> wrote: Peter Where in the proposed policy does it say that RIPE is going to de-register anyone? I can’t see any language for that. All it says is: “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.” Also, if your abuse-c email address is valid it’ll take you about 30 seconds once a year to validate it. Regards Michele -- Mr Michele Neylon Blacknight Solutions Hosting, Colocation & Domains https://www.blacknight.com/ http://blacknight.blog/ Intl. +353 (0) 59 9183072 Direct Dial: +353 (0)59 9183090 Personal blog: https://michele.blog/ Some thoughts: https://ceo.hosting/ ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,R93 X265,Ireland Company No.: 370845 -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.ripe.net/ripe/mail/archives/anti-abuse-wg/attachments/20170908/acaa62e9/attachment.html>
- Previous message (by thread): [anti-abuse-wg] oppose 2017-02 "Regular abuse-c Validation"
- Next message (by thread): [anti-abuse-wg] oppose 2017-02 "Regular abuse-c Validation"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]