<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
On 2 May 2019, at 11:48 AM, JORDI PALET MARTINEZ via ARIN-PPML <<a href="mailto:arin-ppml@arin.net" class="">arin-ppml@arin.net</a>> wrote:<br class="">
<div>
<blockquote type="cite" class=""><br class="Apple-interchange-newline">
<div class=""><span style="caret-color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">As
said before, I’m fine if the RIRs don’t want to take actions, but they must have clear rules (policy text) that allows the victims to claim by other means if they wish. This is a way for the RIR to not get involved, but still facilitate the protection of the
member’s rights.</span></div>
</blockquote>
<br class="">
</div>
<div>Jordi - </div>
<div><br class="">
</div>
<div>To be clear, ARIN customers are issued number resources with very specific rights (see section 2 of the RSA) but all of those rights relate to their number resources in the ARIN registry. We have clear enforcement of those rights; i.e. if you believe
that someone has somehow appropriated your number resources in the ARIN registry, please contact us and we’ll promptly investigate and correct. </div>
<div><br class="">
</div>
<div>You reference some additional “member rights” with regard to routing of issued number resources, but I note that enforcing such rights over routing cannot occur unless/until the community specifically provides for their existence. </div>
<div><br class="">
</div>
<div>ARIN doesn’t (presently) constrain by contract how customers issue routes for their number resources, nor does it constrain how customers process routes received from other networks – as it has historically been the view that such a role lies outside the
scope of ARIN’s mission. ARIN cannot provide for protection of your purported routing rights until those rights are well defined & enforceable, and I would recommend some deep consideration by the community about the implications of any such change. </div>
<div><br class="">
</div>
<div>Thanks,</div>
<div>/John</div>
<div><br class="">
</div>
<div>
<div>John Curran</div>
<div>President and CEO</div>
<div>American Registry for Internet Numbers</div>
<div><br class="">
</div>
<div><br class="">
</div>
</div>
<div><br class="">
</div>
<div><br class="">
</div>
<div><br class="">
</div>
<div><br class="">
</div>
<div><br class="">
</div>
<div><br class="">
</div>
<div><br class="">
</div>
<br class="">
</body>
</html>