[arin-ppml] [EXT] Re: Open Petition for ARIN-prop-266: BGP Hijacking is an ARIN Policy Violation

Keith W. Hare Keith at jcc.com
Fri May 3 11:24:03 EDT 2019


So far, I have seen lots of discussion of the issue but I have not seen a single concise coherent complete definition of the BGP hijacking problem that includes:

·         What technical mechanisms are used to create a BGP hijack

·         How BGP hijacking is initiated

·         Why BGP hijacking is possible

·         The frequency of BGP hijacking instances

·         How long BGP hijacking instances last

·         The locations of BGP hijacking instances

·         How information about BGP hijacking instances can be gathered

Without a really clear definition of the problem, it is hard to evaluate the effectiveness of the proposed process.

So far, it is not at all clear to me how the process described in proposal 266 will have any effect on the problem, but that may be because I do not fully understand the problem.


From: ARIN-PPML [mailto:arin-ppml-bounces at arin.net] On Behalf Of Andrew Bagrin
Sent: Friday, May 3, 2019 10:05 AM
To: Marilson Mapa <marilson.mapa at gmail.com>
Cc: arin-ppml at arin.net
Subject: Re: [arin-ppml] [EXT] Re: Open Petition for ARIN-prop-266: BGP Hijacking is an ARIN Policy Violation

I'm curious why do people not want to let ARIN try to start getting involved to help resolve the issue of hijacking?

Are you doing hijacking and don't want interference?
Are you running a competitive service that you charge for?

Does anyone believe there is a valid reason to hijack and advertise IP space that you do not own? (when the owner of that space does not want you to advertise it)

Why would anyone be against ARIN having a process to help resolve these issues?  Sure we can question how effective it will be, but anything will be more effective than nothing, and by actually doing, failing and learning, ARIN will only improve and refine the process. We will all learn from this.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20190503/8eb55c89/attachment-0002.html>

More information about the ARIN-PPML mailing list