<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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.estilocorreo19
{mso-style-name:estilocorreo19;}
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:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:711538985;
mso-list-template-ids:1383221898;}
@list l0:level1
{mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level2
{mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level3
{mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level4
{mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level5
{mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level6
{mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level7
{mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level8
{mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level9
{mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l1
{mso-list-id:861476525;
mso-list-type:hybrid;
mso-list-template-ids:-171931666 1964773494 67764227 67764229 67764225 67764227 67764229 67764225 67764227 67764229;}
@list l1:level1
{mso-level-start-at:5;
mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;
mso-fareast-font-family:Calibri;
mso-bidi-font-family:"Times New Roman \(Cuerpo en alfa";}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l2
{mso-list-id:1581912261;
mso-list-type:hybrid;
mso-list-template-ids:-304070384 1542251676 67764227 67764229 67764225 67764227 67764229 67764225 67764227 67764229;}
@list l2:level1
{mso-level-start-at:2;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-font-family:"Times New Roman";}
@list l2:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l2:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l2:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l2:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l2:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l2:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l2:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l2:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
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><div><p class=MsoNormal style='margin-bottom:12.0pt'><span lang=ES-TRAD style='font-size:12.0pt;mso-fareast-language:EN-US'>Hi Owen,<o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:12.0pt'><span lang=ES-TRAD style='font-size:12.0pt;mso-fareast-language:EN-US'>So, 5.7:<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'>The resources to be transferred must be from an existing Resource Holder (including Legacy Resource Holders) in the AFRINIC service region/other RIRs.<o:p></o:p></span></p><ul type=disc><li class=MsoListParagraph style='color:black;mso-list:l2 level1 lfo2'><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'>Note that the explicit mention to legacy resource holders is to avoid questioning about that in the impact analysis, or objections during the discussion because it is not sufficiently clear. Anyway, if the staff believes that this mention is not needed, I’m happy to remove it.<o:p></o:p></span></li></ul></div><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'>5.7.1. I agree that it shouldn’t be an internal procedure but a policy. I proposed a policy about that, same as I did in other regions. In the case of AFRINIC it was not supported 2-3 years ago. I think is something to tackle once we have sorted out the transfers. Trying to do it at once, will create more obstacles for a possible consensus.<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. I’m fine with your proposal:<o:p></o:p></span></p><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US>“All the transfers where the source is an AFRINIC resource member will be required to pass a pre-check in order to verify that the resources being transferred were allocated/assigned and used in accordance with the requirements in section 5.7.2.1”.<o:p></o:p></span></p><ul type=disc><li class=MsoListParagraph style='mso-list:l1 level1 lfo3'><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'>However, note that this doesn’t precludes AFRINIC doing other checks never mind you consider them as part of the pre-check or not. They can, as it is their obligation, review if the resources holders are following the RSA and CPM *<b>at any time</b>*. My wish to include “RSA” in that sentence is to make sure that anyone reading the policy is transparently aware of that. Note also that what you see as possible RSA violation is precisely what I’m avoiding with the possible transfer failure in the next paragraph:<o:p></o:p></span></li></ul><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'>“It can happen that a transfer fails due to the recipient failing to be compliant because the lack of proper documentation or non-compliance of the relevant rules, while the source passed the transfer pre-check. This proposal allows the successful transfer pre-check to be valid for up to 12 months after the failed transfer; i.e AFRINIC will not initiate a recovery/reclamation process in this period.”<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'>So, it is clear that the </span><span lang=EN-US>act of making the resources available for transfer can NOT be construed as a violation of the usage requirements.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>Of course, if you declare “I don’t need any more those resources, so I’m transferring them”, the transfer fails because the recipient can’t demonstrate the need, then you either actively search for another valid recipient or your network grows so you don’t need any more to transfer the resources and you are NOT violating the RSA/CPM.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>Is that clear or there is something broken in my rationale that I’m missing?</span><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'><o:p> </o:p></span></p><div><div><p class=MsoNormal style='margin-left:35.4pt'>El 10/10/21 0:26, "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 9, 2021, at 02:10 , 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 lang=EN-US style='font-size:12.0pt'>Hi Owen,</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><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US style='font-size:12.0pt'>Below in-line.</span><o:p></o:p></p></div><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><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 22:51, "Owen DeLong" <<a href="mailto:owen@delong.com">owen@delong.com</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'> <o:p></o:p></p></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 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></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'><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><div><div style='margin-left:35.4pt'><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><div><div style='margin-left:35.4pt'><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><div><div style='margin-left:35.4pt'><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'><span lang=EN-US style='font-size:12.0pt'>This is the new text:</span><o:p></o:p></p></div></div><div><div style='margin-left:35.4pt'><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></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'>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><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 current wording precludes those resource holders from participating in said 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><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'><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></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'>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><div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'><span style='font-size:12.0pt'> </span><o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'><span 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'>[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:</span><o:p></o:p></p></div><p class=MsoListParagraph style='mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:0cm;margin-left:71.4pt;text-indent:-18.0pt;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='mso-list:Ignore'>1.<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]><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?</span><o:p></o:p></p><p class=MsoListParagraph style='mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:0cm;margin-left:71.4pt;text-indent:-18.0pt;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='mso-list:Ignore'>2.<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]><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?</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'>Why not just refer to “resource holders” instead of “members”<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><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'><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></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'>OK… Ugly, but ok.<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-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'>[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?</span><o:p></o:p></p></div></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 many defects in the CPM. I consider them ugly.<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 was referring to the situation, not the text.<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><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US style='font-size:12.0pt'> </span><span lang=EN-US><br><br><br></span><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'><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></div></blockquote><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><div><div style='margin-left:35.4pt'><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'><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></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'>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><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 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><div><div style='margin-left:35.4pt'><p class=MsoNormal style='margin-left:35.4pt'><span style='font-size:12.0pt'> </span><br><br><br><o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><div><div style='margin-left:35.4pt'><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></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'>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><div><div><p class=MsoNormal style='margin-left:35.4pt'><span 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'>[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:</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'>Actual:</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'>“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.”</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'>Proposed:</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'>“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.”</span><o:p></o:p></p></div></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'>If we could make that slightly stronger, then yes…<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'>Altenrate proposal:<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'>“All the transfers where the source is an AFRINIC resource member will be required to pass a pre-check in order to verify that the resources being transferred were allocated/assigned and used in accordance with the requirements in section 5.7.2.1”.<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'>Otherwise, the mere act of making the resources available for transfer can be construed as a violation of the usage requirements as currently written in the RSA. I think 5.7.2.1 is perfectly fine and adequately comprehensive if the pre-check scope is limited accordingly.<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'><o:p> </o:p></p></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>