<html><head></head><body><div style="color:#000; background-color:#fff; font-family:Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px"><div id="yui_3_16_0_ym19_1_1492103161136_522879"><span>Hi David</span></div><div id="yui_3_16_0_ym19_1_1492103161136_522887"><span><br></span></div><div dir="ltr" id="yui_3_16_0_ym19_1_1492103161136_522886"><span id="yui_3_16_0_ym19_1_1492103161136_523039">The list you wrote below proves my point. You have used your knowledge of the hierarchy and relationships to make that. Many consumers of this data don't have that knowledge. I wasn't suggesting we document everyone on earth that could be responsible for abuse handling. The point I am trying to make is that an email address is anonymous. 'Someone/some organisation' made that email address available to report abuse to. Do abuse complainers need to know who that someone is? And it was a question that I was hoping people would answer for me. Regardless of what option we take to solve the problem statement for "abuse-c:", it may still be important to know what information people need to know or should have. That may impact on how we provide this information to consumers.</span></div><div id="yui_3_16_0_ym19_1_1492103161136_523148" dir="ltr"><span id="yui_3_16_0_ym19_1_1492103161136_523039"><br></span></div><div id="yui_3_16_0_ym19_1_1492103161136_523242" dir="ltr"><span id="yui_3_16_0_ym19_1_1492103161136_523039">If the consensus is to add an abuse contact to resource objects we should not add "abuse-mailbox:" to resource objects. It should be "abuse-c:".</span></div><div id="yui_3_16_0_ym19_1_1492103161136_523243" dir="ltr"><span id="yui_3_16_0_ym19_1_1492103161136_523039"><br></span></div><div id="yui_3_16_0_ym19_1_1492103161136_523244" dir="ltr"><span id="yui_3_16_0_ym19_1_1492103161136_523039">cheers</span></div><div id="yui_3_16_0_ym19_1_1492103161136_523245" dir="ltr"><span id="yui_3_16_0_ym19_1_1492103161136_523039"><br></span></div><div id="yui_3_16_0_ym19_1_1492103161136_523246" dir="ltr"><span id="yui_3_16_0_ym19_1_1492103161136_523039">denis</span></div><div id="yui_3_16_0_ym19_1_1492103161136_523247" dir="ltr"><span id="yui_3_16_0_ym19_1_1492103161136_523039"><br></span></div><div id="yui_3_16_0_ym19_1_1492103161136_523248" dir="ltr"><span id="yui_3_16_0_ym19_1_1492103161136_523039">co-chair DB-WG<br></span></div><div id="yui_3_16_0_ym19_1_1492103161136_522888" class="qtdSeparateBR"><br><br></div><div style="display: block;" id="yui_3_16_0_ym19_1_1492103161136_522894" class="yahoo_quoted"> <div id="yui_3_16_0_ym19_1_1492103161136_522893" style="font-family: Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;"> <div id="yui_3_16_0_ym19_1_1492103161136_522892" style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, Sans-Serif; font-size: 16px;"> <div id="yui_3_16_0_ym19_1_1492103161136_522891" dir="ltr"> <font id="yui_3_16_0_ym19_1_1492103161136_522890" face="Arial" size="2"> <hr id="yui_3_16_0_ym19_1_1492103161136_522889" size="1"> <b><span style="font-weight:bold;">From:</span></b> David Hilario <fransossen@yahoo.com><br> <b><span style="font-weight: bold;">To:</span></b> denis walker <ripedenis@yahoo.co.uk>; Sebastian Wiesinger <sebastian@karotte.org>; "db-wg@ripe.net" <db-wg@ripe.net> <br> <b><span style="font-weight: bold;">Sent:</span></b> Friday, 21 April 2017, 6:12<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: [db-wg] NWI-7 proposal for fixing "abuse-c:" problems<br> </font> </div> <div id="yui_3_16_0_ym19_1_1492103161136_522905" class="y_msg_container"><br><div id="yiv8792973661"><div id="yui_3_16_0_ym19_1_1492103161136_522904"><div id="yui_3_16_0_ym19_1_1492103161136_522903" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:small;"><div id="yui_3_16_0_ym19_1_1492103161136_522902"><div><br clear="none"></div><div><br clear="none"></div><div></div><div id="yui_3_16_0_ym19_1_1492103161136_523153">Hi Denis, <br clear="none"> <br clear="none">On Thursday, April 20, 2017, 7:34:50 PM GMT+8, denis walker via db-wg <db-wg@ripe.net> wrote: <br clear="none">> I think you misunderstood the point about email being (in)sufficient information. I agree almost all abuse reports come via email. My >point was, what happens if the complainant gets no response to the email complaint? If the email address is all the information they >have, then they hit a brick wall. They don't know what organisation, company, individual sits behind that email address. But again, if this >is the way we move forward then we have to put our business analyst and software engineering hats on and solve the problem by >providing better information to consumers of this data. <br clear="none"> <br clear="none">To be fair, no one can actually tell who should be contacted as the "abuse" can be of so many kinds, the definition of abuse itself never even reached any firm definition I believe. <br clear="none"> <br clear="none">Who should be contacted, in a somewhat relevant order: <br clear="none">The registration information in the Assignment itself? </div><div id="yui_3_16_0_ym19_1_1492103161136_522901">The registration information in any intermediate layer found between an assignment and an allocation?<br clear="none">The LIR that issued the Assignment? <br clear="none">The sponsoring LIR, in case of PI? <br clear="none">The AS announcing the space? <br clear="none">The sponsoring LIR of the AS number announcing the space? <br clear="none">The peering AS numbers? <br clear="none">The RIPE NCC? <br clear="none">The other RIRs?</div><div>**end of RIPE Database scope of information**</div><div>For other RIRs, repeat all of the above and add NIRs for some of them just to get extra complexity for everyone... </div><div>Their local LEAs?</div><div id="yui_3_16_0_ym19_1_1492103161136_523157"><br clear="none">From either policy, Database or real life point of view, all the above are valid contacts and can be relevant in reporting abuse depending on its nature. <br clear="none"> <br clear="none">So other than allowing/enabling an easy way for RIPE Database users that want clear ways of getting abuse report and to get that registered and displayed on queries, I don't believe it is in the power of anyone to guess where the abuse report should go. <br clear="none"> <br clear="none">When a user does not understand hierarchical delegation queries the Database, they also probably have no clue of route announcements, sponsoring LIRs, RIR system and so on, the educational part will be quite big then. <br clear="none">I do believe that that educational information part can be made available in a simple language so that the ones who really care, can learn and crawl through the complex hierarchy and policies and the others will just give up or contact someone they know to do it for them. <br clear="none"> <br clear="none">Keep in mind as well that no DB data input policy or rules will ever make the "abuser" care about any reports they might receive, this discussion is only for the people who care about receiving reports, it would help a bit for the ones reporting when getting in touch with good networks and will have no effects ion reporting to "abusers" on bad networks. </div><div><br clear="none"></div><div id="yui_3_16_0_ym19_1_1492103161136_523165"><br clear="none"></div><div id="yui_3_16_0_ym19_1_1492103161136_523171"><br clear="none"></div><div id="yui_3_16_0_ym19_1_1492103161136_523172">On the proposed solution with contact-org, one of the main complaints was the need to create an org Object per abuse-email, it is not alleviating that issue.<br clear="none"> <br clear="none">Let's not make the life of good network harder, it should be simple to manage these contact details, have an abuse-mailbox: added to inetnum could be a simple solution, LIR portal gives you an overview of all your registered objects primary keys and the abuse email linked to them.</div><div id="yui_3_16_0_ym19_1_1492103161136_523176"><br clear="none"></div><div id="yui_3_16_0_ym19_1_1492103161136_523175">If you want to change that, click edit/restore default/add and change the email, the first time that you replace the default value a small pop-up informing you that an abuse-mailbox: will be added to the object to replace the default abuse-c: value, done.</div><div> </div><div>No need to learn a new Org object hierarchy or how to make mass updates to the RIPE Database to change the abuse email for your cloud services and keep the "old" abuse email for your ISP services.<br clear="none"></div><div><br clear="none"></div><div>People who would prefer to do this via email/sync/webupdate, can still do it as well, no problem, it isn't breaking any systems.</div><div><br clear="none"></div><div>Does anyone know if PI holders have access to an LIR portal like system?<br clear="none"> <br clear="none">Cheers <br clear="none">David <br clear="none">Co-chair DB-WG<div class="yiv8792973661yqt2507165921" id="yiv8792973661yqtfd54433"><br clear="none"></div></div></div><div class="yiv8792973661yqt2507165921" id="yiv8792973661yqtfd61119"><div class="yiv8792973661ydp4005210fydp69e58754yahoo_quoted" id="yiv8792973661ydp4005210fydp69e58754yahoo_quoted_3421382943"><div><div id="yiv8792973661ydp4005210fydp69e58754yiv9068547633"><div style="color:#000;background-color:#fff;font-family:Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px;"><div class="yiv8792973661ydp4005210fydp69e58754yiv9068547633qtdSeparateBR" id="yiv8792973661ydp4005210fydp69e58754yiv9068547633yui_3_16_0_ym19_1_1492103161136_410763"><br clear="none"></div><div class="yiv8792973661ydp4005210fydp69e58754yiv9068547633yqt9952223291" id="yiv8792973661ydp4005210fydp69e58754yiv9068547633yqt45579"><div class="yiv8792973661ydp4005210fydp69e58754yiv9068547633yahoo_quoted" id="yiv8792973661ydp4005210fydp69e58754yiv9068547633yui_3_16_0_ym19_1_1492103161136_410767" style="display:block;"> <div id="yiv8792973661ydp4005210fydp69e58754yiv9068547633yui_3_16_0_ym19_1_1492103161136_410766" style="font-family:Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px;"> <div id="yiv8792973661ydp4005210fydp69e58754yiv9068547633yui_3_16_0_ym19_1_1492103161136_410765" style="font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, Sans-Serif;font-size:16px;"> <div dir="ltr" id="yiv8792973661ydp4005210fydp69e58754yiv9068547633yui_3_16_0_ym19_1_1492103161136_410764"> <font id="yiv8792973661ydp4005210fydp69e58754yiv9068547633yui_3_16_0_ym19_1_1492103161136_410858" face="Arial" size="2"> </font><hr id="yiv8792973661ydp4005210fydp69e58754yiv9068547633yui_3_16_0_ym19_1_1492103161136_410857" size="1"> <b><span style="font-weight:bold;">From:</span></b> Sebastian Wiesinger via db-wg <db-wg@ripe.net><br clear="none"> <b><span style="font-weight:bold;">To:</span></b> db-wg@ripe.net <br clear="none"> <b><span style="font-weight:bold;">Sent:</span></b> Thursday, 20 April 2017, 11:47<br clear="none"> <b><span style="font-weight:bold;">Subject:</span></b> Re: [db-wg] NWI-7 proposal for fixing "abuse-c:" problems<br clear="none"> </div> <div class="yiv8792973661ydp4005210fydp69e58754yiv9068547633y_msg_container" id="yiv8792973661ydp4005210fydp69e58754yiv9068547633yui_3_16_0_ym19_1_1492103161136_410768"><br clear="none">* denis walker via db-wg <<a rel="nofollow" shape="rect" ymailto="mailto:db-wg@ripe.net" target="_blank" href="mailto:db-wg@ripe.net">db-wg@ripe.net</a>> [2017-04-18 16:11]:<br clear="none">> Colleagues Below is a proposal for fixing the problems with<br clear="none">> "abuse-c:" as shown in the problem statement for<br clear="none">> NWI-7 <a rel="nofollow" shape="rect" target="_blank" href="https://www.ripe.net/manage-ips-and-asns/db/numbered-work-items">https://www.ripe.net/manage-ips-and-asns/db/numbered-work-items</a><br clear="none">> <br clear="none">> I look forward to comments.<br clear="none"><br clear="none">Hello Denis,<br clear="none"><br clear="none">thank you for this. I've read it three times now to understand how it<br clear="none">it works and I think this underlines what I tried to say in the<br clear="none">original problem statement:<br clear="none"><br clear="none"> The problem statement looks good to me, I only would like to comment<br clear="none"> that the current way seems *too* complicated / bloated for a lot of<br clear="none"> people. So a solution should aim to be more "lightweight" for lack of<br clear="none"> a better word. That might happen naturally when tackling the problem<br clear="none"> statement but nontheless I would like to mention it.<br clear="none"><br clear="none">So... I don't think this will make it easier to understand or<br clear="none">implement for people who just want to add an abuse contact and<br clear="none">subsequently will not improve abuse contact information in the<br clear="none">database.<br clear="none"><br clear="none">> It's clear from the problem statement that some situations cannot be<br clear="none">> handled with the current arrangement. Mainly because it would<br clear="none">> require a reference to a second ORGANISATION object from a resource<br clear="none">> object. This is not possible with the syntax and business rules in<br clear="none">> the database.<br clear="none"><br clear="none">Also the RIPE NCC has stated that it does not want two ORG-IDs for an<br clear="none">enduser. If this goes forward I think it would be a good idea to have<br clear="none">at least a statement from the RIPE NCC that they would be okay with an<br clear="none">enduser having multiple chained organisation objects for this.<div class="yiv8792973661ydp4005210fydp69e58754yiv9068547633yqt3317122091" id="yiv8792973661ydp4005210fydp69e58754yiv9068547633yqtfd57085"><br clear="none"><br clear="none">> There is also a question over the double indirection to get to the<br clear="none">> abuse contact information, ie resource object -> ORGANISATION object<br clear="none">> -> ROLE object. If it is accepted that an email on it's own is not<br clear="none">> sufficient information and the clear link to the organisation with<br clear="none">> responsibility for handling abuse is also required, then this double<br clear="none">> indirection is needed. With the right tools it's easy to manage this<br clear="none">> data. This point is not a technical or operational show stopper.<br clear="none">> It's more about who needs what information and how do they get it.</div><br clear="none"><br clear="none">I think it is a show stopper. You have to understand the logic and<br clear="none">implement the tools. Many LIRs will shy away from that. Instead just<br clear="none">adding an "abuse-c:" field to an object is easily understandable.<br clear="none"><br clear="none">As for email being not sufficient information, in the last 10+ years I<br clear="none">cannot remember a single abuse complaint that was not done via email.<br clear="none">The only exception might be some special cases that directly involve<br clear="none">law enforcement or such, and for those the main ORG object should be<br clear="none">enough.<br clear="none"><br clear="none">To sum it up, I don't think that this approach will make it easier to<br clear="none">add and maintain abuse information in the database and as such will<br clear="none">not improve the goal of having accurate and up-to-date abuse contact<br clear="none">information. I would not support the proposal in this form.<br clear="none"><br clear="none">Regards<br clear="none"><br clear="none">Sebastian<br clear="none"><br clear="none">-- <br clear="none">GPG Key: 0x93A0B9CE (F4F6 B1A3 866B 26E9 450A 9D82 58A2 D94A 93A0 B9CE)<br clear="none">'Are you Death?' ... IT'S THE SCYTHE, ISN'T IT? PEOPLE ALWAYS NOTICE THE SCYTHE.<br clear="none"> -- Terry Pratchett, The Fifth Elephant<br clear="none"><br clear="none"><br clear="none"></div> </div> </div> </div></div></div></div></div></div></div></div></div></div><br><br></div> </div> </div> </div></div></body></html>