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

[Andrew Bagrin]

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.



On Thu, May 2, 2019 at 10:08 PM Marilson Mapa <marilson.mapa at gmail.com>
wrote:

> The president of ARIN describes his institution as an RIR with appropriate
> and functional policies. This is what we can deduce from his speech
> whenever he describes the performance of his institution. This same
> attitude can be seen in RIPE.
>
> "Violation can have consequence".
>
> It seems that the expression "can have" should be understood as "almost
> never", after all how to explain the rot that permeates the global
> Internet? The complaints, the lawsuits, the fines are becoming more and
> more frequent.
> I have today received as a member of BPF Cybersecurity the document ***UN
> 1st Committee Processes on Responsible State Behaviour in Cyberspace
> explainer**. *This 25-page document, addressed to ICANN, reports what
> they call disastrous behavior. It was drafted by Rubin International Law
> Firm and Notary of Israel for a Jewish religious institution.
>
> Basically they are demanding:
> "We require ICANN to terminate immediately the activities fostering
> Internet addiction, including the performance of relevant IANA functions,
> relevant gTLD activities, relevant Registry Operators' activities, relevant
> ICANN-accredited registrars' activities, including through RESP and
> amendments of registry and registrar agreements and to refrain from
> renewing the .info registry agreement with Afilias unless Afilias and its
> related companies terminate immediately activities fostering Internet
> addiction and the .info registry agreement is amended to prohibit Internet
> addiction activities."
>
> It's just one of the thousands of complaints popping up around the globe.
> And ARIN does not move a finger... It's out of the scope...
>
> Marilson
>
>
> Em qui, 2 de mai de 2019 às 17:01, John Curran <jcurran at arin.net>
> escreveu:
>
>> > On May 2, 2019, at 2:12 PM, Carlos Friaças via ARIN-PPML <
>> arin-ppml at arin.net> wrote:
>> > ...
>> > It seems evident that a RIR can't revoke legacy space. Ever.
>>
>> Carlos -
>>
>> In the case of ARIN that would be incorrect, as ARIN has revoked legacy
>> address space from parties that have violated registry policies.
>>
>> ARIN registry policies are applicable to all parties in the registry -
>> those legacy holders under RSA do have specific terms and conditions (and a
>> reduced fee schedule), but ARIN registry policies are applicable regardless
>> and violation can have consequence.
>>
>> Thanks!
>> /John
>>
>> John Curran
>> President and CEO
>> American Registry for Internet Numbers
>>
>> _______________________________________________
>> 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 contact 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 contact 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/20190503/c7d601b2/attachment.htm>