<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">
Owen -
<div><br>
</div>
<div>We’ve got a range of possible terms, and each is imperfect in one or more aspects – </div>
<div><br>
</div>
<blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;">
<div>“Direct Registration” actually has different interpretations, including the concept that an address block is distinct from the registration of same. For this reason alone, it’s likely less than ideal. </div>
<div><br>
</div>
<div>“Direct Issuance" would appropriately cover both assignments and allocations, but is awkward to use as a noun.</div>
<div><br>
</div>
<div>“Direct Allocation” is both well understood and encompasses how these address blocks are handled at the present time (and more accurate in many cases as a result of the evolution of the industry towards cloud and hosted service providers.) </div>
</blockquote>
<div><br>
</div>
<div>Anyone looking at how these blocks are handled today will not be confused by the term of art since it is being used in its classic meaning – and if indeed changing Direct Assignment to Direct Allocation results in any degree of confusion, then the same
confusion (or more) would quite likely result from changing both to new terminology altogether. </div>
<div><br>
</div>
<div>Thanks,</div>
<div>/John</div>
<div><br>
</div>
<div>
<div>John Curran</div>
<div>President and CEO</div>
<div>American Registry for Internet Numbers</div>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
<div>
<blockquote type="cite">
<div>On Oct 2, 2023, at 12:58 PM, Owen DeLong via ARIN-PPML <arin-ppml@arin.net> wrote:</div>
<br class="Apple-interchange-newline">
<div>
<div>John,<br>
<br>
At least in my case, this was previously well understood. I appreciate your clarification, but I stand by my suggestion that a new term should be applied. I think “direct registration” is probably the best choice of language. Issuance implies that ARIN had
possession of a thing and provided that thing to the registrant. In reality, nobody possesses or owns integers, but ARIN registers particular integers to particular organizations with the intent that said registrations remain unique within the given registry
(system) for a particular purpose. <br>
<br>
Owen<br>
<br>
<br>
<blockquote type="cite">On Oct 2, 2023, at 09:30, John Sweeting <jsweeting@arin.net> wrote:<br>
<br>
Hello all,<br>
<br>
ARIN staff would like to provide the following clarification on this change.<br>
<br>
The changes being requested in the NRPM through this policy (2022-12) are simply to ensure the NRPM stays synched with the current operational practices of ARIN. Due to the fee harmonization completed in 2022 ARIN no longer does Direct Assignments, ARIN only
does Direct Allocations. Direct Allocations have all the same properties that they have always had. The difference in services being that both ISPs and End Users can now make reassignments and reallocations. Hope that helps.<br>
<br>
John S. <br>
<br>
On 10/2/23, 12:22 PM, "ARIN-PPML on behalf of Owen DeLong via ARIN-PPML" <arin-ppml-bounces@arin.net <mailto:arin-ppml-bounces@arin.net> on behalf of arin-ppml@arin.net <mailto:arin-ppml@arin.net>> wrote:<br>
<br>
<br>
<br>
<br>
<br>
<br>
<blockquote type="cite">On Oct 2, 2023, at 07:21, Pellak, Kaitlyn via ARIN-PPML <arin-ppml@arin.net <mailto:arin-ppml@arin.net>> wrote:<br>
<br>
Hi all,<br>
<br>
<blockquote type="cite">The rationale used was that it was more straightforward to revise the<br>
definition across the NRPM rather than replace each relevant<br>
instance of “allocation” and “assignment” with another term<br>
(allocation appears 245 times, and assignment appears 101 times.)<br>
</blockquote>
<br>
I'm sure this has already been addressed but could we not simply "find and replace" allocation and assignment with the new terms in the NRPM?<br>
<br>
If not, perhaps we should consider a way to make those and similar updates given the ever-changing nature of internet terminology.<br>
</blockquote>
<br>
<br>
Expressing that to the community gets a bit more complicated than the act of doing so.
<br>
<br>
<br>
However, I feel that the effort is warranted for the reasons previously stated. <br>
<br>
<br>
Owen<br>
<br>
<br>
<blockquote type="cite"><br>
Best,<br>
Kaitlyn<br>
<br>
Kaitlyn Pellak <br>
Amazon – Technical Business Developer II <br>
kaitjean@amazon.com <mailto:kaitjean@amazon.com> <mailto:kaitjean@amazon.com <mailto:kaitjean@amazon.com>>
<br>
301.921.5566 <br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
On 10/1/23, 7:10 AM, "ARIN-PPML on behalf of William Herrin" <arin-ppml-bounces@arin.net <mailto:arin-ppml-bounces@arin.net> <mailto:arin-ppml-bounces@arin.net <mailto:arin-ppml-bounces@arin.net>> on behalf of bill@herrin.us <mailto:bill@herrin.us> <mailto:bill@herrin.us
<mailto:bill@herrin.us>>> wrote:<br>
<br>
<br>
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.<br>
<br>
<br>
<br>
<br>
<br>
<br>
<blockquote type="cite">
<blockquote type="cite">On Sat, Sep 30, 2023 at 6:39 PM Douglas Camin <doug@dougcamin.com <mailto:doug@dougcamin.com> <mailto:doug@dougcamin.com <mailto:doug@dougcamin.com>>> wrote:<br>
</blockquote>
Reading the terms Allocation and Assignment, I see the primary<br>
distinction between them as one is “for you” and one is “for you to give to others.”<br>
</blockquote>
<br>
<br>
Hi Douglas,<br>
<br>
<br>
To the extent that there was a "primary" distinction, it's that one<br>
was for organizations acting like an ISP and one was for organizations<br>
acting like end-users. The associated nuance was extensive: everything<br>
from how you justified addresses to your public reporting<br>
responsibilities to not only how much you paid but the very framework<br>
for determining how much you paid. That's what made them "terms of<br>
art." https://www.justia.com/dictionary/term-of-art/ <https://www.justia.com/dictionary/term-of-art/> <https://www.justia.com/dictionary/term-of-art/> <https://www.justia.com/dictionary/term-of-art/>><br>
<br>
<br>
Someone who looks up those terms in connection with ARIN is going to<br>
find all the myriad explanations for how they worked. And be very<br>
confused since things will no longer work that way.<br>
<br>
<br>
The better plan is to pick a new term entirely. Leave assignment and<br>
allocation in the definitions so that you can note that they're<br>
obsolete and no longer used. Doesn't really matter what new words you<br>
choose: they'll become the new term of art attached to the new<br>
operating model.<br>
<br>
<br>
<br>
<br>
<blockquote type="cite">The rationale used was that it was more straightforward to revise the<br>
definition across the NRPM rather than replace each relevant<br>
instance of “allocation” and “assignment” with another term<br>
(allocation appears 245 times, and assignment appears 101 times.)<br>
</blockquote>
<br>
<br>
Understood but respectfully: I think that would be a mistake for the<br>
reason described above.<br>
<br>
<br>
<br>
<br>
Regards,<br>
Bill Herrin<br>
<br>
<br>
<br>
<br>
--<br>
William Herrin<br>
bill@herrin.us <mailto:bill@herrin.us> <mailto:bill@herrin.us <mailto:bill@herrin.us>><br>
https://bill.herrin.us/ <https://bill.herrin.us/> <https://bill.herrin.us/> <https://bill.herrin.us/>><br>
_______________________________________________<br>
ARIN-PPML<br>
You are receiving this message because you are subscribed to<br>
the ARIN Public Policy Mailing List (ARIN-PPML@arin.net <mailto:ARIN-PPML@arin.net> <mailto:ARIN-PPML@arin.net <mailto:ARIN-PPML@arin.net>>).<br>
Unsubscribe or manage your mailing list subscription at:<br>
https://lists.arin.net/mailman/listinfo/arin-ppml <https://lists.arin.net/mailman/listinfo/arin-ppml> <https://lists.arin.net/mailman/listinfo/arin-ppml> <https://lists.arin.net/mailman/listinfo/arin-ppml>><br>
Please contact info@arin.net <mailto:info@arin.net> <mailto:info@arin.net <mailto:info@arin.net>> if you experience any issues.<br>
<br>
<br>
<br>
_______________________________________________<br>
ARIN-PPML<br>
You are receiving this message because you are subscribed to<br>
the ARIN Public Policy Mailing List (ARIN-PPML@arin.net <mailto:ARIN-PPML@arin.net>).<br>
Unsubscribe or manage your mailing list subscription at:<br>
https://lists.arin.net/mailman/listinfo/arin-ppml <https://lists.arin.net/mailman/listinfo/arin-ppml><br>
Please contact info@arin.net <mailto:info@arin.net> if you experience any issues.<br>
</blockquote>
<br>
<br>
_______________________________________________<br>
ARIN-PPML<br>
You are receiving this message because you are subscribed to<br>
the ARIN Public Policy Mailing List (ARIN-PPML@arin.net <mailto:ARIN-PPML@arin.net>).<br>
Unsubscribe or manage your mailing list subscription at:<br>
https://lists.arin.net/mailman/listinfo/arin-ppml <https://lists.arin.net/mailman/listinfo/arin-ppml><br>
Please contact info@arin.net <mailto:info@arin.net> if you experience any issues.<br>
<br>
<br>
<br>
_______________________________________________<br>
ARIN-PPML<br>
You are receiving this message because you are subscribed to<br>
the ARIN Public Policy Mailing List (ARIN-PPML@arin.net).<br>
Unsubscribe or manage your mailing list subscription at:<br>
https://lists.arin.net/mailman/listinfo/arin-ppml<br>
Please contact info@arin.net if you experience any issues.<br>
</blockquote>
<br>
_______________________________________________<br>
ARIN-PPML<br>
You are receiving this message because you are subscribed to<br>
the ARIN Public Policy Mailing List (ARIN-PPML@arin.net).<br>
Unsubscribe or manage your mailing list subscription at:<br>
https://lists.arin.net/mailman/listinfo/arin-ppml<br>
Please contact info@arin.net if you experience any issues.<br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</body>
</html>