<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 13 Oct 2020, at 11:29 AM, Anthony Ubah <<a href="mailto:ubah.tonyiyke@gmail.com" class="">ubah.tonyiyke@gmail.com</a>> wrote:<br class="">
<div>
<blockquote type="cite" class=""><br class="Apple-interchange-newline">
<div class="">
<div dir="auto" class="">
<div dir="auto" class="">Dear John,<br class="">
</div>
<div dir="auto" class=""><br class="">
</div>
<div dir="auto" class="">Thanks for your prompt reply. I'd like to point out the value for us to communicate directly rather than with intermediaries as it is a more effective process.</div>
</div>
</div>
</blockquote>
<div>
<blockquote type="cite" class=""><br class="">
</blockquote>
</div>
<blockquote type="cite" class="">
<div class="">
<div dir="auto" class="">
<div dir="auto" class="">5.7.4.2 The recipient must be an AFRINIC or any RIR member, legacy holders in any region</div>
<div dir="auto" class=""><br class="">
</div>
<div dir="auto" class="">This clause is never intended to put a limit on the other RIR’s recipient requirement. It simply puts a requirement for the AFRINIC region.</div>
<div dir="auto" class=""><br class="">
</div>
<div dir="auto" class="">As members are the only RIR customers in our region, it can be interpreted as "the recipient can be customers of other RIR". Will ARIN accept such clarification?</div>
<div dir="auto" class=""><br class="">
</div>
<div dir="auto" class="">Or, would a rewording of “The transfer recipient must be an AFRINIC member or any RIR member or legacy holders in any region, or any kind of entities as other RIRs deem proper” better clarify our intention? We would prefer not to modify
policy text at this late stage of policy proposal, but if ARIN insists, we will talk to the chairs in our policy community to see if such editorial change would be acceptable.</div>
<div dir="auto" class=""><br class="">
</div>
<div dir="auto" class="">As policy author, we are not lawyers, nor do we consult with lawyers while we are writing policy proposal. We appreciate if ARIN can tolerate such fine wording in the policy text and accept a more open “intention” oriented interpretaion.</div>
</div>
</div>
</blockquote>
<br class="">
</div>
<div>Anthony - </div>
<div><br class="">
</div>
<div><span class="Apple-tab-span" style="white-space:pre"></span>Your local RIR is your best resource for such engagement, as they can help you with clarity of language and will ultimately need to implement any policy adopted in your region. </div>
<div><br class="">
</div>
<div><span class="Apple-tab-span" style="white-space:pre"></span>We will continue to provide formal reviews of InterRIR transfer compatibility as requested by other RIRs – my only advice regarding inter-RIR transfer policy language is a suggestion to be explicit
as possible about requirements imposed on those outside your region to the extent feasible. No specific wording is necesary, but as means of an example, you can see how we handle the requirements in the ARIN NRPM 8.4 clauses – </div>
<div><br class="">
</div>
<div><i class=""><b class=""><span class="Apple-tab-span" style="white-space: pre;"></span>• Source entities outside of the ARIN region must ...</b></i></div>
<div>
<div class=""><b class=""><span class="Apple-tab-span" style="font-style: italic; white-space: pre;"></span><i class="">• Source entities within the ARIN region must ….</i></b></div>
<div class="">
<div style="font-style: italic; font-weight: bold;" class=""><span class="Apple-tab-span" style="white-space: pre;"></span>• The conditions on a recipient outside of the ARIN region will be ...<br class="">
</div>
<div style="font-style: italic; font-weight: bold;" class=""><span class="Apple-tab-span" style="white-space: pre;"></span>• Recipients within the ARIN region must …</div>
<div style="font-style: italic; font-weight: bold;" class=""><br class="">
</div>
<div class=""><span class="Apple-tab-span" style="font-style: italic; font-weight: bold; white-space: pre;"></span>Such clarity helps insure that there is complete understanding of the policy intent and any conditions that ARIN might need to consider during
its review. ARIN does not ever require any particular language, but clearer policy language makes for faster and more accurate reviews of compatibility with our InterRIR transfer policy requirements. </div>
</div>
<div class=""><br class="">
</div>
<div class="">Best wishes,</div>
<div class="">/John</div>
<div class=""><br class="">
</div>
<div class="">
<div class="">John Curran</div>
<div class="">President and CEO</div>
<div class="">American Registry for Internet Numbers</div>
</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
</div>
</body>
</html>