<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=""><div><blockquote type="cite" class=""><div class=""><div dir="auto" class=""><div dir="auto" class=""><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word;line-break:after-white-space" class=""><div class="">3.<span style="white-space:pre-wrap" class=""> </span>(not so simple) An organization which has multiple headquarters in multiple countries around the world and which has a significant global network</div><div class=""><span style="white-space:pre-wrap" class=""> </span>infrastructure.</div><div class=""></div></div></blockquote></div></div><div dir="auto" class=""><br class=""></div><div dir="auto" class=""><br class=""></div><div dir="auto" class="">...it sounds as this interesting usecase </div><div dir="auto" class="">requires a *global* policy [1]...i don't </div><div dir="auto" class="">figure well a *regional* RIR fit to offer </div><div dir="auto" class="">that kind of *global* service...i might be wrong </div><div dir="auto" class="">though :-/ but still open to learn, fortunately.</div><div dir="auto" class="">__</div><div dir="auto" class="">[1]: <<a href="https://nro.net/policy/global" class="">https://nro.net/policy/global</a>></div></div></div></blockquote><div><br class=""></div>This is a misunderstanding of what a global policy is and how the global policy process works.</div><div><br class=""></div><div>Global policies don’t govern how RIRs issue address space. Global policies govern how the IANA interacts with RIRs and how</div><div>resources are issued to RIRs from the global free pool (and/or how RIRs can return them to IANA). An example of a global</div><div>policy would be the last 5 /8s issued 1 to each RIR.</div><div><br class=""></div><div>The reality is that the norm for many years has been for such companies to choose to work with one or more of the RIRs in</div><div>one or more of the regions where they have nexus in a manner that is convenient and functional for the company in question.</div><div><br class=""></div><div>Lots of global companies get their addresses from a single RIR and distribute them all over the world. Other companies get</div><div>their addresses from more than one RIR and to varying extents keep them within each given RIRs service region. No RIR</div><div>has a policy absolutely prohibiting out of region use. The closest is the AFRINIC soft landing policy which only restricts</div><div>addresses issued after phase 2 began and even this strict limitation has a narrowly defined exception.</div><div><br class=""></div><div><blockquote type="cite" class=""><div class=""><div dir="auto" class=""><div dir="auto" class=""><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word;line-break:after-white-space" class=""><div class=""><span style="white-space:pre-wrap" class=""> </span>You seem to think that such a company should be forced to deal with the RIR in each and every region in which it operates and get discontiguous</div><div class=""><span style="white-space:pre-wrap" class=""> </span>network space to number its infrastructure in each applicable region.</div><div class=""></div></div></blockquote></div></div><div dir="auto" class=""><br class=""></div><div dir="auto" class=""><br class=""></div><div dir="auto" class="">...not responding for *our* brother, but imho there are many other possibilities; including proposing a global policy [1]. Why all the proponents of those changes in how the RIR system [2] works, should not simply start the existing process [3] in *transparently* submitting a global DPP? </div></div></div></blockquote><div><br class=""></div>Because a global policy is not the correct solution to this problem.</div><div><br class=""></div><div>Nobody is trying to change how the RIR system works. The RIR system already allows addresses to be used globally. The only place where there is any question about this practice is here in AFRINIC and that mostly recently.</div><div><br class=""></div><div>======</div><div>Due to existing litigation, I am limited in what I can say about this, however, I can repeat some already public facts:</div><div><br class=""></div><div>Some years back, there were some Policy Experience Reports where Madhvi called into question the lack of restrictive language in AFRINIC policy in this area.</div><div>A policy proposal was floated in an attempt to create such a restrictive policy regarding out of region use. It met with opposition in the community and</div><div>was eventually (after more than a year and several meetings) withdrawn by the author.</div><div>======</div><div><br class=""></div><div>Hopefully this allows you to understand why there is actually opposition to changing the way the RIR system works into adding territorial usage limitatoins</div><div>on addresses. Hopefully this also helps you understand the purpose and intent of global policies and why that is not actually the correct solution here.</div><div><br class=""></div><div>Thanks for your comments,</div><div><br class=""></div><div>Owen</div><div><br class=""></div><br class=""></body></html>