<html xmlns:v="urn:schemas-microsoft-com:vml" 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=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Segoe UI";
panose-1:2 11 5 2 4 2 4 2 2 3;}
@font-face
{font-family:"Open Sans";
panose-1:2 11 6 6 3 5 4 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Thanks John! I’ve been working on this with our attorneys for almost a year. I did send over the revisions and it will be good to see what they say. But I’m not sure it will be enough to reduce the perceived risk. Has ARIN considered separating
the fee structure and service goals from the drive to get everyone under an RSA? <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="600" style="width:6.25in;background:white;border-collapse:collapse">
<tbody>
<tr style="height:61.5pt">
<td width="310" style="width:232.5pt;padding:0in 0in 0in 0in;height:61.5pt">
<p class="MsoNormal"><span style="font-family:"Segoe UI",sans-serif;color:#0058A4">Tom Krenn<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-top:1.5pt"><span style="font-size:10.0pt;font-family:"Segoe UI",sans-serif;color:#6E6D6D">Network Architect<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-top:1.5pt"><span style="font-size:10.0pt;font-family:"Segoe UI",sans-serif;color:#6E6D6D">Enterprise Architecture - Information Technology<o:p></o:p></span></p>
</td>
</tr>
<tr style="height:38.25pt">
<td width="40" style="width:30.0pt;padding:18.75pt 0in 0in 0in;height:38.25pt">
<p class="MsoNormal"><span style="font-family:"Open Sans",sans-serif;color:black"><img width="40" height="51" style="width:.4166in;height:.5312in" id="Picture_x0020_1" src="cid:image001.png@01D8C9AA.18A85D20" alt="Hennepin County logo"></span><span style="font-family:"Open Sans",sans-serif"><o:p></o:p></span></p>
</td>
</tr>
<tr>
<td style="padding:18.75pt 0in 0in 0in"></td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> John Curran <jcurran@arin.net> <br>
<b>Sent:</b> Thursday, September 15, 2022 8:42 PM<br>
<b>To:</b> Tom Krenn <Tom.Krenn@hennepin.us><br>
<b>Cc:</b> Rubens Kuhl <rubensk@gmail.com>; North American Network Operators' Group <nanog@nanog.org><br>
<b>Subject:</b> Re: [External] Normal ARIN registration service fees for LRSA entrants after 31 Dec 2023 (was: Fwd: [arin-announce] Availability of the Legacy Fee Cap for New LRSA Entrants Ending as of 31 December 2023)<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">On 15 Sep 2022, at 9:29 PM, Tom Krenn via NANOG <<a href="mailto:nanog@nanog.org">nanog@nanog.org</a>> wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">An interesting idea, but like others have said I think the ship may have sailed for RPKI. Really I have no problem with the ARIN fees. They are a drop in the bucket for most network budgets. In fact as a legacy holder I would gladly pay
the same as an RIR-allocated resource holder if it would allow the use of the more advanced services. It's the ownership question and RSA/LRSA language that throws the wrench in everything.<br>
<br>
As John said " I will note that ARIN’s approach is the result of aiming for a different target – that more specifically being the lowest possible fees administered on an equitable basis for _all resource holders_ in the region.". If that's the goal, give us
the option to pay the same without all the legal mess around signing the RSA/LRSA. I'm sure that's what has been holding some organizations back for the couple decades mentioned. It has been the major stumbling point for a few of the ones I've been part of
over the years.<o:p></o:p></p>
</div>
</div>
</blockquote>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<div>
<p class="MsoNormal">Tom -<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Over the years, ARIN has made several revisions to the RSA/LRSA to make it both clearer and more customer friendly, <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">and the most recent version (announced earlier this week - <<a href="https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.arin.net%2Fannouncements%2F20220912%2F&data=05%7C01%7CTom.Krenn%40hennepin.us%7C970ff4a0fade4b7b0d3308da9784b663%7C8aefdf9f878046bf8fb74c924653a8be%7C0%7C0%7C637988893501824755%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=nbnXoX6%2BXkkwKC6sbxokXipFpmdFq8839TvtK0F4SNY%3D&reserved=0">https://www.arin.net/announcements/20220912/</a>>)
strikes <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">much of the language in section 7 that some legal teams had objection to… It is likely not everything you want, but I <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">would suggest taking a fresh look at it as it was substantially reduced specifically to address the most cited customer <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">concern regarding the legal obligations in the prior version of the RSA/LRSA. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">FYI,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">/John<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal">John Curran<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">President and CEO<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">American Registry for Internet Numbers<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<br>
<br>
<b>Disclaimer:</b> If you are not the intended recipient of this message, please immediately notify the sender of the transmission error and then promptly permanently delete this message from your computer system.
</body>
</html>