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] 2019-03 New Policy Proposal (BGP Hijacking is a RIPE Policy Violation)
- Previous message (by thread): [anti-abuse-wg] 2019-03 New Policy Proposal (BGP Hijacking is a RIPE Policy Violation)
- Next message (by thread): [anti-abuse-wg] 2019-03 New Policy Proposal (BGP Hijacking is a RIPE Policy Violation)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
JORDI PALET MARTINEZ
jordi.palet at consulintel.es
Sat Mar 23 22:42:20 CET 2019
El 23/3/19 22:33, "anti-abuse-wg en nombre de Ronald F. Guilmette" <anti-abuse-wg-bounces at ripe.net en nombre de rfg at tristatelogic.com> escribió: In message <CALZ3u+bpTu+R63s_O_Fqr-Qz3DaFh1e9N+7dD1WbzSn028cDHA at mail.gmail.com> =?UTF-8?Q?T=C3=B6ma_Gavrichenkov?= <ximaera at gmail.com> wrote: >2. OTOH the ultimate result (membership cancellation) may be seen as a >very heavy punishment. Did you have some particular alternative in mind that you wanted to propose? Sending the miscreant hijacker to bed without supper perhaps? >- hire a script kiddie who will break into that company's Mikrotik; >- announce roughly half of IPv4 address space through that breach just >for it to be surely on the news; >- relax and enjoy watching your competition disappearing in no later >than 2,5 months. I do believe that the main idea here was *not* to have the nuclear missles on a hair-trigger *or* to launch them within a few minutes of the beginning of a hijacking event, but rather to *notify* the party responsible, and then, if and ONLY IF absolutely NO ACTION is taken to resolve the problem after some reasonable period of time, then, and only then, it would *begin* to be a real possibility that sanctions would be applied. Believe me, none of the sponsors or proponents of this proposal wants to see the nuclear missles launched mistakenly, for example, in response to a falling meteor or a volcanic eruption somewhere. Any such premature over-reaction would quite obviously be Bad, and that passage of time usually serves to clarify intent. I think is very obvious that the experts (and the board as the last instance) will make sure that when a warning is sufficient (specially first time even for a clear hijack if there are no *very clear* evidences that it is intentional), but if the same organization or the same people hiding behind another organization, is repeating once and against, then it is time to stop it. We can have more explicit text about that, but I think we must trust the experts judgement, and that's why there is an appeal chance and a final ratification step. As you said, and thanks for that, *IT IS OUR MORAL AND ETHICAL RESPONSIBILITY*. Regards, rfg ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.
- Previous message (by thread): [anti-abuse-wg] 2019-03 New Policy Proposal (BGP Hijacking is a RIPE Policy Violation)
- Next message (by thread): [anti-abuse-wg] 2019-03 New Policy Proposal (BGP Hijacking is a RIPE Policy Violation)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]