<div dir="ltr">First, the problem statement is a little misleading; there is no section 11.10, you are adding a section 11.10. Experimental allocations should not be strictly limited to the ARIN region. Organizations receiving an experimental allocation need to demonstrate a nexus to the ARIN region as specified in section 9. Furthermore, I hope experiments include participation globally and not solely from within the ARIN region. The new language confuses the situation more than clarifying it.<div><br></div><div>Additionally, allocations from 4.4 and 6.10 are sufficiently covered by the requirements of section 9 as well. For example, if a critical infrastructure provider meets the requirements of section 9 and wants to use an allocation solely outside of the ARIN region, that should be possible. That is the intent of section 9.</div><div><br></div><div>However, Section 4.10 probably needs something. But the current language is unacceptably restrictive, as it strictly requires use within the ARIN region. The requirement should be that the IPv4 allocation from 4.10 must be in support of an ARIN IPv6 allocation or reassignment made within the ARIN database. If the IPv6 allocation or reassignment is used outside of the ARIN region in compliance with section 9, the 4.10 allocation should be equally capable of being used outside the ARIN region. However, 4.10 allocations should not be made based on IPv6 allocation or reassignment from another RIR.</div><div><br></div><div>Thanks</div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Mon, Jul 14, 2025 at 9:55 AM Pellak, Kaitlyn via ARIN-PPML <<a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="msg791858415885129898">
<div lang="EN-US" style="overflow-wrap: break-word;">
<div class="m_791858415885129898WordSection1">
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif">Hi Martin,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif">Appreciate your feedback. Just to be clear, in your view there are no revisions to the policy language that would make this proposal more palatable?
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif">I want to make sure this isn’t a case where we could wordsmith the policy to prevent conflicts with section 9, or be more specific in the language that applies to each section.
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif">Thanks,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif">Kaitlyn<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif"><u></u> <u></u></span></p>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:black">Kaitlyn Pellak<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:black">Amazon – Technical Business Developer II<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif"><a href="mailto:kaitjean@amazon.com" title="mailto:martesmm@amazon.com" target="_blank"><span style="color:rgb(149,79,114)">kaitjean@amazon.com</span></a><span style="color:black"><u></u><u></u></span></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:black">301.921.5566<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:black"> <u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:black"><img border="0" width="68" height="40" style="width: 0.7083in; height: 0.4166in;" id="m_791858415885129898Picture_x0020_1" src="cid:ii_19809a71c9a4cff311" alt="/Users/tinam/Library/Containers/com.microsoft.Outlook/Data/Library/Caches/Signatures/signature_1323502979"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif"><u></u> <u></u></span></p>
</div>
</div>
</div>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif"><u></u> <u></u></span></p>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(181,196,223);padding:3pt 0in 0in">
<p class="MsoNormal"><b><span style="font-family:Calibri,sans-serif;color:black">From:
</span></b><span style="font-family:Calibri,sans-serif;color:black">ARIN-PPML <<a href="mailto:arin-ppml-bounces@arin.net" target="_blank">arin-ppml-bounces@arin.net</a>> on behalf of Martin Hannigan <<a href="mailto:hannigan@gmail.com" target="_blank">hannigan@gmail.com</a>><br>
<b>Date: </b>Sunday, July 13, 2025 at 9:16 PM<br>
<b>To: </b>ARIN <<a href="mailto:info@arin.net" target="_blank">info@arin.net</a>><br>
<b>Cc: </b>"<a href="mailto:arin-ppml@arin.net" target="_blank">arin-ppml@arin.net</a>" <<a href="mailto:arin-ppml@arin.net" target="_blank">arin-ppml@arin.net</a>><br>
<b>Subject: </b>RE: [EXTERNAL] [arin-ppml] Draft Policy ARIN-2025-5: Clarify justification requirements for 4.4, 4.10, 6.10, and 11.10 IP addresses<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<table border="0" cellspacing="0" cellpadding="0" style="border-collapse:collapse">
<tbody>
<tr style="height:15.25pt">
<td width="1123" valign="top" style="width:842.35pt;border:1.5pt solid rgb(237,125,49);padding:0in 5.4pt;height:15.25pt">
<p><strong><span style="font-family:Aptos,sans-serif;color:black;background:rgb(255,255,153)">CAUTION</span></strong><span style="color:black;background:rgb(255,255,153)">: 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.</span><u></u><u></u></p>
</td>
</tr>
</tbody>
</table>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">- not in favor<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Poor policy writing to stamp multiple sections with boilerplate and set up future conflict with Section 9 - and bloat the NRPM additionally.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Warm regards,<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">-M><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal">On Tue, Jul 1, 2025 at 14:35 ARIN <<a href="mailto:info@arin.net" target="_blank">info@arin.net</a>> wrote:<u></u><u></u></p>
</div>
<blockquote style="border-top:none;border-right:none;border-bottom:none;border-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal">On 26 June 2025, the ARIN Advisory Council (AC) accepted “ARIN-prop-344: Clarify justification requirements for 4.4, 4.10, 6.10, and 11.10 IP addresses” as Draft Policy.
<br>
<br>
Draft Policy ARIN-2025-5 is below and can be found at:<br>
<br>
<a href="https://www.arin.net/participate/policy/drafts/2025_5" target="_blank">https://www.arin.net/participate/policy/drafts/2025_5</a><br>
<br>
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:<br>
<br>
* Enabling Fair and Impartial Number Resource Administration<br>
* Technically Sound<br>
* Supported by the Community<br>
<br>
The PDP can be found at:<br>
<br>
<a href="https://www.arin.net/participate/policy/pdp/" target="_blank">https://www.arin.net/participate/policy/pdp/</a><br>
<br>
Draft Policies and Proposals under discussion can be found at: <a href="https://www.arin.net/participate/policy/drafts/" target="_blank">
https://www.arin.net/participate/policy/drafts/</a><br>
<br>
Regards,<br>
<br>
Eddie Diego<br>
Policy Analyst<br>
American Registry for Internet Numbers (ARIN)<br>
<br>
<br>
<br>
Draft Policy ARIN-2025-5: Clarify justification requirements for 4.4, 4.10, 6.10, and 11.10 IP addresses<br>
<br>
Problem Statement: <br>
<br>
The NRPM text is ambiguous about whether out of region use cases can justify requests for IP addresses allocated under 4.4, 4.10, 6.10, and 11.10, as well as whether these IP Addresses impact justification requirements for normal IP addresses. This change codifies
ARIN Staff's current practices to remove this ambiguity, removing a source of confusion for resource requesters.<br>
<br>
Policy statement:<br>
<br>
Add the following to 4.4:<br>
Justifications for resources under this section must be for use within the ARIN service region. Resources issued under this section may also be used out of<br>
region if that use is consistent with the in-region justification (for example, global Anycast). Resources issued under this section have no impact on the justification or utilization requirements for requests under any other section.<br>
<br>
Add the following to 4.10:<br>
Justifications for resources under this section must be for use within the ARIN service region. Resources issued under this section may also be used out of region if that use is consistent with the in-region justification (for example, global Anycast). Resources
issued under this section have no impact on the justification or utilization requirements for requests under any other section.<br>
<br>
Add the following to 6.10:<br>
Justifications for resources under this section must be for use within the ARIN service region. Resources issued under this section may also be used out of region if that use is consistent with the in-region justification (for example, global Anycast). Resources
issued under this section have no impact on the justification or utilization requirements for requests under any other section.<br>
<br>
Add Section 11.10:<br>
Justifications for resources under this section must be for use within the ARIN service region. Resources issued under this section may also be used out of region if that use is consistent with the in-region justification (for example, global Anycast). Resources
issued under this section have no impact on the justification or utilization requirements for requests under any other section.<br>
<br>
Time Table 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 (<a href="mailto:ARIN-PPML@arin.net" target="_blank">ARIN-PPML@arin.net</a>).<br>
Unsubscribe or manage your mailing list subscription at:<br>
<a href="https://lists.arin.net/mailman/listinfo/arin-ppml" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you experience any issues.<u></u><u></u></p>
</blockquote>
</div>
</div>
</div>
</div>
</div>
_______________________________________________<br>
ARIN-PPML<br>
You are receiving this message because you are subscribed to<br>
the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" target="_blank">ARIN-PPML@arin.net</a>).<br>
Unsubscribe or manage your mailing list subscription at:<br>
<a href="https://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you experience any issues.<br>
</div></blockquote></div><div><br clear="all"></div><div><br></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature">===============================================<br>David Farmer <a href="mailto:Email%3Afarmer@umn.edu" target="_blank">Email:farmer@umn.edu</a><br>Networking & Telecommunication Services<br>Office of Information Technology<br>University of Minnesota <br>2218 University Ave SE Phone: 612-626-0815<br>Minneapolis, MN 55414-3029 Cell: 612-812-9952<br>=============================================== </div>