<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:Helvetica;
panose-1:0 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;
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;}
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.EstiloCorreo18
{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><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'>As I see no opposition to your points and I also agree with them, I’m editing a new version that I shall publish in a while.<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!<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><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 13/11/19 2:07, "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 Nov 12, 2019, at 02:04 , 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><p class=MsoNormal style='margin-left:35.4pt'><span style='font-size:9.0pt;font-family:Helvetica'>Hi Owen,<br><br>In the previous meeting, that sentence with the private ASNs was already there, nobody objected to it, including yourself. That's why I didn't modified that part.</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'>I apologize for not previously noticing it.<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'><span style='font-size:9.0pt;font-family:Helvetica'>I think it provides clarity, however, if is a problem for anyone, I'm happy to remove that. A middle way alterative is a footnote:</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'>A footnote still duplicates data unnecessarily and creates a need to update the CPM any time the IETF chooses to adjust the private ASN range(s). We should avoid duplicating IETF information in policy to avoid the risk of it falling out of sync.<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 style='font-size:9.0pt;font-family:Helvetica'>It is important to determine which sites require unique AS Numbers. Sites which do not require a unique AS Number should use one or more of the AS Numbers reserved for private use*.<br><br>*Those numbers are: 64,512 - 65,535 and 4,200,000,000 - 4,294,967,294 (RFC1930, RFC6996 and possible future updates) - date of publication.<br><br>Will you agree on that?<br><br>Regarding your point on 7.2.2, your wording "technical need", an ISP that has a single upstream and that single upstream is mandating to provide BGP a public ASN, I think will not fall into "technical need”.</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'>It certainly falls into “Unique Routing Policy”, but I would say that it also meets the definition of “technical need”, since the affected organization cannot technically route their addresses via said provider without a public ASN.<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'><span style='font-size:9.0pt;font-family:Helvetica'><br>Regards,<br>Jordi<br>@jordipalet<br><br><br><br></span><span style='font-size:9.0pt'></span><span style='font-size:9.0pt;font-family:Helvetica'>El 12/11/19 2:57, "Owen DeLong" <</span><a href="mailto:owen@delong.com"><span style='font-size:9.0pt;font-family:Helvetica'>owen@delong.com</span></a><span style='font-size:9.0pt;font-family:Helvetica'>> escribió:<br><br> Oppose as written.<br><br> Adding the specific AS numbers for private use to 7.2 is an unnecessary duplication of data that has no mechanism for preserving synchronization with reality.<br><br> Take that out and I would support the policy as written, tough I would prefer to replace 7.2.2 with:<br><br> 7.2.2 Show a unique routing policy or demonstrate a technical need for a coordinated globally unique ASN.<br><br> Owen<br><br><br style='caret-color: rgb(0, 0, 0);font-variant-caps: normal;text-align:start;-webkit-text-stroke-width: 0px;word-spacing:0px'><br></span><o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal style='margin-left:35.4pt'><span style='font-size:9.0pt;font-family:Helvetica'>On Nov 11, 2019, at 01:50 , JORDI PALET MARTINEZ via RPD <<a href="mailto:rpd@afrinic.net">rpd@afrinic.net</a>> wrote:<br><br>Hi all,<br><br>One of the policy proposals that I've updated a week ago, is attached in PDF.<br><br>As usual, it tries to address the inputs from the list, meeting and staff analysis.<br><br>Please, let me know any inputs.<br><br>Regards,<br>Jordi<br>@jordipalet<br><br><br><br><br><br>**********************************************<br>IPv4 is over<br>Are you ready for the new Internet ?<br><a href="http://www.theipv6company.com">http://www.theipv6company.com</a><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><AfriNIC-ASN-no-multihoming-v3.pdf>_______________________________________________<br>RPD mailing list<br>RPD@afrinic.net<br>https://lists.afrinic.net/mailman/listinfo/rpd<o:p></o:p></span></p></blockquote><p class=MsoNormal style='margin-left:35.4pt'><span style='font-size:9.0pt;font-family:Helvetica'><br><br><br><br><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:Helvetica'>http://www.theipv6company.com</span></a><span style='font-size:9.0pt;font-family:Helvetica'><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><br><br>_______________________________________________<br>RPD mailing list<br></span><a href="mailto:RPD@afrinic.net"><span style='font-size:9.0pt;font-family:Helvetica'>RPD@afrinic.net</span></a><span style='font-size:9.0pt;font-family:Helvetica'><br></span><a href="https://lists.afrinic.net/mailman/listinfo/rpd"><span style='font-size:9.0pt;font-family:Helvetica'>https://lists.afrinic.net/mailman/listinfo/rpd</span></a><o:p></o:p></p></div></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>