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/anti-abuse-wg@ripe.net/
[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
Wed Mar 20 15:38:25 CET 2019
Definitively, authors will try to draft something for that, but specific text suggestions to the list are always very welcome ! (actually … please do so) At the moment I can think in the line: “Direct peers allowing the hijack thru their networks will be warned the first time, but may be considered by the experts evaluation to be a party involved in case of subsequent deliberated hijacks cases” Regards, Jordi El 20/3/19 14:58, "anti-abuse-wg en nombre de Andrey Korolyov" <anti-abuse-wg-bounces at ripe.net en nombre de andrey at xdel.ru> escribió: On Wed, Mar 20, 2019 at 4:36 PM Ricardo Patara <ricpatara at gmail.com> wrote: On this line of one ISP trying to make damage to other. One might abuse a vulnerable router (thousand out there), create a tunnel to it and announce hijacked blocks originated from victims ASN. Both, victim ASN and vulnerable router owner, would be damaged and no traces of criminal. How could they defend themselves to the so called group of experts? And things in this line had happened already. Regards, That's exactly my point from above for distributing responsibility over things that AS may do over its direct peers :) With example from Furio all ASNs in proposed topology could be blamed at once, for example. Determining exact topology may be somewhat not trivial, but not as hard as paper relations where both sides are claiming their innocence. So, for this version of proposal, I rather NAK it because it brings more potential mess than the usefulness against bad actors. ********************************************** 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/anti-abuse-wg/attachments/20190320/bbd33028/attachment.html>
- 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 ]