> On Jul 14, 2025, at 09:34, David Farmer via ARIN-PPML <[email protected]> > wrote: > > Additionally, allocations from 4.4 and 6.10 are sufficiently covered by the > requirements of section 9 as well. For example, if a critical infrastructure > provider meets the requirements of section 9 and wants to use an allocation > solely outside of the ARIN region, that should be possible. That is the > intent of section 9. >
I wanted to add a quick note that Draft Policy 2024-5, Rewrite of NRPM Section 4.4 Micro-Allocation, does specify that CII allocations are to be used within the ARIN service area. If there’s a call from the community to allow their use outside ARIN territory, then that current Draft Policy’s language would need to be updated. (I will note that that Draft Policy doesn’t seem to allow for global anycast usage, so that might be an edit to contemplate) Thanks, -Chris > > Thanks > > On Mon, Jul 14, 2025 at 9:55 AM Pellak, Kaitlyn via ARIN-PPML > <[email protected]> wrote: > Hi Martin, > Appreciate your feedback. Just to be clear, in your view there are no > revisions to the policy language that would make this proposal more > palatable? > I want to make sure this isn’t a case where we could wordsmith the policy to > prevent conflicts with section 9, or be more specific in the language that > applies to each section. > Thanks, > Kaitlyn > Kaitlyn Pellak > Amazon – Technical Business Developer II > [email protected] > 301.921.5566 > <image001.png> From: ARIN-PPML <[email protected]> on behalf of > Martin Hannigan <[email protected]> > Date: Sunday, July 13, 2025 at 9:16 PM > To: ARIN <[email protected]> > Cc: "[email protected]" <[email protected]> > Subject: RE: [EXTERNAL] [arin-ppml] Draft Policy ARIN-2025-5: Clarify > justification requirements for 4.4, 4.10, 6.10, and 11.10 IP addresses > 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. > - not in favor > Poor policy writing to stamp multiple sections with boilerplate and set up > future conflict with Section 9 - and bloat the NRPM additionally. > Warm regards, > -M> > On Tue, Jul 1, 2025 at 14:35 ARIN <[email protected]> wrote: > On 26 June 2025, the ARIN Advisory Council (AC) accepted “ARIN-prop-344: > Clarify justification requirements for 4.4, 4.10, 6.10, and 11.10 IP > addresses” as Draft Policy. > > Draft Policy ARIN-2025-5 is below and can be found at: > > https://www.arin.net/participate/policy/drafts/2025_5 > > You are encouraged to discuss all Draft Policies on PPML. The AC will > evaluate the discussion to assess the conformance of this draft policy with > ARIN's Principles of Internet number resource policy as stated in the Policy > Development Process (PDP). Specifically, these principles are: > > * Enabling Fair and Impartial Number Resource Administration > * Technically Sound > * Supported by the Community > > The PDP can be found at: > > https://www.arin.net/participate/policy/pdp/ > > Draft Policies and Proposals under discussion can be found at: > https://www.arin.net/participate/policy/drafts/ > > Regards, > > Eddie Diego > Policy Analyst > American Registry for Internet Numbers (ARIN) > > > > Draft Policy ARIN-2025-5: Clarify justification requirements for 4.4, 4.10, > 6.10, and 11.10 IP addresses > > Problem Statement: > > The NRPM text is ambiguous about whether out of region use cases can justify > requests for IP addresses allocated under 4.4, 4.10, 6.10, and 11.10, as well > as whether these IP Addresses impact justification requirements for normal IP > addresses. This change codifies ARIN Staff's current practices to remove this > ambiguity, removing a source of confusion for resource requesters. > > Policy statement: > > Add the following to 4.4: > Justifications for resources under this section must be for use within the > ARIN service region. Resources issued under this section may also be used out > of > region if that use is consistent with the in-region justification (for > example, global Anycast). Resources issued under this section have no impact > on the justification or utilization requirements for requests under any other > section. > > Add the following to 4.10: > Justifications for resources under this section must be for use within the > ARIN service region. Resources issued under this section may also be used out > of region if that use is consistent with the in-region justification (for > example, global Anycast). Resources issued under this section have no impact > on the justification or utilization requirements for requests under any other > section. > > Add the following to 6.10: > Justifications for resources under this section must be for use within the > ARIN service region. Resources issued under this section may also be used out > of region if that use is consistent with the in-region justification (for > example, global Anycast). Resources issued under this section have no impact > on the justification or utilization requirements for requests under any other > section. > > Add Section 11.10: > Justifications for resources under this section must be for use within the > ARIN service region. Resources issued under this section may also be used out > of region if that use is consistent with the in-region justification (for > example, global Anycast). Resources issued under this section have no impact > on the justification or utilization requirements for requests under any other > section. > > Time Table for Implementation: Immediate > > > > > _______________________________________________ > ARIN-PPML > You are receiving this message because you are subscribed to > the ARIN Public Policy Mailing List ([email protected]). > Unsubscribe or manage your mailing list subscription at: > https://lists.arin.net/mailman/listinfo/arin-ppml > Please contact [email protected] if you experience any issues. > _______________________________________________ > ARIN-PPML > You are receiving this message because you are subscribed to > the ARIN Public Policy Mailing List ([email protected]). > Unsubscribe or manage your mailing list subscription at: > https://lists.arin.net/mailman/listinfo/arin-ppml > Please contact [email protected] if you experience any issues. > > > -- > =============================================== > David Farmer Email:[email protected] > Networking & Telecommunication Services > Office of Information Technology > University of Minnesota > 2218 University Ave SE Phone: 612-626-0815 > Minneapolis, MN 55414-3029 Cell: 612-812-9952 > =============================================== > _______________________________________________ > ARIN-PPML > You are receiving this message because you are subscribed to > the ARIN Public Policy Mailing List ([email protected]). > Unsubscribe or manage your mailing list subscription at: > https://lists.arin.net/mailman/listinfo/arin-ppml > Please contact [email protected] if you experience any issues. _______________________________________________ ARIN-PPML You are receiving this message because you are subscribed to the ARIN Public Policy Mailing List ([email protected]). Unsubscribe or manage your mailing list subscription at: https://lists.arin.net/mailman/listinfo/arin-ppml Please contact [email protected] if you experience any issues.
