<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
On Oct 8, 2015, at 1:01 AM, Martin Hannigan <<a href="mailto:hannigan@gmail.com" class="">hannigan@gmail.com</a>> wrote:<br class="">
<div>
<blockquote type="cite" class="">
<div class="">
<div dir="ltr" class=""><br class="">
<div class="gmail_extra">
<div class="gmail_quote">On Fri, Aug 28, 2015 at 4:05 PM, John Curran <span dir="ltr" class="">
<<a href="mailto:jcurran@arin.net" target="_blank" class="">jcurran@arin.net</a>></span> wrote:<br class="">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class="">On Aug 28, 2015, at 1:56 PM, Gary T. Giesen <<a href="mailto:ggiesen@giesen.me" class="">ggiesen@giesen.me</a>> wrote:<br class="">
> Not to beat a dead horse, but I think if an org wants to (or is required to)<br class="">
> make assignments to entities that don't fit that definition, then they<br class="">
> should apply for an ISP block (or have their existing block converted) and<br class="">
> pay the appropriate fees, and allow the rest of us to keep end-user fees<br class="">
> low.<br class="">
<br class="">
</span>We have had a handful of organizations switch from end-user to ISP for the<br class="">
purposes of being able to put in reassignment records (e.g. to improve the<br class="">
usefulness of geolocation), but it is almost certain that others having avoided<br class="">
such a change due to the cost implications.<br class="">
</blockquote>
<div class=""><br class="">
</div>
<div class="">What's the process to make such a change?</div>
</div>
</div>
</div>
</div>
</blockquote>
<br class="">
</div>
<div>We’ve had so few requests of that type that there is no process; we really need to </div>
<div>hear from the community about whether there needs to be two different service</div>
<div>levels (end-users, who cannot sub delegate & ISPs, who can) or whether we can</div>
<div>provide the same registry services to all organizations. Long-term, there will be</div>
<div>a substantial fee differential between end-users and ISPs due to the very material</div>
<div>difference in assignment sizes under IPv6 policies, so we’ll end up at the same </div>
<div>place in the end, but the question remains how to handle services and fees in</div>
<div>the meantime.</div>
<div><br class="">
</div>
<div>We’ll have some time to explore this topic later today during the Fee Schedule </div>
<div>discussion.</div>
<div><br class="">
</div>
<div>Thanks!</div>
<div>/John</div>
<div><br class="">
</div>
<div>John Curran</div>
<div>President and CEO</div>
<div>ARIN</div>
<div><br class="">
</div>
<div><br class="">
</div>
<br class="">
</body>
</html>