This seems like a big improvement. However, given that the requirements to qualify for MDN are the same for IPv4 and IPv6, would it make sense to split that out into a common location (maybe a new top level section, or a Section 2 definition)? Then the protocol specific differences (e.g. how being an MDN changes the utilization requirements) is all that needs to remain in Sections 4 and 6.
Tyler On Thu, 2024-06-20 at 12:33 -0400, ARIN wrote: > The following Draft Policy has been revised: > > * ARIN-2023-7: Clarification of NRPM Sections 4.5 and 6.11 Multiple Discrete > Networks > > Revised text is below and can be found at: > > https://www.arin.net/participate/policy/drafts/2023_7/ > > 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 2023-7: Clarification of NRPM Sections 4.5 and 6.11 Multiple > Discrete Networks > > Problem Statement: > > Section 4.5 and 6.11 of the NRPM does not adhere to the style guide used by > the remainder of the document. The numbered lists in these two sections also > detracts from the readability and usability of the NRPM. > > Policy Statement: > > Current: > > 4.5 Multiple Discrete Networks > > Organizations with multiple discrete networks desiring to request new or > additional address space under a single Organization ID must meet the > following criteria: > > 1. The organization shall be a single entity and not a consortium of smaller > independent entities. > > 2. The organization must have compelling criteria for creating discrete > networks. Examples of a discrete network might include: > > 3. Regulatory restrictions for data transmission, > > 4. Geographic distance and diversity between networks, > > 5. Autonomous multihomed discrete networks. > > 6. The organization must keep detailed records on how it has allocated space > to each location, including the date of each allocation. > > 7. When applying for additional internet address registrations from ARIN, the > organization must demonstrate utilization greater than 50% of both the last > block allocated and the aggregate sum of all blocks allocated from ARIN to > that organization. If an organization is unable to satisfy this 50% minimum > utilization criteria, the organization may alternatively qualify for > additional internet address registrations by having all unallocated blocks of > addresses smaller than ARIN’s current minimum allocation size. > > 8. The organization may not allocate additional address space to a location > until each of that location’s address blocks are 80% utilized. > > 9. The organization should notify ARIN at the time of the request their desire > to apply this policy to their account. > > 10. Upon verification that the organization has shown evidence of deployment > of the new discrete network site, the new network(s) shall be allocated the > minimum allocation size under section 4.2.1.5. > > Proposed: > > Replace Section 4.5 in its entirety with the following text: > > 4.5 Multiple Discrete Networks > > Organizations with multiple discrete networks desiring to request a new or > additional IP address space allocation under a single Organization ID must > meet the following criteria: > > 1. The organization must be a single entity and not a consortium of > smaller independent entities. > > 2. The organization must have compelling criteria for creating > discrete networks. Examples of situations which may represent compelling > criteria for multiple discrete networks might include: > * Regulatory restrictions for data transmission; > * Geographic distance and diversity between networks > * Autonomous multihomed discrete networks. > > 3. The organization must keep detailed records on how it has > allocated IP addresses to each location, including the date of each > allocation. > > 4. When applying for additional Internet Resource allocations from > ARIN, the organization must demonstrate utilization greater than 50% of both > the last IP addresses allocated and the aggregate sum of all IP addresses > allocated from ARIN to that organization. If an organization is unable to > satisfy this 50% minimum utilization criteria, the organization may > alternatively qualify for additional internet IP address allocations by having > all unallocated IP address blocks smaller than ARIN’s current minimum > allocation size. > > 5. The organization must not allocate additional IP address space to > a location until each of that location’s IP address allocations are 80% > utilized. > > The organization must notify ARIN at the time of the request of their desire > to apply this policy to their account. > > > Current: > > 6.11. IPv6 Multiple Discrete Networks > > Organizations with multiple discrete IPv6 networks desiring to request new or > additional address space under a single Organization ID must meet the > following criteria: > > 1. The organization shall be a single entity and not a consortium of smaller > independent entities. > > 2. The organization must have compelling criteria for creating discrete > networks. Examples of a discrete network might include: > > * Regulatory restrictions for data transmission, > > * Geographic distance and diversity between networks, > > * Autonomous multihomed discrete networks. > > 3. The organization must keep detailed records on how it has allocated space > to each location, including the date of each allocation. > > 4. The organization should notify ARIN at the time of the request their desire > to apply this policy to their account. > > 5. Requests for additional space: > > 6. Organization must specify on the application which discrete network(s) the > request applies to > > 7. Each network will be judged against the existing utilization criteria > specified in 6.5.2 and 6.5.3 as if it were a separate organization, rather > than collectively as would be done for requests outside of this policy. > > Proposed: > > Replace Section 6.11 in its entirety with the following text: > > 6.11. IPv6 Multiple Discrete Networks > > Organizations with multiple discrete IPv6 networks desiring to request new or > additional IPv6 address allocations under a single Organization ID must meet > the following criteria: > > 1. The organization must be a single entity and not a consortium of > smaller independent entities. > > 2. The organization must have compelling criteria for creating > discrete networks. Examples of situations which may represent compelling > criteria for multiple discrete networks might include: > * Regulatory restrictions for data transmission; > * Geographic distance and diversity between networks > * Autonomous multihomed discrete networks. > > 3. The organization must keep detailed records on how it has > allocated IPv6 addresses to each location, including the date of each IPv6 > address allocation. > > 4. When an organization is requesting additional space under this > policy, the organization must specify on the application which discrete > network(s) the IPv6 address request applies to. A request for additional space > will be judged against the existing utilization criteria specified in 6.5.2 > and 6.5.3 as if it were a separate organization, rather than collectively as > would be done for requests outside of this policy. > > The organization must notify ARIN at the time of the request their desire to > apply this policy to their account. > > > Comments: > > The working group considered entering 3 separate proposals but decided that > the parts are all related enough to combine into one proposal; community > feedback recommended that a previously-included definition of the > Organizational Identifier term be moved into a separate policy. > > Timetable 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.
