[arin-ppml] Revised - Draft Policy ARIN-2026-4: Harmonize Section 1 and Section 6, Principles and Goals Statements

Mike Burns mike at sum.net
Wed Nov 18 10:32:16 EST 2026


But the principles and goals for these resource types can be different. You can’t focus on only one at the expense of others. When I say “free” pools, I mean as opposed to priced addresses.  

 

I mean Ipv6, 4.10,4.4, and the waiting list.

 

I don’t think the goals of each are fully aligned, and would support removing section 1.5.

 

Regards,
Mike

 

 

 

 

From: David Farmer <farmer at umn.edu> 
Sent: Tuesday, November 17, 2026 2:46 PM
To: Jones, Brian <bjones at vt.edu>
Cc: Mike Burns <mike at iptrading.com>; arin-ppml at arin.net
Subject: Re: [arin-ppml] Revised - Draft Policy ARIN-2026-4: Harmonize Section 1 and Section 6, Principles and Goals Statements

 

This is only true for IPv4; IPv6 and ASNs both have sizable free pools. The Principles and Goals for ARIN's policies should not focus on IPv4 limitations; they should focus on the abundance of IPv6 and ASNs.

 

On Tue, Nov 17, 2026 at 1:26 PM Jones, Brian <bjones at vt.edu <mailto:bjones at vt.edu> > wrote:

Hi Mike,  

 

Thank you for the feedback. I’m not sure “Free” is the correct word to use here either, since there really is no free pool of addresses, only those reclaimed or returned besides the Reserved pools. Also it sounds like you would be in favor of removing the proposed 1.5 Section “Fairness” from the NRPM, is that your stance?

 

Again your feedback is greatly appreciated.

 

_

Brian





On Nov 17, 2026, at 9:43 AM, Mike Burns via ARIN-PPML <arin-ppml at arin.net <mailto:arin-ppml at arin.net> > wrote:

 

Hi,

 

“Conservation of these common number spaces requires that Internet number resources be efficiently distributed to those organizations who have a technical need for them in support of operational networks.”

 

This line from the NRPM is no longer true, and conservation does NOT require allocations from the RIRs to those with a justified need.

The word I point to is “requires”. 

 

A small historical lesson. ARIN codified and implemented this particular language on January 15th, 2014. 

Just three weeks later, RIPE accepted the policy removing conservation as an explicit goal of IPv4 distribution on February 4th, 2014.

 

RIPE recognized that exhaustion of the free pool eliminated the original rationale for needs-based controls. Price creates conservation. Only distributions from the free pools should require justification. Good stewardship requires the lightest effective touch.

 

I suggest “Conservation of these common number spaces requires that internet number resources from ARIN’s free pools be efficiently distributed to those organizations who have a technical need for them in support of operational networks.”

 

As Eric pointed out, it is hard to use the word “fairness” without definition while in the face of plainly UNfair policies.

But defining that word could be a morass. I like keeping it out of the main goals section, thus allowing for different goals in different situations.

 

Regards,

Mike

 

 

 

 

 

 

From: ARIN-PPML <arin-ppml-bounces at arin.net <mailto:arin-ppml-bounces at arin.net> > On Behalf Of John Curran
Sent: Monday, November 16, 2026 10:42 AM
To: Eric C. Landgraf <echarlie at vt.edu <mailto:echarlie at vt.edu> >
Cc: arin-ppml at arin.net <mailto:arin-ppml at arin.net> 
Subject: Re: [arin-ppml] Revised - Draft Policy ARIN-2026-4: Harmonize Section 1 and Section 6, Principles and Goals Statements

 

Eric –

 

An excellent observation, and the staff and legal review of 25 September 2026 < <https://www.arin.net/participate/policy/drafts/2026_4/#staff-and-legal-review-25-september-2026> https://www.arin.net/participate/policy/drafts/2026_4/#staff-and-legal-review-25-september-2026> speaks to this very point. 

 

Staff reads the proposed 1.5 as mirroring the current 6.3.6: a statement that ARIN administers policies fairly and impartially, not a definition of fairness or a requirement that policies be justified against it (and legal review agreed with that understanding.)  

 

If the community would prefer that the policy text say so expressly, then aligning the proposed 1.5 with the "fair and impartial" administration language of PDP 1.4.1 would accomplish that goal more explicitly, 

 

Thanks! 

/John

 

John Curran

President and CEO

American Registry for Internet Numbers

 

On Nov 16, 2026, at 10:19 AM, Eric C. Landgraf < <mailto:echarlie at vt.edu> echarlie at vt.edu> wrote:

 

As I stated for the first draft, I generally support this policy. But as
I noted at ARIN 58, I think we need to be very careful about including
"fairness" as a goal.

ARIN should enforce the policies fairly. However, some policies,
especially around allocation of IPv4 addresses, are inherently UNfair.
This is of course a matter of perspective, but 4.4 and 4.10 space
clearly favor certain types of organizations. Should we choose to move
that fairness statement into the main goals, we should be very careful
as a community to agree on a definition of fairness where clearly
discriminatory policies meeting the proposed 1.1 thru 1.4 can be
construed as fair without invoking the proposed 1.6.

As a possible solution, we should revise the proposed 1.5 to say that
polcies should be "enforced" fairly, not that they should "apply"
fairly.

Regards,
Eric C. Landgraf
Virginia Tech

On Nov 10 14:43, ARIN wrote:

The following Draft Policy has been revised:

*Draft Policy ARIN-2026-4: Harmonize Section 1 and Section 6, Principles and Goals Statements

Revised text is below and can be found at:

 <https://www.arin.net/participate/policy/drafts/2026_4> https://www.arin.net/participate/policy/drafts/2026_4

A PDF document showing the proposed NRPM edits is available to download at:

 <https://www.arin.net/participate/policy/drafts/pdf/ARIN_2026_4_diff_111026.pdf> https://www.arin.net/participate/policy/drafts/pdf/ARIN_2026_4_diff_111026.pdf


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/> https://www.arin.net/participate/policy/pdp/

Draft Policies and Proposals under discussion can be found at:  <https://www.arin.net/participate/policy/drafts/> https://www.arin.net/participate/policy/drafts/

Regards,

Eddie Diego
Policy Analyst
American Registry for Internet Numbers (ARIN)


Draft Policy ARIN-prop-352: Harmonize Section 1 and Section 6, Principles and Goals Statements

Problem Statement: 

There are two main sections of the NRPM that discuss principles and goals; one is found in Section 1, and the other in Section 6; similar language in Section 4 has been previously retired. Given the history of these two sections, there are multiple redundancies and incongruities in their language. This proposal seeks to clarify the language of both sections in order to better communicate ARIN’s principles and goals.

This policy proposal is not intended to make meaningful changes to these goals and principles, but to clarify their language and remove duplication. Any analysis that suggests otherwise should be addressed.

Policy Statement: 

Original Text:

Principles and Goals of the American Registry for Internet Numbers (ARIN)
1.1. Registration

The principle of registration guarantees the uniqueness of Internet number resources. Provision of this public registry documenting Internet number resource allocation, reallocation, assignment, and reassignment is necessary:

to ensure uniqueness,
to provide a contact in case of operational/security problems,
to provide the transparency required to ensure that Internet number resources are efficiently utilized, and
to assist in IP allocation studies.

1.2. Conservation

The principle of conservation guarantees sustainability of the Internet through efficient utilization of unique number resources.

Due to the requirement for uniqueness, Internet number resources of each type are drawn from a common number space. Conservation of these common number spaces requires that Internet number resources be efficiently distributed to those organizations who have a technical need for them in support of operational networks.

1.3. Routability

The principle of routability guarantees that Internet number resources are managed in such a manner that they may be routed on the Internet in a scalable manner.

While routing scalability is necessary to ensure proper operation of Internet routing, allocation or assignment of Internet number resources by ARIN in no way guarantees that those addresses will be routed by any particular network operator.

1.4. Stewardship

The principle of stewardship guarantees the application of these principles when managing Internet number resources.

The fundamental purpose of Internet number stewardship is to distribute unique number resources to entities building and operating networks thereby facilitating the growth and sustainability of the Internet for the benefit of all.

It should be noted that the above goals may sometimes be in conflict with each other and with the interests of individual end-users or network operators. Care must be taken to ensure balance with these conflicting goals given the resource availability, relative size of the resource, and number resource specific technical dynamics, for each type of number resource.

6.3. Goals of IPv6 Address Space Management

6.3.1. Goals

IPv6 address space is a public resource that must be managed in a prudent manner with regards to the long-term interests of the internet. Responsible address space management involves balancing a set of sometimes competing goals. The following are the goals relevant to IPv6 address policy.

6.3.2. Uniqueness

Every assignment and/or allocation of address space must guarantee uniqueness worldwide. This is an absolute requirement for ensuring that every public host on the Internet can be uniquely identified.

6.3.3. Registration

Internet address space must be registered in a registry database accessible to appropriate members of the Internet community. This is necessary to ensure the uniqueness of each Internet address and to provide reference information for Internet troubleshooting at all levels, ranging from all RIRs and IRs to end users.

The goal of registration should be applied within the context of reasonable privacy considerations and applicable laws.

6.3.4. Aggregation

Wherever possible, address space should be distributed in a hierarchical manner, according to the topology of network infrastructure. This is necessary to permit the aggregation of routing information by ISPs, and to limit the expansion of Internet routing tables.

This goal is particularly important in IPv6 addressing, where the size of the total address pool creates significant implications for both internal and external routing.

IPv6 address policies should seek to avoid fragmentation of address ranges.

Further, RIRs should apply practices that maximize the potential for subsequent allocations to be made contiguous with past allocations currently held. However, there can be no guarantee of contiguous allocation.

6.3.5. Conservation

Although IPv6 provides an extremely large pool of address space, address policies should avoid unnecessarily wasteful practices. Requests for address space should be supported by appropriate documentation and stockpiling of unused addresses should be avoided.

6.3.6. Fairness

All policies and practices relating to the use of public address space should apply fairly and equitably to all existing and potential members of the Internet community, regardless of their location, nationality, size or any other factor.

6.3.7. Minimized Overhead

It is desirable to minimize the overhead associated with obtaining address space. Overhead includes the need to go back to RIRs for additional space too frequently, the overhead associated with managing address space that grows through a number of small successive incremental expansions rather than through fewer, but larger, expansions.

6.3.8. Conflict of Goals

The goals described above will often conflict with each other, or with the needs of individual IRs or end users. All IRs evaluating requests for allocations and assignments must make judgments, seeking to balance the needs of the applicant with the needs of the Internet community as a whole.

In IPv6 address policy, the goal of aggregation is considered to be the most important.

Proposal Text:

Principles and Goals of the American Registry for Internet Numbers (ARIN)

Update Sections 1.1, 1.2, 1.3 and 1.4 as follows:

1.1. Registration (refactor of original language)

The provisioning of a public registry documenting Internet number resource allocation, reallocation, assignment, and reassignment is necessary:

to ensure the uniqueness of allocated resources,
to provide operational and security contacts for resource holders,
to provide the transparency required to ensure that Internet number resources are efficiently utilized, and
to provide data for the research and reporting of allocation activity.

1.2. Conservation (moving language from 6.3.5, integrating into existing)

Due to the requirement for uniqueness, Internet number resources of each type are drawn from a common number space. Conservation of these common number spaces requires that these resources be efficiently distributed to those organizations who have a technical need for them in support of operational networks. Requests for address space should be supported by appropriate documentation; stockpiling of unused addresses should be discouraged.

1.3. Routability and Scalability (moving language from 6.3.4, integrating into existing)

Wherever possible, address space should be distributed in a hierarchical manner, according to the topology of network infrastructure. This is necessary to permit the aggregation of routing information by LIRs, and to limit the expansion of Internet routing tables.

Where possible, address policies should seek to avoid fragmentation of address ranges.

While routing scalability is necessary to ensure proper operation of Internet routing, allocation or assignment of Internet number resources by ARIN in no way guarantees that those addresses will be routed by any particular network operator.

1.4. Stewardship (removing language and moving to new sections harmonized with original 6.3. sections)

The fundamental purpose of Internet number stewardship is to distribute unique number resources to entities building and operating networks thereby facilitating the growth and sustainability of the Internet for the benefit of all.

Add new sections, with language borrowed from original section 1.4 and sections 6.3.6 and 6.3.7:

1.5 Fairness

All policies and practices relating to the use of public address space should apply fairly and equitably to all existing and potential members of the Internet community.

1.6 Conflict of Goals It should be noted that the above goals may sometimes be in conflict with each other and with the interests of individual end-users or network operators. Care must be taken to ensure balance with these conflicting goals given the resource availability, relative size of the resource, and number resource specific technical dynamics, for each type of number resource.

6.3. Goals of IPv6 Address Space Management

Update 6.3.1 to reference earlier principals and goals statements:

6.3.1. Goals

IPv6 address space, like other resources under ARIN’s purview, must be managed in a prudent manner in keeping with the long-term interests of the Internet. Responsible address space management involves balancing a set of potentially competing goals. In addition to the general principles and goals in Section 1, the following principles and goals should be followed in managing IPv6 address resources:

Remove 6.3.2 and 6.3.3 as redundant to 1.2 and 1.1:

6.3.2. (retired)

6.3.3. (retired)

Modify 6.3.4, moving more generic language to 1.3 while keeping IPv6-specific language

6.3.4. Aggregation

Wherever possible, address space should be distributed in a hierarchical manner, according to the topology of network infrastructure. This is necessary to permit the aggregation of routing information by ISPs, and to limit unnecessary expansion of the size of Internet routing tables.

IPv6 address policies should seek to avoid fragmentation of address ranges. ARIN will apply practices that maximize the potential for subsequent allocations to be made contiguous with past allocations currently held; however, there can be no guarantee of contiguous allocation.

When managing IPv6 address resources, the goal of Aggregation should be considered the most important.

6.3.5. (retired)

6.3.6. (retired)

6.3.7. Minimized Overhead

It is desirable to minimize the overhead associated with obtaining address space. Overhead includes the need to request additional space too frequently and the overhead associated with managing address space that grows through a number of small successive incremental expansions, rather than through fewer, but larger, expansions.

Remove 6.3.8 as redundant to 1.6 (which now calls out the IPv6-specific priority of conflicting goals)

6.3.8. (retired)

Comments

This proposal is being submitted as a work product of the ARIN Advisory Council Policy Experience Report Working Group (PERWG).

As stated earlier, this is intended to be solely a language cleanup and harmonization, and is submitted with no intention to materially change allocation policies. All parties should carefully review the updated language and call out potential changes in policy that may happen unintentionally with the adoption of this language.


_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List ( <mailto:ARIN-PPML at arin.net> ARIN-PPML at arin.net).
Unsubscribe or manage your mailing list subscription at:
 <https://lists.arin.net/mailman/listinfo/arin-ppml> https://lists.arin.net/mailman/listinfo/arin-ppml
Please contact  <mailto:info at arin.net> info at arin.net if you experience any issues.

_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List ( <mailto:ARIN-PPML at arin.net> ARIN-PPML at arin.net).
Unsubscribe or manage your mailing list subscription at:
 <https://lists.arin.net/mailman/listinfo/arin-ppml> https://lists.arin.net/mailman/listinfo/arin-ppml
Please contact  <mailto:info at arin.net> info at arin.net if you experience any issues.

 

_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List (ARIN-PPML at arin.net <mailto:ARIN-PPML at arin.net> ).
Unsubscribe or manage your mailing list subscription at:
https://lists.arin.net/mailman/listinfo/arin-ppml
Please contact info at arin.net <mailto:info at arin.net>  if you experience any issues.

 

_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List (ARIN-PPML at arin.net <mailto:ARIN-PPML at arin.net> ).
Unsubscribe or manage your mailing list subscription at:
https://lists.arin.net/mailman/listinfo/arin-ppml
Please contact info at arin.net <mailto:info at arin.net>  if you experience any issues.




 

-- 

Thank you / Ho Pidamayado / Miigwech

===============================================
David Farmer               Email:farmer at umn.edu <mailto:Email%3Afarmer at umn.edu> 
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota   
2829 University Ave SE, Room 200G   
Minneapolis, MN 55414   

Phone: 612-626-0815  Cell: 612-812-9952
=============================================== 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20261118/5d94cd1a/attachment-0001.htm>


More information about the ARIN-PPML mailing list