<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Times New Roman \(Cuerpo en alfa";
panose-1:2 2 6 3 5 4 5 2 3 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EstiloCorreo20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=ES link=blue vlink=purple style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal><span class=EstiloCorreo20><span style='font-size:12.0pt'></span></span><span class=EstiloCorreo20><span lang=EN-US style='font-size:12.0pt'>Hi Mike,<o:p></o:p></span></span></p><p class=MsoNormal><span class=EstiloCorreo20><span lang=EN-US style='font-size:12.0pt'><o:p> </o:p></span></span></p><p class=MsoNormal><span class=EstiloCorreo20><span lang=EN-US style='font-size:12.0pt'>No, is not compatible, there is a nit in the text that precisely makes it against as John as confirmed. Nevertheless I only wanted to clarify the situation, I don’t think this is a topic for a continued discussion in ARIN ppml.</span></span><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'><o:p></o:p></span></p><div><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;color:black'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;color:black'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;color:black'>Regards,<o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:12.0pt'><span lang=EN-US style='font-size:12.0pt;color:black;mso-fareast-language:EN-US'>Jordi<o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:12.0pt'><span lang=EN-US style='font-size:12.0pt;color:black;mso-fareast-language:EN-US'>@jordipalet<o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:12.0pt'><span lang=EN-US style='font-size:12.0pt;color:black;mso-fareast-language:EN-US'><o:p> </o:p></span></p></div><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'><o:p> </o:p></span></p><div><div><p class=MsoNormal style='margin-left:35.4pt'>El 12/10/20 22:03, "Mike Burns" <<a href="mailto:mike@iptrading.com">mike@iptrading.com</a>> escribió:<o:p></o:p></p></div></div><div><p class=MsoNormal style='margin-left:35.4pt'><o:p> </o:p></p></div><p class=MsoNormal style='margin-left:35.4pt'>Hi Jordi,<o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'>As I mentioned on the AFRINIC list, it would not be a problem if the AFRINIC inter-regional transfer policy retained legacy status for inbound legacy resources from ARIN. I know this because this is an option for ARIN legacy addresses received inter-regionally at RIPE.<o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'>So the issue of ARIN reciprocity related to retention of legacy status for addresses received at AFRINIC is moot.<o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'>I also pointed out on that list that as you say, AFRINIC policy cannot mandate ARIN’s retention of legacy status for outbound transfers from AFRINIC.<o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'>I believe the current version in last call will prove to be compliant with ARIN staff’s designation as a reciprocal policy.<o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'>I also believe very few transfer recipients care about legacy status because the benefits are few and the costs increasing (RPKI).<o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'>It’s an insignificant point to my mind, and delaying an AFRINIC inter-regional transfer proposal in last call over it is the wrong move.<o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'>Regards,<br>Mike<o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal style='margin-left:35.4pt'><b>From:</b> ARIN-PPML <arin-ppml-bounces@arin.net> <b>On Behalf Of </b>John Curran<br><b>Sent:</b> Monday, October 12, 2020 2:35 PM<br><b>To:</b> JORDI PALET MARTINEZ <jordi.palet@consulintel.es><br><b>Cc:</b> Eddy Kayihura <eddy@afrinic.net>; Taiwo Oyewande <taiwo.oyewande88@gmail.com>; arin-ppml@arin.net<br><b>Subject:</b> [arin-ppml] Legacy number resources in the ARIN region (was: Re: Inter-RIR transfer Policy reciprocity with Afrinic_Resource Transfer Policy proposal)<o:p></o:p></p></div></div><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'>On 12 Oct 2020, at 1:37 PM, JORDI PALET MARTINEZ <<a href="mailto:jordi.palet@consulintel.es">jordi.palet@consulintel.es</a>> wrote:<o:p></o:p></p><div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p><div><p class=MsoNormal style='margin-left:35.4pt'><span style='font-size:12.0pt'>For example, I can’t imposse the condition to legacy resources transfered from AFRINIC to ARIN to lose the legacy status, because that’s against ARIN policy.<span class=apple-converted-space> </span></span><o:p></o:p></p></div></blockquote></div><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p><div><p class=MsoNormal style='margin-left:35.4pt'>Jordi - <o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'>It’s probably worth elaborating a bit on this, because I do not know the origin of this statement and may have to quibble a bit with the stated reasoning.<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'>ARIN’s number resource policy applies to all resources under our administration – and in general doesn’t reference “legacy status” (i.e. the only section of ARIN’s policy manual which references legacy number resources is NRPM Section 12 / Resource Review, and that's solely to make plain that Resource Review doesn’t create any authority with respect to legacy number resources that ARIN doesn’t already have.) <o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'>ARIN defines legacy number resources with some precision: "number resources issued to the resource holder or its predecessor in interest prior to ARIN’s inception on December 22, 1997’. This is done in the ARIN Registration Services Agreement (RSA) because, per direction of the ARIN Board of Trustees, ARIN has provided reduced fees for legacy resource holders and slightly different exit provision on termination for cause. <o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'>Number resources are considered “legacy number resources” in the ARIN region is if they are held by original registrant (or its legal successor), and so it is highly unlikely that any resources transferred in from another region would be treated as legacy number resources (i.e. unless being brought into the region via merger/acquisition activity.) Similarly, it probably wouldn’t make sense for resources transferred to another party outside the region to be treated as “legacy number resources” (again, aside from M&A activity), but I should note that we leave it to other RIRs to define their terms and conditions of their registration services as they see fit. <o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'>I understand that some regions may treat “legacy status” as an innate property of the number resource block, but that certainly is not the case in the ARIN region - again, the only way number resources can be consider "legacy number resources” is while held by the original registrant or their legal successor, so the idea of “legacy status” for the number block itself independent of the resource holder is meaningless in the ARIN region. <o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'>ARIN wouldn’t find a policy proposal that required (or prohibited) “legacy status” treatment for transferred resources to be compatible, but not due to policy conflict but rather because it would could create a conflict with the very specific definition of “legacy number resources” in our registration services agreement. <o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'>Thanks,<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'>/John<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p></div><div><div><p class=MsoNormal style='margin-left:35.4pt'>John Curran<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'>President and CEO<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'>American Registry for Internet Numbers<o:p></o:p></p></div></div><div><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p></div></div><br>**********************************************<br>
IPv4 is over<br>
Are you ready for the new Internet ?<br>
http://www.theipv6company.com<br>
The IPv6 Company<br>
<br>
This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.<br>
<br>
</body></html>