<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Aptos;
panose-1:2 11 6 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:10.0pt;
font-family:"Aptos",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Aptos",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">Your emails are getting through John, but I will have our ISS team look into this. Thanks.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div id="mail-editor-reference-message-container">
<div>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">ARIN-PPML <arin-ppml-bounces@arin.net> on behalf of John Santos <john@egh.com><br>
<b>Date: </b>Tuesday, March 18, 2025 at 4:11</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"> </span><span style="font-size:12.0pt;color:black">PM<br>
<b>To: </b>arin-ppml@arin.net <arin-ppml@arin.net><br>
<b>Subject: </b>Re: [arin-ppml] Fwd: Revised - Draft Policy ARIN-2024-5: Rewrite of NRPM Section 4.4 Micro-Allocation<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">And it bounced again. Said "Delivery to the following email address failed
<br>
permanently:<br>
<br>
<br>
<br>
Please try another method to reach your intended recipient.<br>
"<br>
<br>
Notice that list of failed addresses is NOTHING. Maybe I'm just getting old but <br>
every day, I encounter terrible undebugged software, things the used to work and <br>
now don't because someone "fixed something" that wasn't broken in the first <br>
place. I've never had a problem replying on the ARIN list, but, not having <br>
changed ANYTHING except my email client, which updates itself several times a <br>
month, it either doesn't work any longer, or ARIN's list server doesn't work any <br>
longer.<br>
<br>
<br>
<br>
On 3/18/2025 4:04 PM, John Santos wrote:<br>
> I got a mysterious bounce. I don't know if my comment went to the list or not,
<br>
> so I'm sending it again. Sorry if it's a duplicate.<br>
> <br>
> <br>
> <br>
> -------- Forwarded Message --------<br>
> Subject: Re: [arin-ppml] Revised - Draft Policy ARIN-2024-5: Rewrite of NRPM <br>
> Section 4.4 Micro-Allocation<br>
> Date: Tue, 18 Mar 2025 15:58:48 -0400<br>
> From: John Santos <john@egh.com><br>
> Reply-To: john@egh.com<br>
> Organization: Evans Griffiths & Hart, Inc.<br>
> To: arin-ppml@arin.net<br>
> <br>
> Maybe I'm just being persnickety, but is "Use of this policy for CII is <br>
> voluntary." unambiguous? To me, it means a user can implement CII using any <br>
> addresses that are allocated to them, i.e. they are not required to apply for <br>
> and use 4.4 space for CII, *BUT* might someone argue that this clause means that
<br>
> if they have 4.4 space, or acquire it somehow, then using it for CII is <br>
> voluntary and they can use it for anything they want? Should we add an explicit
<br>
> provision that 4.4 space may *ONLY* be used for CII?<br>
> <br>
> Also, does section 4.4.2 create a chicken and egg problem: A TLD operator must <br>
> be "a currently active zone operator" to apply for 4.4 space, but they can't <br>
> become an active zone operator until they have acquired the IP addresses to do <br>
> so? It would complicate the situation if we added "or plans to become one <br>
> within <reasonable time period>", and another sentence that the allocation would
<br>
> be subject to revocation if they did not do so.<br>
> <br>
> Or is this just too pedantic to worry about?<br>
> <br>
> <br>
> On 3/18/2025 2:44 PM, ARIN wrote:<br>
>> The following Draft Policy has been revised:<br>
>> *ARIN-2024-5: Rewrite of NRPM Section 4.4 Micro-Allocation<br>
>> Revised text is below and can be found at:<br>
>> <a href="https://www.arin.net/participate/policy/drafts/2024_5/">https://www.arin.net/participate/policy/drafts/2024_5/</a><br>
>> You are encouraged to discuss all Draft Policies on PPML. The AC will evaluate
<br>
>> the discussion to assess the conformance of this Draft Policy with ARIN's <br>
>> Principles of Internet number resource policy as stated in the Policy <br>
>> Development Process (PDP). Specifically, these principles are:<br>
>> * Enabling Fair and Impartial Number Resource Administration<br>
>> * Technically Sound<br>
>> * Supported by the Community<br>
>> The PDP can be found at:<br>
>> <a href="https://www.arin.net/participate/policy/pdp/">https://www.arin.net/participate/policy/pdp/</a><br>
>> Draft Policies and Proposals under discussion can be found at:<br>
>> <a href="https://www.arin.net/participate/policy/drafts/">https://www.arin.net/participate/policy/drafts/</a><br>
>> Regards,<br>
>> Eddie Diego<br>
>> Policy Analyst<br>
>> American Registry for Internet Numbers (ARIN)<br>
>><br>
>><br>
>> Draft Policy ARIN-2024-5: Rewrite of NRPM Section 4.4 Micro-Allocation<br>
>><br>
>> Problem Statement:<br>
>><br>
>> The current NRPM Section 4.4 language hasn’t aged well. As the ARIN 53 policy <br>
>> experience report demonstrated, 4.4 has also become difficult to implement by <br>
>> ARIN staff. The growth and use of Internet Exchanges have also changed. The <br>
>> overhaul seeks to improve technical soundness, respect the privilege of a <br>
>> dedicated pool and to more closely observe conservation principles using <br>
>> clear, minimum and enforceable requirements and underscoring the value of <br>
>> routability of allocated prefixes as required.<br>
>><br>
>> Policy Statement:<br>
>><br>
>> 4.4 Critical Internet Infrastructure (CII) Allocations<br>
>><br>
>> ARIN will reserve a /15 equivalent of IPv4 address space for Critical Internet
<br>
>> Infrastructure (CII) within the ARIN RIR service area. Allocations from this <br>
>> pool will be no smaller than a /24. Sparse allocation will be used whenever <br>
>> practical. CII includes Internet Exchanges, IANA-authorized root servers, TLD <br>
>> operators that offer domain-level DNS services to outside parties, ARIN, and <br>
>> IANA.<br>
>><br>
>> Previous allocations under this policy must continue to meet the justification
<br>
>> requirements of this policy. Use of this policy for CII is voluntary. ARIN <br>
>> will publish all 4.4 allocated addresses for research purposes.<br>
>><br>
>> 4.4.1 Internet Exchange Allocations<br>
>><br>
>> Internet Exchange operators must justify their need by providing a minimum of <br>
>> three initial participants not under common control connected to a shared, <br>
>> physical switching fabric to be used for the purpose of the exchange of data <br>
>> destined for and between the respective networks. This justification must <br>
>> include participant names, ASNs and contact information for each named <br>
>> participant. The applicant’s Internet Exchange affiliated ASNs are not <br>
>> eligible to be included in meeting the participant requirement.<br>
>><br>
>> Allocated addresses may be publicly reachable at the operator’s discretion, <br>
>> but must be assigned only to resources required to operate the IXP.<br>
>><br>
>> 4.4.2 TLD Allocations<br>
>><br>
>> TLD operators will provide justification of their need and certification of <br>
>> their status as currently active zone operators.<br>
>><br>
>> 4.4.3 Additional Requests<br>
>><br>
>> A recipient may request up to a 24-month supply of IPv4 resources under this <br>
>> section. Requests for additional resources under this section will be <br>
>> evaluated using Section 4.2.4.1’s usage requirements.<br>
>><br>
>> Timetable for Implementation: Immediate<br>
>><br>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> ARIN-PPML<br>
>> You are receiving this message because you are subscribed to<br>
>> the ARIN Public Policy Mailing List (ARIN-PPML@arin.net).<br>
>> Unsubscribe or manage your mailing list subscription at:<br>
>> <a href="https://lists.arin.net/mailman/listinfo/arin-ppml">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
>> Please contact info@arin.net if you experience any issues.<br>
> <br>
<br>
-- <br>
John Santos<br>
Evans Griffiths & Hart, Inc.<br>
781-861-0670 ext 539<br>
<br>
_______________________________________________<br>
ARIN-PPML<br>
You are receiving this message because you are subscribed to<br>
the ARIN Public Policy Mailing List (ARIN-PPML@arin.net).<br>
Unsubscribe or manage your mailing list subscription at:<br>
<a href="https://lists.arin.net/mailman/listinfo/arin-ppml">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
Please contact info@arin.net if you experience any issues.<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>