[arin-ppml] prop266 - re-framing the discussion

Fernando Frediani fhfrediani at gmail.com
Thu May 2 11:49:23 EDT 2019


On 02/05/2019 12:41, Scott Leibrand wrote:
>
>
> If the hijacker is someone with no relationship with ARIN, we can’t 
> punish them by kicking them out of a club they’re not a member of. If 
> you’re ok with ARIN doing nothing about hijacks by entities who don’t 
> have ARIN resources, fine: that’s the status quo. But if you do want 
> ARIN to do something on those cases (which I believe are the vast 
> majority of hijacks) the only action I can see that ARIN could take at 
> that point is against whichever of their transit providers is 
> accepting the hijacked routes.
This policy is obviously for ARIN members which is enough for the 
region. It couldn't be different.
Other regions (and "clubs") may have similar rules that apply to their 
members and if all regions having it will cover majority of members 
worldwide.
>
> -Scott
>
>>>
>>> On May 2, 2019, at 7:18 AM, Adam Thompson <athompson at merlin.mb.ca 
>>> <mailto:athompson at merlin.mb.ca>> wrote:
>>>
>>>> Instead of focusing on whether the current proposal is or isn’t in 
>>>> scope, I suggest we re-cast the discussion as follows:
>>>>
>>>>  1. So far, we have unanimous community agreement that BGP
>>>>     hijacking is bad.
>>>>  2. So far, we have broad agreement that “something ought to be
>>>>     done” about BGP hijacking, although detailed opinions vary
>>>>     significantly.
>>>>  3. So what (else) *_can_* ARIN do about it?  (Caveat: the answer
>>>>     “/nothing/” is unacceptable to a significant proportion of PPML
>>>>     participants.)
>>>>
>>>> My suggested direction to the AC and/or the board would therefore 
>>>> be: */_Find_/* something ARIN can do to help combat the problem 
>>>> (more effectively).  If this requires expanding the scope of ARIN’s 
>>>> operations or policies, bring that back to the membership (possibly 
>>>> via PPML?) with the accompanying financial & legal analysis, as usual.
>>>>
>>>> Now the question becomes: what is the most appropriate mechanism, 
>>>> within ARIN’s existing policies, to bring a request like that to 
>>>> the AC and/or Board?  It seems clear to me that the petition 
>>>> already underway here is not meeting, and will not meet, the needs 
>>>> of the community very well.
>>>>
>>>> -Adam
>>>>
>>>> *Adam Thompson*
>>>> Consultant, Infrastructure Services
>>>> *<image001.png>*
>>>> 100 - 135 Innovation Drive
>>>> Winnipeg, MB, R3T 6A8
>>>> (204) 977-6824 or 1-800-430-6404 (MB only)
>>>> athompson at merlin.mb.ca <mailto:athompson at merlin.mb.ca>
>>>> www.merlin.mb.ca <http://www.merlin.mb.ca/>
>>>>
>>>> _______________________________________________
>>>> ARIN-PPML
>>>> You are receiving this message because you are subscribed to
>>>> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net 
>>>> <mailto:ARIN-PPML at arin.net>).
>>>> Unsubscribe or manage your mailing list subscription at:
>>>> https://lists.arin.net/mailman/listinfo/arin-ppml
>>>> Please contact info at arin.net <mailto:info at arin.net> if you 
>>>> experience any issues.
>>>
>>> _______________________________________________
>>> ARIN-PPML
>>> You are receiving this message because you are subscribed to
>>> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
>>> Unsubscribe or manage your mailing list subscription at:
>>> https://lists.arin.net/mailman/listinfo/arin-ppml
>>> Please contactinfo at arin.net  if you experience any issues.
>> _______________________________________________
>> ARIN-PPML
>> You are receiving this message because you are subscribed to
>> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net 
>> <mailto:ARIN-PPML at arin.net>).
>> Unsubscribe or manage your mailing list subscription at:
>> https://lists.arin.net/mailman/listinfo/arin-ppml
>> Please contact info at arin.net <mailto:info at arin.net> if you experience 
>> any issues.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20190502/ec976815/attachment-0002.html>


More information about the ARIN-PPML mailing list