<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Dec 19, 2009, at 12:25 AM, Michel Py wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div><blockquote type="cite">Leo Bicknell wrote:<br></blockquote><blockquote type="cite">As I see it, the problem space has three, high level,<br></blockquote><blockquote type="cite">diverging paths:<br></blockquote><blockquote type="cite">A Multihoming happens entirely at the host, making<br></blockquote><blockquote type="cite">PA-only possible.<br></blockquote><blockquote type="cite">B The routing system can scale to PI, so everyone has PI.<br></blockquote><blockquote type="cite">C Neither A or B is possible, so we attempt to decide<br></blockquote><blockquote type="cite">who is worthy of PI.<br></blockquote><br>There is also D: Dual space protocols (ID/LOC). None of them really got<br>traction in the IETF.<br><br><blockquote type="cite">It seems to me we are in case C now.<br></blockquote><br>We are. And in the case of IPv6, we are because the RIRs passed policies<br>to allocate PI to non-LIRs, not because the IETF wanted so.<br><br></div></blockquote>Space A is a non-starter in the real world and was a strong barrier to</div><div>IPv6 adoption. The IETF wanting to restrict the world to case A</div><div>simply wasn't going to fly. The RIRs recognized this and passed</div><div>pragmatic policy to enable IPv6 to get deployed, since it was far</div><div>more important to get people moving on IPv6 than to pretend we</div><div>didn't have to solve the routing scalability problem.</div><div><br></div><div>The fact that the IETF couldn't see this does not really further the</div><div>discussion.</div><div><blockquote type="cite"><div><font class="Apple-style-span" color="#000000"><br></font></div><div>Sadly, nothing matches the raw simplicity of this unique PI prefix that,<br>unfortunately, makes the DFZ big.<br><br></div></blockquote>It doesn't have to, if you consider using a different locator for your IDR</div><div>forwarding decisions, such as destination ASN.</div><div><br></div><div>Owen</div><div><br></div></body></html>