Scott, To clarify, the current draft policy is to propose the addition of a definition for IP addresses that are reserved for specific purposes by ARIN:
Policy Statement: Add the following definition to Section 2 2.18 Reserved IPv4 and IPv6 Addresses Addresses that are reserved by ARIN for specific purposes including, but not limited to; maintaining critical infrastructure, facilitating IPv6 deployment, or temporary experimental purposes as approved by ARIN. Timetable for Implementation: Immediate. The change to text I included in my request for feedback was an example of how the definition could be put into place, only if the proposed definition were added to the NRPM. We felt that gaining community input on the definition itself would be the first step and if it the definition were to be accepted then a follow-up policy to enact the changes in the NRPM would be submitted. If you have thoughts about the current language in the proposed definition that would be helpful in determining whether or not we should move forward. Thanks, Kaitlyn Kaitlyn Pellak Amazon – Technical Business Developer II [email protected]<mailto:[email protected]> 301.921.5566 [/Users/tinam/Library/Containers/com.microsoft.Outlook/Data/Library/Caches/Signatures/signature_1323502979] From: Scott Leibrand <[email protected]> Date: Wednesday, February 26, 2025 at 7:09 PM To: Kaitlyn Pellak <[email protected]> Cc: ARIN <[email protected]>, "[email protected]" <[email protected]> Subject: RE: [EXTERNAL] [arin-ppml] Revised - ARIN-2024-7: Addition of Definitions for General and Special Purpose 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. That would be a very substantial change. It should be proposed separately. I don't see the point of making changes to definitions that aren't referenced anywhere. If you want to add a new definition in order to more clearly make a substantive policy change, then that definition (and the text referencing it) should be included in the substantive policy proposal. If we decide not to make the substantive change, we don't need to change definitions either. -Scott On Wed, Feb 26, 2025 at 9:22 AM Pellak, Kaitlyn via ARIN-PPML <[email protected]<mailto:[email protected]>> wrote: Hello PPML, I am soliciting any additional feedback the community may have on the below policy. Please note, we received one comment suggesting that rather than using the term "2.18 Reserved IPv4 and IPv6 Addresses" we could instead use the term "Defined Purpose IPv4 and IPv6 Addresses." If anyone in the community feels this is better language (or has a suggestion for different language) please respond accordingly. If the community are able to agree on language surrounding a definition there would be subsequent policies to update the language in the NRPM to match. The author provided an example of what that may look like as follows: "Section 4.3.2 Change paragraph 1 text FROM: “End-user organizations without an IPv4 allocation from ARIN qualify for an initial allocation of ARIN’s minimum allocation size.” TO: “End-user organizations without a Reserved (or Defined Purpose) IPv4 allocation from ARIN qualify for an initial allocation of ARIN’s minimum allocation size.”" Given the lack of responses we've received thus far I would also like to pose the question to the community: do you feel that this is a policy the AC should continue to work on? Again, if the community feels strongly one way or another please respond in the PPML so we can gain a sense of whether or not this policy has community support. Much appreciated, Kaitlyn Kaitlyn Pellak Amazon – Technical Business Developer II [email protected]<mailto:[email protected]> <mailto:[email protected]<mailto:[email protected]>> 301.921.5566 On 12/13/24, 1:42 PM, "ARIN-PPML on behalf of ARIN" <[email protected]<mailto:[email protected]> <mailto:[email protected]<mailto:[email protected]>> on behalf of [email protected]<mailto:[email protected]> <mailto:[email protected]<mailto:[email protected]>>> wrote: 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. The following Draft Policy has been revised: * ARIN-2024-7: Addition of Definitions for General and Special Purpose IP Addresses Revised text is below and can be found at: https://www.arin.net/participate/policy/drafts/2024_7/ <https://www.arin.net/participate/policy/drafts/2024_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/ <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-2024-7: Addition of Definitions for General and Special Purpose IP Addresses Problem Statement: The Number Resource Policy Manual (NRPM) often treats general purpose and special purpose IP addresses differently. Unfortunately, we don’t have a convenient to use term to describe these categories, so policy often becomes either excessively wordy or does not correctly capture the intent. Examples of this can be found in section 4.1.8 of the NRPM, and in (currently pending) Draft Policies ARIN-2023-8 (where the fact that 4.4 and 4.10 space isn’t counted against an organization is repeated numerous times) and ARIN-2022-12 (where the text does not exclude 4.4 and 4.10 allocations from being counted against an organization, but it is the intent that those allocations should be ignored). Additionally, temporary allocations under section 11 are rarely carved out, even when 4.4 and 4.10 are, even though it is likely the policy’s intent that these too should be ignored. Policy Statement: Add the following definition to Section 2 2.18 Reserved IPv4 and IPv6 Addresses Addresses that are reserved by ARIN for specific purposes including, but not limited to; maintaining critical infrastructure, facilitating IPv6 deployment, or temporary experimental purposes as approved by ARIN. Timetable for Implementation: Immediate. _______________________________________________ ARIN-PPML You are receiving this message because you are subscribed to the ARIN Public Policy Mailing List ([email protected]<mailto:[email protected]> <mailto:[email protected]<mailto:[email protected]>>). 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 [email protected]<mailto:[email protected]> <mailto:[email protected]<mailto:[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]<mailto:[email protected]>). Unsubscribe or manage your mailing list subscription at: https://lists.arin.net/mailman/listinfo/arin-ppml Please contact [email protected]<mailto:[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.
