<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;}
@font-face
{font-family:Monaco;
panose-1:2 0 5 0 0 0 0 0 0 0;}
/* 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;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.estilocorreo19
{mso-style-name:estilocorreo19;}
span.apple-tab-span
{mso-style-name:apple-tab-span;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EstiloCorreo21
{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;}
/* List Definitions */
@list l0
{mso-list-id:1838110188;
mso-list-type:hybrid;
mso-list-template-ids:1142865822 67764241 67764249 67764251 67764239 67764249 67764251 67764239 67764249 67764251;}
@list l0:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></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 lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'>Hi Owen,<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'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'>Below in-line.<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 8/10/21 22:51, "Owen DeLong" <<a href="mailto:owen@delong.com">owen@delong.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'><o:p> </o:p></p><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 8, 2021, at 1:07 PM, JORDI PALET MARTINEZ via RPD <<a href="mailto:rpd@afrinic.net">rpd@afrinic.net</a>> wrote:<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'><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,</span></span><o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'><span class=estilocorreo19><span lang=EN-US style='font-size:12.0pt'> </span></span><o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US style='font-size:12.0pt'>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.</span><o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US style='font-size:12.0pt'> </span><o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US style='font-size:12.0pt'>This is the new text:</span><o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'><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><o:p></o:p></p></div></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'>There are lots of resource holders in other RIRs (at least in ARIN) who are not RIR members.<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 current wording precludes those resource holders from participating in said transfers.<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'><o:p> </o:p></p></div><div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US style='font-size:12.0pt'>It clearly says AFRINIC/other RIRs, so what I’m missing?</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'>That not all RIRs require membership to have resources. IIRC, this is the case with sponsored PI in RIPE as well.<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'><span style='font-size:12.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt'>[Jordi] I should have noticed that, as I was the author of the IPv6 PI in RIPE, which resulted in the “sponsored PI”. So, we have two choices here:<o:p></o:p></span></p><ol style='margin-top:0cm' start=1 type=1><li class=MsoListParagraph style='margin-left:0cm;mso-list:l0 level1 lfo1'><span lang=EN-US style='font-size:12.0pt'>Maybe this text is redundant. I don’t see an equivalent text in other RIRs, and trying to clarify was worse than not having it. Can the staff confirm if they really need this text or it has no impact to remove it, as it was in the previous versions? I don’t recall previous analysis impact requiring a clarification on that. In fact, these conditions are already somehow expressed with the text in 5.7.1.b) and 5.7.2.1. May be the only “excluded case” is if a legacy holder has no registration of the resources in none of the RIRs – is that happening or actually possible?<o:p></o:p></span></li><li class=MsoListParagraph style='margin-left:0cm;mso-list:l0 level1 lfo1'><span lang=EN-US style='font-size:12.0pt'>Use the text that you proposed. In principle I’m fine with that. I will like to see inputs from others, and specially from the staff. We need to make sure that they don’t have any misunderstanding/issue with that. I know they will check with the analysis impact, but it should be possible to have a preliminary view on that?<o:p></o:p></span></li></ol><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US style='font-size:12.0pt'> </span><span lang=EN-US><o:p></o:p></span></p></div><div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US style='font-size:12.0pt'>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.</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'>OK… Ugly, but ok.<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'><span style='font-size:12.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt'>[Jordi] I don’t think it is ugly, there are other similar situations in the CPM. We could also just remove that text, as it was in previous versions. I think it is fine keeping it, may be as a foot note and not “policy text” (such as “note Mergers and Acquisitions (inter or intra) are not covered by this policy”. The idea was to ensure that the analysis impact doesn’t “complain” about that. Will be that fine for the staff?<o:p></o:p></span></p><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US style='font-size:12.0pt'> </span><span lang=EN-US><br><br><o:p></o:p></span></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US style='font-size:12.0pt'>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.</span><o:p></o:p></p></div></blockquote><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><div><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US style='font-size:12.0pt'> </span><o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US style='font-size:12.0pt'>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.</span><o:p></o:p></p></div></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'>I am proposing not allowing staff to block a transfer because they decide they don’t like a registrant.<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 am not proposing limitations on other sections of the CPM, but limitations on the excuses staff can use to block a transfer to the criteria that can be measured objectively and without subjecting transfer participants (receive or supply) to arbitrary and capricious misinterpretations of the CPM by a staff which has shown a clear propensity to engage in same.<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'><span style='font-size:12.0pt'> </span><br><br><o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><div><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US style='font-size:12.0pt'>I’m happy to accept suggestions from anyone, as usual, but they should be reasonable and consistent.</span><o:p></o:p></p></div></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'>I believe that my suggestions were both reasonable and consistent, with the exception of the 5.7.1 as noted.<o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:12.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt'>[Jordi] I feel that you’re being too much suspicious about the staff and I understand the situation. However, we should not over-micro-manage. In my opinion the pre-check must be done based on the RSA mainly. If there is a problem with the RSA, let’s fix it there. Have you noticed that what you’re asking is already in 5.7.2? Do you think anything is missed there? Would you be ok if we just do something like:<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt'>Actual:<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt'>“All the transfers where the source is an AFRINIC resource member, will be required to pass a pre-check in order verify that the resources being transferred were allocated/assigned and used following the RSA/CPM provisions.”<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt'>Proposed:<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt'>“All the transfers where the source is an AFRINIC resource member, will be required to pass a pre-check in order verify that the resources being transferred were allocated/assigned and used following the RSA provisions and 5.7.2.1.”<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt'><o:p> </o:p></span></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><div><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US style='font-size:12.0pt'>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.</span><span lang=EN-US><o:p></o:p></span></p></div></div></blockquote><div><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US><o:p> </o:p></span></p></div><p class=MsoNormal style='margin-left:35.4pt'>I am not attempting to change the other CPM sections. I am attempting to limit staff authority to block transfers.<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'><span style='font-size:12.0pt'> </span><br><br><o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><div><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US style='font-size:12.0pt'>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?</span><o:p></o:p></p></div></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'>I am not attempting to change the RSA. I am attempting to limit the staff authority to block transfers. My intent is for these<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'>limits to apply strictly to transactions occurring under this proposed 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'>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><div><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US style='font-size:12.0pt'> </span><o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US style='font-size:12.0pt'>Regards,</span><o:p></o:p></p></div><p class=MsoNormal style='mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:35.4pt'><span lang=EN-US style='font-size:12.0pt'>Jordi</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:35.4pt'><span lang=EN-US style='font-size:12.0pt'>@jordipalet</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:35.4pt'><span lang=EN-US style='font-size:12.0pt'> </span><o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US style='font-size:12.0pt'> </span><o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US style='font-size:12.0pt'> </span><o:p></o:p></p></div><div><div><div style='margin-left:35.4pt'><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><div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p></div></div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'>I oppose this version of the policy proposal.<o:p></o:p></p></div><div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p></div></div><div><div style='margin-left:35.4pt'><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><div><div style='margin-left:35.4pt'><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><div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p></div></div><div><div style='margin-left:35.4pt'><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><div><div style='margin-left:35.4pt'><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><div><div style='margin-left:35.4pt'><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><div><div style='margin-left:35.4pt'><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><div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'>overriding the expressed possibilities in the subsequent proposed sections.<o:p></o:p></p></div></div><div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p></div></div><div><div style='margin-left:35.4pt'><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><div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'>this limitation was not intended.<o:p></o:p></p></div></div><div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p></div></div><div><div style='margin-left:35.4pt'><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><div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'><span class=apple-tab-span> </span><span class=apple-converted-space> </span>state that this policy does not apply to them.<o:p></o:p></p></div></div><div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p></div></div><div><div style='margin-left:35.4pt'><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><div><div style='margin-left:35.4pt'><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><div><div style='margin-left:35.4pt'><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><div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'>interpretations thereof.<o:p></o:p></p></div></div><div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p></div></div><div><div style='margin-left:35.4pt'><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><div><div style='margin-left:35.4pt'><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><div><div style='margin-left:35.4pt'><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><div><div style='margin-left:35.4pt'><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><div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'>or achieve prudent or accurate determinations in such matters.<o:p></o:p></p></div></div><div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p></div></div><div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p></div></div><div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'>Proposed modified text:<o:p></o:p></p></div></div><div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p></div></div><div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'>5.7 IPv4 Transfers<o:p></o:p></p></div></div><div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p></div></div><div><div style='margin-left:35.4pt'><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><div><div style='margin-left:35.4pt'><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><div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p></div></div><div><div style='margin-left:35.4pt'><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><div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p></div></div><div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'>5.7.5 Transfer pre-check<o:p></o:p></p></div></div><div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p></div></div><div><div style='margin-left:35.4pt'><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><div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'><span class=apple-tab-span> </span><span class=apple-converted-space> </span>+<span class=apple-tab-span> </span><span class=apple-converted-space> </span>Resource member is a member in good standing<o:p></o:p></p></div></div><div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'><span class=apple-tab-span> </span><span class=apple-converted-space> </span>+<span class=apple-tab-span> </span><span class=apple-converted-space> </span>Resource member is the current registrant of record for the resources being transferred<o:p></o:p></p></div></div><div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'><span class=apple-tab-span> </span><span class=apple-converted-space> </span>+<span class=apple-tab-span> </span><span class=apple-converted-space> </span>Resource member’s registration of the resources is not credibly disputed by any third party<o:p></o:p></p></div></div><div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'><span class=apple-tab-span> </span><span class=apple-converted-space> </span>+<span class=apple-tab-span> </span><span class=apple-converted-space> </span>Resource member’s fees are current with AFRINIC<o:p></o:p></p></div></div><div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p></div></div><div><div style='margin-left:35.4pt'><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><div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p></div></div><div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p></div></div><div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p></div></div><div><div style='margin-left:35.4pt'><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><div><div style='margin-left:35.4pt'><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><div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p></div></div><div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'>Owen<o:p></o:p></p></div></div><div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'><br><br><br><o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><div style='margin-left:35.4pt'><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></div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p></div><div><div><div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'><span style='font-family:"Arial",sans-serif;color:black;background:white'>Hello PDWG Members,</span><o:p></o:p></p></div></div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'><span style='font-family:"Arial",sans-serif'> </span><o:p></o:p></p></div><div><div style='margin-left:35.4pt'><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><o:p></o:p></p></div></div><div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'><span style='font-family:"Arial",sans-serif;color:black;background:white'><br><br><br></span><o:p></o:p></p></div></div><div><div style='margin-left:35.4pt'><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><o:p></o:p></p></div></div><div><div style='margin-left:35.4pt'><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><o:p></o:p></p></div></div><div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'><span style='font-family:"Arial",sans-serif'> </span><o:p></o:p></p></div></div><div><div style='margin-left:35.4pt'><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><o:p></o:p></p></div></div><div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'><span style='font-family:"Arial",sans-serif;color:black;background:white'>feedback.</span><o:p></o:p></p></div></div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'><span style='font-family:"Arial",sans-serif'> </span><o:p></o:p></p></div><div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'><span style='font-family:"Arial",sans-serif;color:black;background:white'>Regards,</span><o:p></o:p></p></div></div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'><span style='font-family:"Arial",sans-serif'> </span><o:p></o:p></p></div><div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'><span style='font-family:"Arial",sans-serif;color:black;background:white'>PDWG Co-Chair.</span><o:p></o:p></p></div></div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p></div></div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'>_______________________________________________<br>RPD mailing list<br><a href="mailto:RPD@afrinic.net">RPD@afrinic.net</a><br><a href="https://lists.afrinic.net/mailman/listinfo/rpd">https://lists.afrinic.net/mailman/listinfo/rpd</a><o:p></o:p></p></div></div></blockquote></div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p></div></div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'>_______________________________________________ RPD mailing list<span class=apple-converted-space> </span><a href="mailto:RPD@afrinic.net">RPD@afrinic.net</a><span class=apple-converted-space> </span><a href="https://lists.afrinic.net/mailman/listinfo/rpd">https://lists.afrinic.net/mailman/listinfo/rpd</a><o:p></o:p></p></div><p class=MsoNormal style='margin-left:35.4pt'><span style='font-size:9.0pt;font-family:Monaco'><br>**********************************************<br>IPv4 is over<br>Are you ready for the new Internet ?<br></span><a href="http://www.theipv6company.com/"><span style='font-size:9.0pt;font-family:Monaco'>http://www.theipv6company.com</span></a><span style='font-size:9.0pt;font-family:Monaco'><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>_______________________________________________<br>RPD mailing list<br></span><a href="mailto:RPD@afrinic.net"><span style='font-size:9.0pt;font-family:Monaco'>RPD@afrinic.net</span></a><span style='font-size:9.0pt;font-family:Monaco'><br></span><a href="https://lists.afrinic.net/mailman/listinfo/rpd"><span style='font-size:9.0pt;font-family:Monaco'>https://lists.afrinic.net/mailman/listinfo/rpd</span></a><o:p></o:p></p></blockquote></div><p class=MsoNormal style='margin-left:35.4pt'><br><br><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>