<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Nov 17, 2010, at 2:10 PM, Ted Mittelstaedt wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>On 11/17/2010 1:30 PM, Owen DeLong wrote:<br><blockquote type="cite">Ignoring the personal attacks, I've answered Ted at length in private email.<br></blockquote><blockquote type="cite"><br></blockquote><br>Owen has indeed responded to the DFZ issue to me via private e-mail. It is a logical, concrete response that really has nothing at all with the items listed here. I wish that he would have included it in his response here.<br><br>Ted<br><br><blockquote type="cite"><br></blockquote></div></blockquote></div><br><div>I consider it pretty well related, but, at Ted's request, I will saddle</div><div>you all with that piece of my response to him:</div><div><br></div><div><blockquote type="cite" style="font-family: monospace; "><blockquote type="cite"><blockquote type="cite">By increasing the maximum amount of space allowed (possibly dramatically),<br></blockquote></blockquote></blockquote><blockquote type="cite" style="font-family: monospace; "><blockquote type="cite"><blockquote type="cite">if anything, this should reduce the impact on the DFZ.<br></blockquote></blockquote></blockquote><blockquote type="cite" style="font-family: monospace; "><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite" style="font-family: monospace; "><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite" style="font-family: monospace; "><blockquote type="cite">And the logical reason for this is....<br></blockquote></blockquote><blockquote type="cite" style="font-family: monospace; "><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite" style="font-family: monospace; ">Because it will reduce the number of organizations that come, get a /32, discover<br></blockquote><blockquote type="cite" style="font-family: monospace; ">that isn't enough, come back, get a /31, fill that up, come back, get a /30... Which<br></blockquote><blockquote type="cite" style="font-family: monospace; ">is one of two possible outcomes of current policy. The other possible outcome<br></blockquote><blockquote type="cite" style="font-family: monospace; ">is that LIRs will be assigning end sites blocks smaller than /48 in order to have<br></blockquote><blockquote type="cite" style="font-family: monospace; ">the ability to support more than ~60,000 customers which, while not harmful<br></blockquote><blockquote type="cite" style="font-family: monospace; ">to the DFZ is harmful to innovation on the internet in general.<br></blockquote><blockquote type="cite" style="font-family: monospace; "><br></blockquote><blockquote type="cite" style="font-family: monospace; ">We have already seen this harmful behavior in Europe (<a href="http://Free.fr/">Free.fr</a> is giving<br></blockquote><blockquote type="cite" style="font-family: monospace; ">customers /60s), Asia (many ISPs are squeezing their customers into<br></blockquote><blockquote type="cite" style="font-family: monospace; ">prefixes of /56 and /64 in order to squeeze their entire networks into<br></blockquote><blockquote type="cite" style="font-family: monospace; ">a /32), and North America (several IPv6 trials have involved prefix sizes<br></blockquote><blockquote type="cite" style="font-family: monospace; ">ranging from /52 to /60).<br></blockquote></div><div><br></div><div><br></div><div>Owen</div><div><br></div></body></html>