<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I doubt anyone can really do such aggregation these days. There are all kinds of<div>cases of addresses obtained by global companies from the RIR where HQ is or</div><div>where they have some portion of their infrastructure and having some of that</div><div>space deployed in other regions, etc.</div><div><br></div><div>I don't see the routing table as a major factor here.</div><div><br></div><div>It could affect in-addr delegation, but, I would expect that impact to be minor.</div><div><br></div><div>FWIW, RIPE is now starting to talk about implementing a no-holds-barred</div><div>transfer policy as well.</div><div><br></div><div>Owen</div><div><br><div><div>On Nov 24, 2010, at 2:22 AM, <a href="mailto:cja@daydream.com">cja@daydream.com</a> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div><br></div><div>How do folks feel about how transfers between regions would affect the routing table? We would be in essence punching holes in RIR blocks. This depends entirely on whether there are ISPs filtering or aggregating on regional boundaries based on RIR /8 block allocations. </div>
<div><br></div><div>Thanks!</div><div>----Cathy</div><div><br></div><div><br><div class="gmail_quote">On Wed, Oct 27, 2010 at 8:54 AM, ARIN <span dir="ltr"><<a href="mailto:info@arin.net">info@arin.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">The proposal originator submitted a revised version of the proposal.<br>
<br>
Regards,<br>
<br>
Communications and Member Services<br>
American Registry for Internet Numbers (ARIN)<br>
<br>
<br>
## * ##<br>
<br>
<br>
Policy Proposal 119: Globally Coordinated Transfer Policy<br>
<br>
Proposal Originator: Chris Grundemann, Martin Hannigan, Jason Schiller<br>
<br>
Proposal Version: 2.0<br>
<br>
Date: 27 October 2010<br>
<br>
Proposal type: new<br>
<br>
Policy term: permanent<br>
<br>
Policy statement: Any RIR's resource registrant may transfer IPv4<br>
addresses to the resource registrant of another RIR as long as the two<br>
RIRs agree and exercise Internet stewardship and the values expressed in<br>
RFC2050.<br>
<br>
Rationale: Since individual RIRs now allow transfers, it makes sense to<br>
be able to transfer between regions as well.<br>
<br>
Timetable for implementation: upon ratification of all five RIRs<br>
<br>
Timetable for de-implementation: upon change to this policy text in any RIR<br>
<br>
<br>
<br>
_______________________________________________<br>
PPML<br>
You are receiving this message because you are subscribed to<br>
the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" target="_blank">ARIN-PPML@arin.net</a>).<br>
Unsubscribe or manage your mailing list subscription at:<br>
<a href="http://lists.arin.net/mailman/listinfo/arin-ppml" target="_blank">http://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you experience any issues.<br>
</blockquote></div><br></div>
_______________________________________________<br>PPML<br>You are receiving this message because you are subscribed to<br>the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).<br>Unsubscribe or manage your mailing list subscription at:<br><a href="http://lists.arin.net/mailman/listinfo/arin-ppml">http://lists.arin.net/mailman/listinfo/arin-ppml</a><br>Please contact info@arin.net if you experience any issues.</blockquote></div><br></div></body></html>