<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div>
<div>On Mar 27, 2013, at 8:50 PM, William Herrin <<a href="mailto:bill@herrin.us">bill@herrin.us</a>> wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">/32, just as the IETF recommends. Given sound technical reasons to<br>
diverge from the IETF's suggestion, I'll lead the charge. But what<br>
sound technical reason do we have for discouraging ISPs, any ISPs of<br>
any size, from starting with at least a /32?</blockquote>
<br>
</div>
<div>Bill - </div>
<div> </div>
<div> The IETF does indeed note in RFC 4029 "Scenarios and Analysis for </div>
<div> Introducing IPv6 into ISP Networks" that the typical ISP would get</div>
<div> a /32, but also recognizes this might not be true for smaller ISPs:</div>
<div><span style="white-space: pre-wrap; "> </span></div>
<div><span style="white-space: pre-wrap; ">"This document is not aimed at covering small ISPs, hosting providers,</span></div>
<div><span style="white-space: pre-wrap; ">or data centers; only the scenarios applicable to ISPs eligible for</span></div>
<div><span style="white-space: pre-wrap; ">at least a /32 IPv6 prefix allocation from an RIR are covered."</span></div>
<div><span style="white-space: pre-wrap; "><br>
</span></div>
<div><span style="white-space: pre-wrap; ">We certainly can have a fee table which ends at the bottom with a /32</span></div>
<div><span style="white-space: pre-wrap; ">of IPv6 space, but given the number of ISPs in that size allocation then</span></div>
<div><span style="white-space: pre-wrap; ">we would also likely have to carry with it very similar fees </span><span style="white-space: pre-wrap; ">as
</span><span style="white-space: pre-wrap; ">today. </span></div>
<div><span style="white-space: pre-wrap; ">By</span><span style="white-space: pre-wrap; "> recognizing smaller categories for smaller ISPs, we are
</span><span style="white-space: pre-wrap; ">enabling them </span></div>
<div><span style="white-space: pre-wrap; ">to get an IPv6 allocation with far lower fees than would
</span><span style="white-space: pre-wrap; ">otherwise be </span></div>
<div><span style="white-space: pre-wrap; ">possible, and would be quite ironic to deny them that
</span><span style="white-space: pre-wrap; ">opportunity</span><span style="white-space: pre-wrap; "> in </span></div>
<div><span style="white-space: pre-wrap; ">the name of "encouraging IPv6" via one size fits all.</span></div>
<div><span style="white-space: pre-wrap; "><br>
</span></div>
<div><span style="white-space: pre-wrap; ">FYI,</span></div>
<div><span style="white-space: pre-wrap; ">/John</span></div>
<div><span style="white-space: pre-wrap; "><br>
</span></div>
<div><span style="white-space: pre-wrap; ">John Curran</span></div>
<div><span style="white-space: pre-wrap; ">President and CEO</span></div>
<div><span style="white-space: pre-wrap; ">ARIN</span></div>
<div><span style="white-space: pre-wrap; "><br>
</span></div>
<div><span style="white-space: pre-wrap; "><br>
</span></div>
</body>
</html>