<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Bill,</div>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Suggest you read the staff assessment again as well as review the training mentioned below. Again, customers provide their own default for what they assign to their customers or end users. ARIN recommends the industry standard of /48 but it can be /56 or /64
if they wish. In fact, we have some customers that due to the nature of their business use a mixture of the 3 different sizes. This information is included in all the information provided to our customers. Most of ARIN’s customers look to ARIN to provide the
necessary information and training to come up with the proper block size to request. ARIN works extensively to help our customers with their requests if they do not have the experience and knowledge to figure it out in-house. </div>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Thanks,</div>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
John S. </div>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div id="mail-editor-reference-message-container">
<div class="ms-outlook-mobile-reference-message skipProofing">
<meta name="Generator" content="Microsoft Exchange Server">
</div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="text-align: left; padding: 3pt 0in 0in; border-width: 1pt medium medium; border-style: solid none none; border-color: rgb(181, 196, 223) currentcolor currentcolor; font-family: Aptos; font-size: 12pt; color: black;">
<b>From: </b>William Herrin <bill@herrin.us><br>
<b>Date: </b>Monday, February 16, 2026 at 7:30 PM<br>
<b>To: </b>John Sweeting <jsweeting@arin.net><br>
<b>Cc: </b>DeLong Owen <owen@delong.com>, arin-ppml@arin.net <arin-ppml@arin.net><br>
<b>Subject: </b>Re: [arin-ppml] Draft Policy ARIN-2025-6: Fix formula in 6.5.2.1c<br>
<br>
</div>
<div class="PlainText" style="font-size: 11pt;">On Tue, Feb 17, 2026 at 2:31 AM John Sweeting <jsweeting@arin.net> wrote:<br>
> This is not true. ARIN follows policy as mandated and allows<br>
> customers to select their default size for downstream reassignment.<br>
> This is very clear in “ARIN’s IPv6 Address Planning Basics” located<br>
> in the ARIN Academy. ARIN does encourage /48 as industry standard<br>
> but the customer may determine their own default in accordance<br>
> with policy and ARIN training material.<br>
<br>
Hi John,<br>
<br>
With due respect, I was told across multiple inquiries that ARIN<br>
presumes the PAU to be /48 for the purposes of policy section 6.5.2.1,<br>
the staff assessment was clear about ARIN's disuse of the second<br>
paragraph of NRPM section 6.5.2.1c where the requirement appears, I<br>
reported ARIN's disuse of that policy component at the October meeting<br>
without contradiction, and I reported PAU issue even more explicitly<br>
to the AC again without contradiction.<br>
<br>
Are you now telling me that all of that was in error, that ARIN does<br>
in fact inquire into the ISP's intended downstream assignment size and<br>
that ARIN does in fact scale the ISP's entitlement based on their<br>
response in the manner Owen correctly describes the policy to require?<br>
That contrary to prior report, ARIN _does_ implement the second<br>
paragraph of section 6.5.2.1c?<br>
<br>
If not, I respectfully submit that denial is unseemly and the time has<br>
come to find out what the community wants done about the<br>
misimplementation. They're the ones who are supposed to be in the<br>
number policy driver's seat. Let's make sure they are.<br>
<br>
Regards,<br>
Bill Herrin<br>
</div>
</div>
</body>
</html>