<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-tab-span
{mso-style-name:apple-tab-span;}
span.EstiloCorreo19
{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:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=ES link=blue vlink=purple style='word-wrap:break-word;-webkit-nbsp-mode: space;line-break:after-white-space'><div class=WordSection1><p class=MsoNormal><span class=EstiloCorreo19><span style='font-size:12.0pt'></span></span><span class=EstiloCorreo19><span lang=EN-US style='font-size:12.0pt'>Hi Owen,<o:p></o:p></span></span></p><p class=MsoNormal><span class=EstiloCorreo19><span lang=EN-US style='font-size:12.0pt'><o:p> </o:p></span></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'>The modification of 5.7 was done to add clarity to the text. I don’t understand where you see the problem, if there was no problem about reciprocity in the previous versions.<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><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'>This is the new text:<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;color:#C45911'>The resources to be transferred must be from an existing RIR member’s account or from a Legacy Resource Holder in the AFRINIC service region/other RIRs.</span><span lang=EN-US style='font-size:10.0pt;font-family:"Times New Roman",serif;color:#C45911'><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><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'>It clearly says AFRINIC/other RIRs, so what I’m missing?<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><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'>Regarding 5.7.1, the M&A today is not a policy, but an internal procedure (as it happens in RIPE, for example). I don’t agree this should be an internal procedure, but that’s what we have today. My plan is to, once we have fixed this, make a proposal for that, but I think it is better to go step by step, so adding a reference will be breaking it in the future (or requiring one more change in this part of the text). It is not needed. If you look at the existing text for intra-RIR that it is in the policy manual today, there is no such reference.<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><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'>5.7.5 is to make explicit something that was already there. When you attempt an intra-RIR transfer, *<b>all</b>* the parties are verified. This is the same in other RIRs. However, I’m also adding a “protection” to the failed transfers, because today, if AFRINIC strictly follows the intra-RIR transfer and it fails because, for example, the destination doesn’t meet the policies, then the source will lose the resources, as he clearly demonstrated that doesn't need them and that’s the reason, he is willing to transfer.<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'>What your text for 5.7.5 is proposing seems to be a restriction of some of the RSA and CPM text. I don’t think that’s right, otherwise, each proposal or part of the CPM can actually “change” what is already written in the RSA and/or CPM and create a mess.<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><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'>I’m happy to accept suggestions from anyone, as usual, but they should be reasonable and consistent.<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><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'>If we want to change the CPM in other sections, let’s do it, but not make each part of the CPM modifying others or modifying the RSA.<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><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'>If we want to change the RSA, I guess this can be done, but probably via membership. The RPD is fine to suggest that, but not by means of a policy proposal, right?<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 8/10/21 21:44, "Owen DeLong via RPD" <<a href="mailto:rpd@afrinic.net">rpd@afrinic.net</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'>I oppose this version of the policy proposal.<o:p></o:p></p><div><p class=MsoNormal style='margin-left:35.4pt'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'>Section 5.7 needs to be amended to allow the source of the transferred resources<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'>to be a resource holder from any RIR, not just AFRINIC.<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'>This may seem like a minor NIT, but as written, the policy would be outbound only<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'>and not symmetrical (thus not reciprocal), so fixing this is important. Admittedly,<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'>the text in 5.7 is inconsistent with the subsequent text in this regard, but<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'>it is possible to interpret the limitations expressed in the proposed 5.7 as<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'>overriding the expressed possibilities in the subsequent proposed sections.<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 suspect that the 5.7 text is an accident on the part of the author and that<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'>this limitation was not intended.<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'>5.7.1 should point to the policy that does cover M&A transfers rather than simply<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'><span class=apple-tab-span> </span>state that this policy does not apply to them.<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 oppose section 5.7.5 because AFRINIC has already demonstrated a propensity<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'>to make arbitrary and capricious decisions about compliance based not on the<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'>actual text of the contracts, bylaws, or CPM, but on their own creative<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'>interpretations thereof.<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'>The pre-check authorized by section 5.7.5 should be limited to deterministic<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'>factors which can achieve a binary outcome strictly on provable facts and not<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'>be subject to staff interpretation and judgment, as staff has already<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'>proven on numerous occasions that it cannot be trusted to exercise good judgment<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'>or achieve prudent or accurate determinations in such matters.<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'>Proposed modified text:<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'>5.7 IPv4 Transfers<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'>This policy applies to organizations with a justified need for IPv4 resources (recipients) and organizations with IPv4 resources which no longer need (sources).<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'><br>The resources to be transferred must be from an existing resource holder of a direct allocation or assignment from an IANA[1] accredited RIR or a legacy resource holder registered and recognized as the current registrant of the addresses to be transferred by the applicable IANA[1] accredited RIR.<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'>5.7.1 — Mostly fine, just add the needed cross-reference to the M&A policy section.<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'>5.7.5 Transfer pre-check<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'>Where the source of a transfer is a resource member of AFRINIC, AFRINIC will perform a pre-check prior to authorizing the transfer which shall include validation of the following items:<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'><span class=apple-tab-span> </span>+<span class=apple-tab-span> </span>Resource member is a member in good standing<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'><span class=apple-tab-span> </span>+<span class=apple-tab-span> </span>Resource member is the current registrant of record for the resources being transferred<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'><span class=apple-tab-span> </span>+<span class=apple-tab-span> </span>Resource member’s registration of the resources is not credibly disputed by any third party<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'><span class=apple-tab-span> </span>+<span class=apple-tab-span> </span>Resource member’s fees are current with AFRINIC<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'>[1] At the time of writing, this IANA function is performed by ICANN in accordance with ICP-2.<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'>Author is, of course welcome to accept, decline, or modify these proposed edits as they see fit, but these edits, as<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'>written, would allow me to support the proposal as written.<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'>Owen<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'><br><br><o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal style='margin-left:35.4pt'>On Oct 4, 2021, at 10:33 AM, PDWG Chair <<a href="mailto:dacostadarwin@gmail.com">dacostadarwin@gmail.com</a>> wrote:<o:p></o:p></p></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'><span style='font-family:"Arial",sans-serif;color:black;background:white'>Hello PDWG Members,</span><span style='font-family:"Arial",sans-serif'><o:p></o:p></span></p></div><p class=MsoNormal style='margin-left:35.4pt'><span style='font-family:"Arial",sans-serif'><o:p> </o:p></span></p><div><p class=MsoNormal style='margin-left:35.4pt'><span style='font-family:"Arial",sans-serif;color:black;background:white'>We have received a new version of policy Proposal - IPv4 Inter-RIR Resource Transfers (Comprehensive Scope) - AFPUB-2019-IPv4-002-DRAFT06 from author Jordi Palet Martinez. </span><span style='font-family:"Arial",sans-serif'><o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:35.4pt'><span style='font-family:"Arial",sans-serif;color:black;background:white'><br><br></span><span style='font-family:"Arial",sans-serif'><o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:35.4pt'><span style='font-family:"Arial",sans-serif;color:black;background:white'>The proposal contents are published at: </span><span style='font-family:"Arial",sans-serif'><o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:35.4pt'><span style='font-family:"Arial",sans-serif;color:black;background:white'><a href="https://afrinic.net/policy/proposals/2019-ipv4-002-d6">https://afrinic.net/policy/proposals/2019-ipv4-002-d6</a></span><span style='font-family:"Arial",sans-serif'><o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:35.4pt'><span style='font-family:"Arial",sans-serif'><o:p> </o:p></span></p></div><div><p class=MsoNormal style='margin-left:35.4pt'><span style='font-family:"Arial",sans-serif;color:black;background:white'>Please take some time to go through the proposal contents and provide your</span><span style='font-family:"Arial",sans-serif'><o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:35.4pt'><span style='font-family:"Arial",sans-serif;color:black;background:white'>feedback.</span><span style='font-family:"Arial",sans-serif'><o:p></o:p></span></p></div><p class=MsoNormal style='margin-left:35.4pt'><span style='font-family:"Arial",sans-serif'><o:p> </o:p></span></p><div><p class=MsoNormal style='margin-left:35.4pt'><span style='font-family:"Arial",sans-serif;color:black;background:white'>Regards,</span><span style='font-family:"Arial",sans-serif'><o:p></o:p></span></p></div><p class=MsoNormal style='margin-left:35.4pt'><span style='font-family:"Arial",sans-serif'><o:p> </o:p></span></p><div><p class=MsoNormal style='margin-left:35.4pt'><span style='font-family:"Arial",sans-serif;color:black;background:white'>PDWG Co-Chair.</span><span style='font-family:"Arial",sans-serif'><o:p></o:p></span></p></div><p class=MsoNormal style='margin-left:35.4pt'><o:p> </o:p></p></div><p class=MsoNormal style='margin-left:35.4pt'>_______________________________________________<br>RPD mailing list<br><a href="mailto:RPD@afrinic.net">RPD@afrinic.net</a><br>https://lists.afrinic.net/mailman/listinfo/rpd<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'>_______________________________________________ RPD mailing list RPD@afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd <o:p></o:p></p></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>