This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[anti-abuse-wg] [routing-wg] 2019-08 New Policy Proposal (RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space) to be discussed on Routing Working Group Mailing List
- Previous message (by thread): [anti-abuse-wg] [routing-wg] 2019-08 New Policy Proposal (RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space) to be discussed on Routing Working Group Mailing List
- Next message (by thread): [anti-abuse-wg] 2019-08 New Policy Proposal (RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space) to be discussed on Routing Working Group Mailing List
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ronald F. Guilmette
rfg at tristatelogic.com
Tue Dec 24 04:16:54 CET 2019
In message <20191223180753.af7f9f79718891d8e76b551cf73e1563.1c863887b3.mailapi@ email19.godaddy.com>, "Fi Shing" <phishing at storey.xxx> wrote: >You're suggesting that RIR should have reasonable oversight of internet >resources? Not really. My comments weer directed rather explicitly at IRRs, which is a somewhat different set of entities, albeit with a considerable overlap. >In reality, the RIR (and ICANN) should be arrested for aiding & abetting >serious crimes. >... >Absolutely the RIR employees and ICANN should be arrested and imprisoned. Thank you for sharing Mr. Fi Shing. I myself would not go quite that far, even retorically, and indeed, I am conflicted about even lesser remedies. On the one hand, part of me would like nothing better than to see certain poorly maintained IRRs end up on the business end of at least one civil legal action charging vicarious liability and/or professional negligence. This would quite certainly get everyone's attention. On the other hand, I am mindful of the fact that even the vague possibility of some such civil legal action has been asserted as the basis for ARIN's demand for indemnification from all those wishing to avail themselves of ARIN's RPKI-related services, and that this in turn has purportedly been responsible for retarding the adoption of RPKI materially and globally. Given this contextual backdrop, I continue to hope that we in the technical community will continue, as we have, to try find ways to solve what are fundamentally technical problems of our own making, without resort to fisticuffs, war, attorneys, or law enforcement. Wherever possible, we should clean up our own messes, and serious public/peer pressure on the wayward IRRs has not yet been adequately explored as a means to the desired result. Regards, rfg
- Previous message (by thread): [anti-abuse-wg] [routing-wg] 2019-08 New Policy Proposal (RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space) to be discussed on Routing Working Group Mailing List
- Next message (by thread): [anti-abuse-wg] 2019-08 New Policy Proposal (RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space) to be discussed on Routing Working Group Mailing List
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]