ARIN 54 – Recommended Draft Policies
October 22, 2024
ARIN 54 will be hosted in Toronto, Canada from October 24 to October 25 to discuss with the community current draft policies and recommended draft policies.
Recommended Draft Policies
These are policies that are going to be presented at ARIN 54 to judge consensus to move them to a last call. The Advisory Council has already reviewed these and recommends their adoption.
ARIN-2022-12: Direct Assignment Language Update.
This recommended draft policy updates the NRPM by replacing “assignment” with “allocation” to better match ARIN’s current practices, as direct assignments are no longer a part of their resource distribution model. The change is largely technical, with terms like “assigned” being switched to “issued” for improved clarity and consistency across the NRPM. This aims to eliminate any ambiguity regarding the nature of IP address distributions. Given that this recommended draft policy reflects a shift that has already taken place operationally, it’s expected to be implemented within three months and to have minimal impact on ARIN’s current processes. Community feedback has been relatively quiet, as the recommended draft policy does not introduce major changes.
ARIN-2023-7: Clarification of NRPM Sections 4.5 and 6.11 Multiple Discrete Networks.
This recommended draft policy aims to make the requirements for managing multiple discrete networks clearer by revising Sections 4.5 and 6.11. It updates outdated terms and aligns the sections with ARIN’s style guide, making it easier for organizations to understand the requirements. For example, organizations that want additional IP allocations need to show 50% utilization of their existing space and provide strong reasons for keeping discrete networks. Some community members have supported the revision, seeing it as a way to make the application process smoother and more understandable. However, like all revisions, there needs to be careful consideration to ensure that the new language does not create any additional complications.
ARIN-2024-1: Definition of Organization ID/Org ID.
This recommended draft policy aims to clarify the definition of the Organization Identifier (Org ID) used in ARIN’s documentation, ensuring consistent terminology across all ARIN publications and resources. By formalizing the definition of Org ID, the policy seeks to simplify compliance for organizations and enhance their understanding of how these identifiers are referenced in various policy documents. This clarity will also address inconsistencies in processes such as resource management and registration updates, making interactions with ARIN more efficient. Earlier discussions within the community highlighted the need for a precise definition, with members advocating for clearer terminology to facilitate better understanding and application of ARIN’s requirements.
ARIN-2024-2: Whois Data Requirements Policy for Non-Personal Information.
This recommended draft policy seeks to balance privacy concerns with transparency by clarifying the types of non-personal information that must be made available in ARIN’s public Whois database. It emphasizes the need for essential non-personal data to remain publicly accessible while protecting personal information. Community discussions have centered around finding the right balance between transparency for network operators and privacy for individuals, especially due to evolving regulations. There was a call for further discussion from to increase clarity on this recommended draft policy.
ARIN-2024-9: Remove Outdated Carveout for Community Networks.
This recommended draft policy proposes the removal of a special carveout that allows Community Networks to receive a /40 of IPv6 space, arguing that this provision is no longer necessary. With current rules permitting any Local Internet Registry (LIR) to request this allocation size, this recommended draft policy aims to simplify the Number Resource Policy Manual (NRPM) and treat all organizations under the same criteria. Supporters believe this change will reduce administrative complexity and bring ARIN’s policies up to date with the current needs of the internet community. Community discussion has seen some support that the carveout has outlived its purpose, but further conversation may be needed to ensure that there are no unintended consequences and that everyone is considered.
Draft Policies
These are considered to be a work in progress that will be presented for feedback.
ARIN-2023-8: Reduce 4.1.8 Maximum Allocation.
This draft policy proposes reducing the maximum IPv4 allocation size from a /22 to a /24 to address the lengthy waiting periods for new IPv4 address allocations, which currently extend to around three years. The draft policy aims to give priority to new entrants by restricting eligibility for additional allocations to those who do not already hold IPv4 space, thus freeing up the limited available pool. This would help ensure that organizations new to the internet ecosystem have a chance to secure the resources they need.
The community has been actively discussing the draft policy online, raising concerns about its potential effects on organizations currently on the IPv4 waitlist. One suggestion is to grandfather these waitlisted entities, allowing them to receive allocations based on the previous /22 limit instead of the proposed /24 restriction. As a potential compromise, some community members have proposed a /23 allocation, which would still conserve IPv4 space while providing slightly larger allocations to those in need. However, there is also opposition to further changes, as some believe the waitlist serves an important role in promoting IPv6 adoption.
ARIN-2024-4: Internet Exchange Point Definition.
This draft policy introduces a precise definition of an Internet Exchange Point (IXP) as a shared network used by three or more autonomous systems, providing a consistent reference point across ARIN’s policies. The aim is to eliminate ambiguities that might arise when organizations seek resources specifically for IXP purposes. The definition aligns ARIN’s standards with operational norms observed by IXPs globally, ensuring that draft policy references are consistent with how these infrastructures function in practice. Feedback from the community has been supportive, with stakeholders noting that this clarification helps smooth out policy application in cases involving IXPs. Some members have asked for further details on how the new definition will interact with existing policies on critical infrastructure and micro-allocations. There was also a suggestion to allow a grace period for smaller IXPs to meet the requirement of three autonomous systems.
ARIN-2024-5: Rewrite of NRPM Section 4.4 Micro-Allocation.
This draft policy proposes a rewrite of Section 4.4, which deals with micro-allocations for critical infrastructure like Internet Exchanges and DNS root servers. The updates aim to make the requirements clearer and more in line with current practices by setting minimum criteria for entities eligible for micro-allocations. The new language seeks to ensure that resources are allocated fairly while still supporting the needs of essential internet infrastructure.
Community feedback has highlighted the importance of clear guidelines, with some noting that previous language left too much room for interpretation. However, other members have raised concerns that the stricter criteria might make it more difficult for smaller or emerging IXPs to secure necessary resources. The importance of aligning this draft policy with the proposed definition in ARIN-2024-4 was also discussed to avoid conflicting interpretations. Community members suggest consolidating all definitional text for Internet Exchanges (IX) to ensure consistency and to avoid future synchronization issues.
ARIN-2024-6: 6.5.1a Definition Update.
This draft policy focuses on improving the clarity of Section 6.5.1a of the Number Resource Policy Manual (NRPM) by explicitly defining the interchangeable use of Internet Service Providers (ISPs) and Local Internet Registry (LIRs). This update aims to reduce confusion and ensure that policy language aligns with ARIN’s current practices, making it easier for organizations to understand and comply with ARIN’s allocation guidelines. The proposed change is expected to be implemented immediately, given its minimal operational impact.
Community discussions recognize that this policy addresses longstanding ambiguities in the language. Participants emphasize the need for precise terminology to prevent misunderstandings and highlight the importance of careful evaluation, as broad changes could significantly impact implementation. There’s a call for consistent terminology throughout the NRPM, particularly regarding requirements like physical presence. Overall, there’s a consensus on the need for clear guidelines, with some advocating for specific wording to maintain consistency and understanding within the community.
ARIN-2024-7: Addition of Definitions for General and Special Purpose IP Addresses.
This draft policy introduces precise definitions for “General Purpose” and “Special Purpose” IP addresses within the Number Resource Policy Manual (NRPM). By adding these definitions, ARIN aims to enhance the clarity of its policy language, making it easier for organizations to understand the types of allocations they may qualify for. This change is designed to simplify future policy proposals and discussions, providing a clearer framework for managing IP address allocations while keeping the overall policy structure intact.
Community feedback shows support for ARIN’s initiative to clarify definitions for general and special purpose IP addresses. Many members believe these definitions will help differentiate between everyday and specific functions, aiding resource management. While most view the proposal as harmless, some question its necessity, arguing it may not significantly improve existing policies. Concerns about potential unintended consequences, such as confusion or misinterpretation of rules, highlight the importance of compliance with ARIN policy on special purpose addresses. Participants suggest detailed revisions to enhance clarity and align with ARIN’s allocation practices.
ARIN-2024-8: Restrict the Largest Initial IPv6 Allocation to /20.
This draft policy proposes limiting the largest initial IPv6 allocation size to a /20 to encourage more conservative use of IPv6 space and support long-term address conservation. The intention is to promote efficient address use while still accommodating the needs of growing organizations. Some community members support the draft policy, viewing it as a necessary step for improved resource management and a means to promote conservative allocation practices, especially since larger allocations like a /16 are rarely needed. However, opinions vary regarding the strictness of these proposed restrictions. While some participants stress the importance of requiring clear justifications for larger allocations, others argue that limits are unwarranted if organizations can effectively demonstrate their specific needs.
ARIN-2024-10: Registration Requirements and Timing of Requirements With Retirement of Section 4.2.3.7.2.
This draft policy aims to streamline registration processes for both IPv4 and IPv6 resources, emphasizing timely updates to records. Key changes include a requirement that IPv4 reassignments of /29 or larger must be registered within 14 days and adjustments to ensure IPv6 records are maintained in a similar manner. The goal is to keep ARIN’s records accurate, benefiting both ARIN and the wider internet community by ensuring that routing and contact information remains up to date. While there has not been extensive discussion on this draft policy within the community yet, it is going to be discussed in ARIN 54.
Participate
These proposals will be discussed during the two policy sessions at ARIN 54 on Thursday, October 24, 2024, from 11:10am to 12:20pm and 3:30pm to 4:45pm. To participate in these discussions, please register to attend the conference either on site in Toronto or remotely