Subject: Feedback on ARIN-2024-7: Addition of Definitions for General and
Special Purpose IP Addresses

Dear ARIN Policy Team,

Thank you for sharing the revised draft policy ARIN-2024-7. I appreciate
the effort to make ARIN policies clearer and more concise.

I agree with William Herrin’s feedback regarding the term "Reserved." Since
it has a specific meaning in IP standards, using a different term, such as
"Defined Purpose IP Addresses" or "Special Purpose IP Addresses," might
reduce potential confusion and align better with the intended purpose.

Additionally, it could be helpful to include a few examples of how these
addresses might be used (e.g., testing, critical infrastructure, IPv6
support). This would provide additional clarity for those interpreting the
policy.

I look forward to further discussions on this and welcome feedback from
others in the community.

Best regards,
Mohibul Mahmud

Cloud Engineer at Microsoft

ARIN 52 Fellow





On Sat, Dec 14, 2024 at 12:00 PM <[email protected]> wrote:

> Send ARIN-PPML mailing list submissions to
>         [email protected]
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.arin.net/mailman/listinfo/arin-ppml
> or, via email, send a message with subject or body 'help' to
>         [email protected]
>
> You can reach the person managing the list at
>         [email protected]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of ARIN-PPML digest..."
>
>
> Today's Topics:
>
>    1. Revised - ARIN-2024-7: Addition of Definitions for General
>       and Special Purpose IP Addresses (ARIN)
>    2. Re: Revised - ARIN-2024-7: Addition of Definitions for
>       General and Special Purpose IP Addresses (William Herrin)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 13 Dec 2024 13:41:38 -0500
> From: ARIN <[email protected]>
> To: <[email protected]>
> Subject: [arin-ppml] Revised - ARIN-2024-7: Addition of Definitions
>         for General and Special Purpose IP Addresses
> Message-ID: <[email protected]>
> Content-Type: text/plain;       charset="UTF-8"
>
> 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/
>
> 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 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.
>
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 13 Dec 2024 12:42:36 -0800
> From: William Herrin <[email protected]>
> Cc: [email protected]
> Subject: Re: [arin-ppml] Revised - ARIN-2024-7: Addition of
>         Definitions for General and Special Purpose IP Addresses
> Message-ID:
>         <CAP-guGXkjK3dUAF+qREkN7GzWvcN_q12RoRSR=
> [email protected]>
> Content-Type: text/plain; charset="UTF-8"
>
> On Fri, Dec 13, 2024 at 10:41?AM ARIN <[email protected]> wrote:
> > 2.18 Reserved IPv4 and IPv6 Addresses
> > Addresses that are reserved by ARIN for specific purposes including,
>
> "Reserved" has a well known meaning in the context of IP address
> standards. This is not that meaning. Pick another word.
>
> If you want to avoid overlap with other uses, I haven't heard "defined
> purpose addresses" before.
>
> Regards,
> Bill Herrin
>
> --
> William Herrin
> [email protected]
> https://bill.herrin.us/
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> ARIN-PPML mailing list
> [email protected]
> https://lists.arin.net/mailman/listinfo/arin-ppml
>
>
> ------------------------------
>
> End of ARIN-PPML Digest, Vol 234, Issue 4
> *****************************************
>
_______________________________________________
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