<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
Folks -
<div class=""><br class="">
</div>
<div class="">I started writing this initially for the ARIN Advisory Council but realized that it was germane to the current Fee Consultation discussion – i.e. some have asked whether the proposed fee change means the elimination of “assignment” versus “allocation”
IP block types, and the answer is No, not necessarily – it is entirely up to the community whether such distinction continues from a policy perspective (and ARIN services will naturally align with policy, as usual.)
<div class=""><br class="">
</div>
<div class="">FYI,</div>
<div class="">/John</div>
<div class="">
<div class=""><br class="">
</div>
<div>
<blockquote type="cite" class="">
<div class="">On 14 Apr 2021, at 7:37 AM, John Curran <<a href="mailto:jcurran@arin.net" class="">jcurran@arin.net</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
ARIN AC Members -
<div class=""><br class="">
</div>
<blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class="">
<div class="">A topic arose yesterday in open mic regarding policy restrictions on services offered to certain types of blocks in the Internet number registry system, and I wanted to take a moment to be clear about my remarks. In particularly, it occurred
to me that my repeating the same phrases several times didn’t prove particularly conducive to effective communications (and I usually know better), so instead I’m going to try to clarify my remarks below - </div>
<div class=""><br class="">
</div>
<div class="">It is worth noting that the vast majority of registry services for IP blocks are either hierarchical in nature (reverse DNS, RDAP, RPKI, etc.) or allow for inclusion of third-party contact data (Whois, IRR) into their systems. As a result, there
is actually very little from a technical perspective that prevents any given Internet number resource holder from operating their own subdelegation infrastructure or delegating number resource blocks on a temporary/permanent basis to any other party.</div>
<div class=""><br class="">
</div>
<div class="">This makes it particularly important to be very clear about any restrictions on subdelegation for any particular type of IP number resource blocks, and make these restrictions on resource holder (if indeed restrictions are desired.) ARIN will
of course align our services provided for such resources to be compliant with registry policy, but such policy should be defined as limitations on usage by the resource holders of those blocks and be established by the community after full discussion of the
associated benefits/risks. </div>
<div class=""><br class="">
</div>
<div class="">This also has the benefit of freeing the ARIN policy discussion from concerns regarding services and fees – ARIN will respect any policies that restrict resource holders from subdelegation of specific blocks but no discussion of services or fees
is required so long as the policy discussion is clear about what constraints the resource holders face for specific types of Internet number resource blocks. </div>
<div class=""><br class="">
</div>
</blockquote>
I hope this helps clarify my otherwise incoherent ramblings yesterday - please don’t hesitate to ask if there are any questions whatsoever…
<div class=""><br class="">
</div>
<div class="">Thanks!</div>
<div class="">/John</div>
<div class=""><br class="">
</div>
<div class="">
<div class="">John Curran</div>
<div class="">President and CEO</div>
<div class="">American Registry for Internet Numbers</div>
</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
</div>
_______________________________________________<br class="">
ARIN-Consult<br class="">
You are receiving this message because you are subscribed to the ARIN Consult Mailing<br class="">
List (<a href="mailto:ARIN-consult@arin.net" class="">ARIN-consult@arin.net</a>).<br class="">
Unsubscribe or manage your mailing list subscription at:<br class="">
<a href="https://lists.arin.net/mailman/listinfo/arin-consult" class="">https://lists.arin.net/mailman/listinfo/arin-consult</a> Please contact the ARIN Member Services<br class="">
Help Desk at <a href="mailto:info@arin.net" class="">info@arin.net</a> if you experience any issues.<br class="">
</div>
</blockquote>
</div>
<br class="">
</div>
</div>
</body>
</html>