<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Nov 25, 2019, at 07:35 , Fernando Frediani <<a href="mailto:fhfrediani@gmail.com" class="">fhfrediani@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" class="">
<div class=""><p class="">Hello Jordi</p><p class="">The change you made on 7.2.2 from "<span class=" diff-chunk jsx-406281813
diff-chunk-removed">Single interconnection, with a
provider that requires a public" to "</span><span class="jsx-406281813 diff-chunk-removed diff-chunk"><span class="jsx-406281813 diff-chunk-inserted diff-chunk">Show a
unique routing policy or demonstrate a technical need for a
coordinated globally unique" means different things in my view
and may make things slightly more difficult for organizations
to receive an ASN.</span></span></p><div class=""><br class=""></div></div></div></blockquote>Fernando,</div><div><br class=""></div><div>A “single interconnection with a provider that requires a public ASN” is an example of a unique routing policy.</div><div>It is also an example of a technical need for a coordinated globally unique ASN.</div><div><br class=""></div><div>However, you are correct in that the two things cited above are each supersets of the example you cite from the previous version of the policy.</div><div><br class=""></div><div>As such, the new wording should make things easier, not more difficult.</div><div><blockquote type="cite" class=""><div class=""><div class=""><p class=""><span class="jsx-406281813 diff-chunk-removed diff-chunk"><span class="jsx-406281813 diff-chunk-inserted diff-chunk">When it
says "show a unique routing policy" doesn't necessarily mean
two Transit providers (it could be an IX, a private peering
to another ASN, etc), but excludes the possibility to have an
ASN with a single Transit Upstream. On the second part that
says "demonstrate a technical need for a coordinated globally
unique ASN" what kind of technical need could for example be
acceptable to justify to have an ASN with a single Transit
Upstream provider (have their own assigned IP space ?) ?<br class="">
My concern is not to exclude de possibility for organizations
to have an ASN even if they have a single interconnection with
their Transit Upstream.</span></span></p></div></div></blockquote>A unique routing policy is any situation in which a stub or transit autonomous system has a difference in interconnection from all other autonomous systems. As such, an IX, a private peering session, a cloud service provider which requires a globally unique ASN for BYO addressing, etc. would all qualify.</div><div><br class=""></div><div>If you have a single upstream who requires that you have a globally unique ASN in order to use BYO addresses, then that is an example of a technical need.</div><div>In essence, any situation where you cannot accomplish your interconnection goals without a globally unique ASN is a technical need.</div><div><br class=""></div><div>FWIW, the language in the current version of the policy is very similar to that which has been in use in the ARIN region for many years without any difficulty for organizations obtaining ASNs on any need.</div><div><br class=""></div><div>Owen</div><div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><p class=""><span class="jsx-406281813 diff-chunk-removed diff-chunk"><span class="jsx-406281813 diff-chunk-inserted diff-chunk">Could you
clarify this please ?</span></span></p><p class=""><span class="jsx-406281813 diff-chunk-removed diff-chunk"><span class="jsx-406281813 diff-chunk-inserted diff-chunk">Thanks<br class="">
Fernando Frediani<br class="">
</span></span></p>
<div class="moz-cite-prefix">On 25/11/2019 08:45, JORDI PALET
MARTINEZ via RPD wrote:<br class="">
</div>
<blockquote type="cite" cite="mid:1D0D8752-0172-4574-B192-CEA80F5B6955@consulintel.es" class="">
<pre class="moz-quote-pre" wrap="">Hi all,
Find attached a new version of the proposal "Multihoming not required for ASN", following the latest inputs in the list.
I've also prepared an online diff of the changes to the proposed policy text, so it is easy to track:
<a class="moz-txt-link-freetext" href="https://www.diffchecker.com/omm6xj7m">https://www.diffchecker.com/omm6xj7m</a>
Regards,
Jordi
@jordipalet
**********************************************
IPv4 is over
Are you ready for the new Internet ?
<a class="moz-txt-link-freetext" href="http://www.theipv6company.com/">http://www.theipv6company.com</a>
The IPv6 Company
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.
</pre>
<br class="">
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
RPD mailing list
<a class="moz-txt-link-abbreviated" href="mailto:RPD@afrinic.net">RPD@afrinic.net</a>
<a class="moz-txt-link-freetext" href="https://lists.afrinic.net/mailman/listinfo/rpd">https://lists.afrinic.net/mailman/listinfo/rpd</a>
</pre>
</blockquote>
</div>
_______________________________________________<br class="">RPD mailing list<br class=""><a href="mailto:RPD@afrinic.net" class="">RPD@afrinic.net</a><br class="">https://lists.afrinic.net/mailman/listinfo/rpd<br class=""></div></blockquote></div><br class=""></body></html>