<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:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML con formato previo Car";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
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.HTMLconformatoprevioCar
{mso-style-name:"HTML con formato previo Car";
mso-style-priority:99;
mso-style-link:"HTML con formato previo";
font-family:Consolas;}
p.HTMLPreformatted, li.HTMLPreformatted, div.HTMLPreformatted
{mso-style-name:"HTML Preformatted";
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EstiloCorreo22
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;
font-weight:normal;
font-style:normal;}
span.EstiloCorreo23
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;
font-weight:normal;
font-style:normal;}
span.EstiloCorreo25
{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><div class=WordSection1><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'>Hi Mike,<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'>Exactly, that’s the point.<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'>Thanks for your support!<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'>The reality is that *<b>even</b>* if we don’t have that text in the policy, the staff can always call the board which in turn, can always “stop any policy”, because they have a responsibility to protect the membership/organization (and consequently the managed resources).<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 happened recently in ARIN, right?<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'>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 27/11/19 17:00, "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'>While I do not see it as healthy to have staff-bypass language present in policy, I understand you included the language at community request. In that case, I will support the policy as written in the hope this language will never need to be utilized.<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 can’t think of a similar circumstance having occurred in my experience anyway, at any other RIR.<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><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> Mike Burns <mike@iptrading.com> <br><b>Sent:</b> Tuesday, November 26, 2019 2:11 PM<br><b>To:</b> 'Fernando Frediani' <fhfrediani@gmail.com>; 'rpd@afrinic.net' <rpd@afrinic.net><br><b>Subject:</b> RE: [rpd] New version of AFPUB-2019-IPv4-002-DRAFT03 "IPv4 Inter-RIR Resource Transfers (Comprehensive Scope)"<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'>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'>Thanks for the diffchecker layout.<o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'>I agree with Fernando that this should not be a board issue.<o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'>Particularly in a fraught environment of board/staff responsibility, I think that you should remove the language about the escalation to the board, and adopt Fernando’s ideas about a structured, staff-based appeal process. I don’t think the details of that process belong in the policy necessarily, but we should direct the staff to organize and administer that appeal process.<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 would support this policy with that change to remove the specified escalation to the board language.<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><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> Fernando Frediani <<a href="mailto:fhfrediani@gmail.com">fhfrediani@gmail.com</a>> <br><b>Sent:</b> Tuesday, November 26, 2019 1:34 PM<br><b>To:</b> <a href="mailto:rpd@afrinic.net">rpd@afrinic.net</a><br><b>Subject:</b> Re: [rpd] New version of AFPUB-2019-IPv4-002-DRAFT03 "IPv4 Inter-RIR Resource Transfers (Comprehensive Scope)"<o:p></o:p></p></div></div><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p><p style='margin-left:35.4pt'>Hello Jordi<o:p></o:p></p><p style='margin-left:35.4pt'>The text seems fine despite the change of wording on some parts, at the end they means about the same thing. I have 2 points to note:<o:p></o:p></p><p style='margin-left:35.4pt'>- on 5.7.6 it says "information permitted by the source or recipient". Although there is minimum mandatory information that must be published, I understand the wording allow the RIR to publish extra information or notes about the transaction ? How likely is that to happen and what examples of information would be that ? Could you clarify a bit further.<o:p></o:p></p><p style='margin-left:35.4pt'>- On 5.7.7.2 there is a possibility, should the staff finds a transaction suspicious, to escalate it for the Board for a final decision. I normally think this type of individual thing should not end up in the Board, but internally inside the staff in a well defined appeal process because they are staff decisions (e.g: appeal to the Manager, Director, CEO, etc). The Board should only be involved in something that affects several members or a number of organizations (for example to preemptively suspend a policy that may be damaging the RIR or the Community, etc). The same way the Board can always issue statements for staff on certain topics and procedures but always in a more generic way.<o:p></o:p></p><p style='margin-left:35.4pt'>Best regards<br>Fernando Frediani<o:p></o:p></p><div><p class=MsoNormal style='margin-left:35.4pt'>On 26/11/2019 14:58, JORDI PALET MARTINEZ via RPD wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre style='margin-left:35.4pt'>Hi all,<o:p></o:p></pre><pre style='margin-left:35.4pt'> <o:p></o:p></pre><pre style='margin-left:35.4pt'>Find attached a new version of the proposal "IPv4 Inter-RIR Resource Transfers (Comprehensive Scope)".<o:p></o:p></pre><pre style='margin-left:35.4pt'> <o:p></o:p></pre><pre style='margin-left:35.4pt'>As usual, I've considered the inputs received.<o:p></o:p></pre><pre style='margin-left:35.4pt'> <o:p></o:p></pre><pre style='margin-left:35.4pt'>I've also prepared a diff with the previous version:<o:p></o:p></pre><pre style='margin-left:35.4pt'> <o:p></o:p></pre><pre style='margin-left:35.4pt'><a href="https://www.diffchecker.com/azpn4DK0">https://www.diffchecker.com/azpn4DK0</a><o:p></o:p></pre><pre style='margin-left:35.4pt'> <o:p></o:p></pre><pre style='margin-left:35.4pt'>Thanks!<o:p></o:p></pre><pre style='margin-left:35.4pt'> <o:p></o:p></pre><pre style='margin-left:35.4pt'>Regards,<o:p></o:p></pre><pre style='margin-left:35.4pt'>Jordi<o:p></o:p></pre><pre style='margin-left:35.4pt'> <o:p></o:p></pre><pre style='margin-left:35.4pt'> <o:p></o:p></pre><pre style='margin-left:35.4pt'> <o:p></o:p></pre><pre style='margin-left:35.4pt'> <o:p></o:p></pre><pre style='margin-left:35.4pt'>**********************************************<o:p></o:p></pre><pre style='margin-left:35.4pt'>IPv4 is over<o:p></o:p></pre><pre style='margin-left:35.4pt'>Are you ready for the new Internet ?<o:p></o:p></pre><pre style='margin-left:35.4pt'><a href="http://www.theipv6company.com">http://www.theipv6company.com</a><o:p></o:p></pre><pre style='margin-left:35.4pt'>The IPv6 Company<o:p></o:p></pre><pre style='margin-left:35.4pt'> <o:p></o:p></pre><pre style='margin-left:35.4pt'>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.<o:p></o:p></pre><pre style='margin-left:35.4pt'> <o:p></o:p></pre><p class=MsoNormal style='mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:35.4pt'> <o:p></o:p></p><pre style='margin-left:35.4pt'>_______________________________________________<o:p></o:p></pre><pre style='margin-left:35.4pt'>RPD mailing list<o:p></o:p></pre><pre style='margin-left:35.4pt'><a href="mailto:RPD@afrinic.net">RPD@afrinic.net</a><o:p></o:p></pre><pre style='margin-left:35.4pt'><a href="https://lists.afrinic.net/mailman/listinfo/rpd">https://lists.afrinic.net/mailman/listinfo/rpd</a><o:p></o:p></pre></blockquote><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>