The language "makes available for specific purposes including" seems to imply 
that there are purposes other than the ones listed that could be classified as 
"special purpose." To avoid problems or gaming, why not just define special 
purpose exclusively and exhaustively as the three listed purposes (critical 
infra, v6 transition, experimental)?

________________________________
From: ARIN-PPML <[email protected]> on behalf of Pellak, Kaitlyn via 
ARIN-PPML <[email protected]>
Sent: Tuesday, August 20, 2024 2:06 PM
To: [email protected] <[email protected]>
Subject: [arin-ppml] Request for Feedback: ARIN-2024-7 Addition of definitions 
for General and Special Purpose IP Addresses


Hello PPML,



As lead shepherded on this policy I am seeking additional feedback from the 
community. We received some feedback when this was first published to the PPML 
but are seeking input for a clearer direction on how to move forward.



Previous discussion indicated that defining Special and General purposes 
addresses was “mostly harmless” if not strictly necessary. There was also 
encouragement to rethink the wording of the policy language to better reflect 
the intention of the proposal.



Questions for the community:

-Do you support the policy as written?

-If you do not support the policy as written, what changes (if any) would you 
propose?

-Are there unintended consequences that could arise from specifically defining 
general and special purpose IP addresses?



The current text is below, and a link to the PPML achieved discussion on this 
draft can be found 
here<https://lists.arin.net/pipermail/arin-ppml/2024-June/037405.html>.



Thanks in advance,

Kaitlyn Pellak



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 definitions to Section 2

Special Purpose IPv4 Address - An IPv4 address that the NRPM makes available 
for specific purposes including maintaining critical Internet infrastructure 
(Section 4.4), facilitating IPv6 deployment (Section 4.10), or temporarily for 
experimental purposes as approved by ARIN (Section 11).

General Purpose IPv4 Address - Any IPv4 address issued by ARIN that is not 
issued solely for the purposes stated under Special Purpose IPv4 Addresses.

Special Purpose IPv6 Address - An IPv6 address that the NRPM makes available 
for specific purposes such as maintaining critical Internet infrastructure 
(Section 6.10) or temporarily for experimental purposes as approved by ARIN 
(Section 11).

General Purpose IPv6 Address - Any IPv6 address issued by ARIN that is not 
issued solely for the purposes stated under Special Purpose IPv6 Addresses.



Timetable for Implementation: Immediate.





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]




_______________________________________________
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.

Reply via email to