<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=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:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
.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">
<div class="WordSection1">
<p class="MsoNormal">I disagree on the usage of "fair". The policy 2019-16 may have been applied fairly based on the verbiage stated within. However, having entities' requests approved under the previous rules and policies, and allowing these entities/requests
onto the wait list in accordance with those rules, then subsequently removing them from the wait list is not fair. Those requests went through the process and were allowed to proceed, and therefore should be grandfathered and remain on the wait list until
such time that the request can be fulfilled. Moving forward, it makes sense to not approve requests of this nature and apply the limitations put forward in 2019-16, but it is certainly unfair to apply those standards to requests that were already approved
under the previous standards. Please strongly consider approving policy ARIN-2020-2<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="mso-line-height-rule:exactly;-webkit-text-size-adjust:100%;"><table cellpadding="0" cellspacing="0" border="0" style="width:100%;"><tr style="font-size:0;"><td align="left" style="vertical-align:top;"><table cellpadding="0" cellspacing="0" border="0" style="font-size:0;color:#0066FF;font-style:normal;font-weight:400;white-space:nowrap;"><tr style="font-size:12px;"><td align="left" style="vertical-align:bottom;font-size:14.67px;font-family:Arial;font-weight:700;">Jason<span style="font-family:remialcxesans;font-size:1px;color:#FFFFFF;line-height:1px;"></span></td><td align="left" style="vertical-align:top;color:#000001;font-family:Arial;"> <br /></td><td align="left" style="vertical-align:bottom;font-size:14.67px;font-family:Arial;font-weight:700;">Brandt</td><td align="left" style="vertical-align:top;color:#000001;font-family:Arial;"> <br /></td><td align="left" style="vertical-align:bottom;color:#666666;font-family:Arial;">Senior Systems Engineer</td></tr></table></td></tr><tr style="font-size:0;"><td align="left" style="vertical-align:top;"><table cellpadding="0" cellspacing="0" border="0" style="font-size:0;color:#666666;font-style:normal;font-weight:400;white-space:nowrap;"><tr style="font-size:12px;"><td align="left" style="vertical-align:bottom;font-family:Arial;font-weight:700;">Pearl Companies</td><td align="left" style="vertical-align:bottom;color:#0066FF;font-family:Arial;"> | </td><td align="left" style="vertical-align:bottom;font-family:Arial;">1200 E Glen Ave</td><td align="left" style="vertical-align:top;color:#000001;font-family:Arial;"> </td><td align="left" style="vertical-align:bottom;font-family:Arial;">Peoria Heights</td><td align="left" style="vertical-align:bottom;font-family:Arial;">, </td><td align="left" style="vertical-align:bottom;font-family:Arial;">IL</td><td align="left" style="vertical-align:top;color:#000001;font-family:Arial;"> </td><td align="left" style="vertical-align:bottom;font-family:Arial;">61616</td></tr></table></td></tr><tr style="font-size:0;"><td align="left" style="vertical-align:top;"><table cellpadding="0" cellspacing="0" border="0" style="font-size:0;color:#000001;font-style:normal;font-weight:400;white-space:nowrap;"><tr style="font-size:12px;"><td align="left" style="vertical-align:top;color:#0066FF;font-family:Arial;">P: </td><td align="left" style="vertical-align:top;font-family:Arial;"><a href="tel:309.679.0184" target="_blank" id="LPlnk689713" style="text-decoration:none;color:#666666;"><strong style="font-weight:400;">309.679.0184</strong></a></td><td align="left" style="vertical-align:top;font-family:Arial;"> </td><td align="left" style="vertical-align:top;color:#0066FF;font-family:Arial;">F: </td><td align="left" style="vertical-align:top;font-family:Arial;"><a href="fax:309.688.5444" target="_blank" id="LPlnk689713" style="text-decoration:none;color:#666666;"><strong style="font-weight:400;">309.688.5444</strong></a></td><td align="left" style="vertical-align:top;font-family:Arial;"> </td><td align="left" style="vertical-align:top;color:#0066FF;font-family:Arial;">E: </td><td align="left" style="vertical-align:top;font-family:Arial;"><a href="mailto:jason.brandt@pearlcompanies.com" target="_blank" id="LPlnk689713" style="text-decoration:none;color:#666666;"><strong style="font-weight:400;">jason.brandt@pearlcompanies.com</strong></a></td></tr></table></td></tr><tr style="color:#0066FF;font-size:10px;font-style:normal;font-weight:400;white-space:nowrap;"><td align="left" style="vertical-align:top;font-family:Arial;"><a href="http://www.pearlcompanies.com/" target="_blank" id="LPlnk689713" style="text-decoration:none;color:#0066FF;"><strong style="font-weight:400;">www.pearlcompanies.com | I</strong></a>nsurance ‑ Technology ‑ Automotive<br /></td></tr><tr style="font-size:0;"><td align="left" style="vertical-align:top;"><table cellpadding="0" cellspacing="0" border="0" style="font-size:0;color:#000001;font-style:normal;font-weight:400;white-space:nowrap;"><tr style="font-size:12px;"><td align="left" style="padding:6px;vertical-align:top;font-family:Arial;"><br /></td></tr></table></td></tr><tr style="font-size:0;"><td align="left" style="vertical-align:top;"><table cellpadding="0" cellspacing="0" border="0" style="white-space:normal;color:#0066FF;font-size:12px;font-family:Arial;font-weight:400;font-style:normal;text-align:justify;width:100%;"><tr style="font-size:9.33px;"><td style="font-family:Arial;">PEARL COMPANIES CONFIDENTIALITY: This communication, including attachments, is for exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, any use, copying, disclosure, or distribution or the taking of any action in reliance upon this information is strictly prohibited. If you are not the intended recipient, please notify the sender immediately and delete this communication and destroy all copies [v1.0.002].<br /></td></tr></table></td></tr></table></div><div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> ARIN-PPML <arin-ppml-bounces@arin.net> <b>On Behalf Of
</b>David Farmer via ARIN-PPML<br>
<b>Sent:</b> Monday, July 20, 2020 09:29<br>
<b>To:</b> Tom Pruitt <tpruitt@stratusnet.com><br>
<b>Cc:</b> arin-ppml@arin.net<br>
<b>Subject:</b> Re: [arin-ppml] Draft Policy ARIN-2020-2: Grandfathering of OrganizIt reaations Removed from Waitlist by Implementation of ARIN-2019-16<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" align="left">
<tbody>
<tr>
<td style="background:#BBA555;padding:5.25pt 5.5pt 5.25pt 1.5pt"></td>
<td width="100%" style="width:100.0%;background:#FFE599;padding:5.25pt 3.75pt 5.25pt 11.25pt;word-wrap:break-word">
<div>
<p style="mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<b><span style="font-family:"Arial",sans-serif;color:#212121">CAUTION:</span></b><span style="font-family:"Arial",sans-serif;color:#212121"> This email originated from outside the organization. Do not click links or open attachments unless you recognize the
sender and know the content is safe. </span><o:p></o:p></p>
</div>
</td>
</tr>
</tbody>
</table>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">I have to disagree, the implementation of 2019-16 was fair and impartial. There was a general criterion that was applied, it wasn't overly specific, such that it only targeted a single or small group of specific
organizations. Yes, the selection of /20 was mostly arbitrary, but any number picked would have been mostly arbitrary. The /18 that this policy proposes is mostly arbitrary as well. The specific numbers are a judgment call, both in 2019-16 and this policy. Nevertheless,
innocent organizations were impacted by the implementation of 2019-16, and that is regrettable, unfortunate, and frankly, it sucks, but that doesn't me it was unfair.
<o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Further, the alternative implementation, that you propose would have been unfair because the organizations with a /20 or less of total holdings, but requesting more than a /22, would qualify under the policy
in 2019-16 if they simply reduced their request. Therefore, requiring them to be removed from the waiting list and to reapply would have been unnecessarily bureaucratic and petty, with the only effect being that they lost their place on the waiting list. Allowing
these entities to reduce their request seems an eminently fair way do deal with that situation.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Personally, I like and support the concept of mitigating at least some of the impact on innocent organizations by allowing those with up to and including a /18 of total holdings back on the list for up to a /22. I'll note that this specific
idea didn't come up during the discussions leading up to 2019-16 or immediately following the implementation of it. However, while I support mitigating the effects of 2019-16 on several innocent organizations, I most strenuously object to referring to the
implementation of 2019-16 as unfair. The implementation of 2019-16 was both fair and impartial, even though the impact on some organizations was undesirable, it was nevertheless fair.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Thanks.<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Fri, Jul 17, 2020 at 3:34 PM Tom Pruitt <<a href="mailto:tpruitt@stratusnet.com">tpruitt@stratusnet.com</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal">The organizations this draft policy would affect had qualified for space before 2019-16 (limiting space to a /20 and limiting a max request to a /22) was implemented. The implementation of the policy removed the organizations that had
over a /20, but allowed organizations with less than that who wanted more than a /22 to adjust their request and remain on the list. If all organizations who didn't fit the new criteria with their existing requests were removed then it would have been applied
fairly and equal, but that isn't what happened.<br>
<br>
This proposal actually equalizes the implementation of 2019-16.<br>
<br>
<br>
Yes the problem is the lack of IPv6 deployment, I don't think anyone can argue that.<br>
<br>
Thanks,<br>
Tom Pruitt <br>
Network Engineer<br>
Stratus Networks<br>
<br>
This e-mail, and any files transmitted with it are the property of Stratus Networks, Inc. and/or its affiliates, are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not one of the named
recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the sender at 309-408-8704 and delete this message immediately from your computer. Any other use, retention, dissemination, forwarding, printing, or
copying of this e-mail is strictly prohibited<br>
<br>
-----Original Message-----<br>
From: ARIN-PPML <<a href="mailto:arin-ppml-bounces@arin.net" target="_blank">arin-ppml-bounces@arin.net</a>> On Behalf Of Fernando Frediani<br>
Sent: Friday, July 17, 2020 11:01 AM<br>
To: <a href="mailto:arin-ppml@arin.net" target="_blank">arin-ppml@arin.net</a><br>
Subject: Re: [arin-ppml] Draft Policy ARIN-2020-2: Grandfathering of Organizations Removed from Waitlist by Implementation of ARIN-2019-16<br>
<br>
What is the justification to give organization who already have some reasonable space to work with, more space in current times ?<br>
<br>
Everybody is suffering from the same problem of IPv4 scarcity and that affects all equally. If we have already a policy that limits on /20 it is for a reason, a fair reason by the way. So why are we going to bend it in this case in the other direction ?<br>
I see this type of proposal privileging just a few rather than been equalized to all others.<br>
<br>
Therefore I keep opposed to it.<br>
<br>
Fernando<br>
<br>
On 17/07/2020 12:24, Steven Ryerse via ARIN-PPML wrote:<br>
> +1<br>
><br>
><br>
> Steven Ryerse<br>
> President<br>
><br>
> <a href="mailto:sryerse@eclipse-networks.com" target="_blank">sryerse@eclipse-networks.com</a> | C: 770.656.1460<br>
> 100 Ashford Center North | Suite 110 | Atlanta, Georgia 30338<br>
><br>
> <br>
><br>
><br>
><br>
> -----Original Message-----<br>
> From: ARIN-PPML <<a href="mailto:arin-ppml-bounces@arin.net" target="_blank">arin-ppml-bounces@arin.net</a>> On Behalf Of Mike Burns<br>
> Sent: Friday, July 17, 2020 10:59 AM<br>
> To: <a href="mailto:hostmaster@uneedus.com" target="_blank">hostmaster@uneedus.com</a>;
<a href="mailto:arin-ppml@arin.net" target="_blank">arin-ppml@arin.net</a><br>
> Subject: Re: [arin-ppml] Draft Policy ARIN-2020-2: Grandfathering of <br>
> Organizations Removed from Waitlist by Implementation of ARIN-2019-16<br>
><br>
> I support the policy as written and I do not believe we should prioritize small holders over large holders.<br>
> Large holders pay higher fees but I don't see the rationale behind favoring small holders on the wait list.<br>
> All holders should be on equal footing, we never had a new-entrant reserve at ARIN and I think if that is something we want to do, it should be discussed openly and not inserted through the back door of waitlist policy.<br>
><br>
> Regards,<br>
> Mike<br>
><br>
><br>
><br>
> -----Original Message-----<br>
> From: ARIN-PPML <<a href="mailto:arin-ppml-bounces@arin.net" target="_blank">arin-ppml-bounces@arin.net</a>> On Behalf Of
<br>
> <a href="mailto:hostmaster@uneedus.com" target="_blank">hostmaster@uneedus.com</a><br>
> Sent: Thursday, July 16, 2020 7:59 AM<br>
> To: <a href="mailto:arin-ppml@arin.net" target="_blank">arin-ppml@arin.net</a><br>
> Subject: Re: [arin-ppml] Draft Policy ARIN-2020-2: Grandfathering of <br>
> Organizations Removed from Waitlist by Implementation of ARIN-2019-16<br>
><br>
> I am also against this proposal.<br>
><br>
> If we allow holders of larger blocks back onto the list, we take away blocks that should go to smaller holders.<br>
><br>
> The waiting list is NOT a lottery to be "won", and I think the policy should not change.<br>
><br>
> Albert Erdmann<br>
> Network Administrator<br>
> Paradise On Line Inc.<br>
><br>
><br>
> On Wed, 15 Jul 2020, Andrew Dul wrote:<br>
><br>
>> I do not support the reintroduction of organizations onto the <br>
>> wait-list who were removed due to having existing address holdings <br>
>> larger than a /20. Being on the wait-list was never a guarantee that <br>
>> you would receive space. The AC had to balance the various elements <br>
>> of<br>
> block size and organizations who would be eligible to receive space under the updated policy and we were aware that the rules as implemented would prevent some organizations on the wait-list from receiving blocks going forward.<br>
>> Speaking only for myself, not the AC<br>
>><br>
>> Andrew<br>
>><br>
>> On 6/19/2020 11:25 AM, Alyssa Moore wrote:<br>
>> Hi folks,<br>
>><br>
>> There was some great discussion of this policy proposal at ARIN45.<br>
> We hear a wide range of views including:<br>
>> 1. Don't grandfather organizations. The new waitlist policy <br>
>> is<br>
> sound.<br>
>> 2. Organizations that were on the waitlist before 2019-16 <br>
>> should be<br>
> eligible for their original request size (even if it exceeds the new <br>
> limit<br>
>> of a /22).<br>
>> 3. Organizations that were on the waitlist before 2019-16 <br>
>> should<br>
> remain eligible if their holdings exceed a /20 OR a /18. The draft <br>
> policy<br>
>> under discussion specifies a /18 total holdings for<br>
> grandfathered orgs, while the current waitlist policy (2019-16) specifies a /20.<br>
>> 4. Organizations that were on the waitlist before 2019-16 <br>
>> should be<br>
> eligible regardless of their total holdings because that was not a<br>
>> restriction of the policy under which they originally <br>
>> qualified<br>
> for the waitlist.<br>
>> There was general support to continue finessing this draft. <br>
>> If you<br>
> have views on the above noted parameters, please make them known here.<br>
>> For reference:<br>
>><br>
>> Old waitlist policy<br>
>> 1. Requester specifies smallest block they'd be willing to accept, <br>
>> equal<br>
> to or larger than the applicable minimum size specified elsewhere in <br>
> ARIN<br>
>> policy.<br>
>> 2. Did not place a limit on the total existing IP address holdings <br>
>> of a<br>
> party eligible for the waitlist.<br>
>> 3. Made resources issued from the waitlist ineligible for transfer <br>
>> until after a period of 12 months. New Waitlist Policy 1. Limits the <br>
>> size of block ARIN can issue on the waitlist to a /22.<br>
>> 2. Places a limit on the total existing IP address holdings of a <br>
>> party<br>
> eligible for the waitlist at a /20 or less.<br>
>> 3. Makes resources issued from the waitlist ineligible for transfer <br>
>> until after a period of 60 months.<br>
>><br>
>> Best,<br>
>> Alyssa<br>
>><br>
>> On Thu, Mar 26, 2020 at 3:35 PM David Farmer <<a href="mailto:farmer@umn.edu" target="_blank">farmer@umn.edu</a>> wrote:<br>
>> I support this policy and believe the policy development <br>
>> process is<br>
> the proper place to handle this issue. However, this policy seems to<br>
>> be implementable as a one-time policy directive to ARIN Staff.<br>
>> Once<br>
> implemented, by putting the effected organizations back on the waiting<br>
>> list, it seems unnecessary to memorialized the text in the <br>
>> NRPM, it<br>
> would immediately become extraneous and potentially confusing to<br>
>> future readers of the NRPM.<br>
>> Therefore, I would like to recommend the Policy Statement not be <br>
>> added to the NRPM upon its implementation. I believe this to be <br>
>> consistent with<br>
> the intent of the policy. Otherwise, does ARIN Staff have procedural advice on how best to handle what seems like a one-time directive?<br>
>> Thanks<br>
>><br>
>> On Tue, Mar 24, 2020 at 12:21 PM ARIN <<a href="mailto:info@arin.net" target="_blank">info@arin.net</a>> wrote:<br>
>><br>
>> Draft Policy ARIN-2020-2: Grandfathering of Organizations <br>
>> Removed<br>
> from<br>
>> Waitlist by Implementation of ARIN-2019-16<br>
>><br>
>> Problem Statement:<br>
>><br>
>> The implementation of the ARIN-2019-16 Advisory Council<br>
> Recommendation<br>
>> Regarding NRPM 4.1.8: Unmet Requests caused some organizations to be<br>
>> removed from the waiting list that were approved under the old<br>
> policy?s<br>
>> eligibility criteria. These organizations should have been<br>
> grandfathered<br>
>> when the waitlist was reopened to allow them to receive an<br>
> allocation of<br>
>> IPv4 up to the new policy?s maximum size constraint of a /22.<br>
>><br>
>> Policy Statement: Update NRPM Section 4.1.8 as follows:<br>
>><br>
>> Add section 4.1.8.3 (temporary language in the NRPM to remain <br>
>> until<br>
> the<br>
>> policy objective is achieved)<br>
>><br>
>> Restoring organizations to the waitlist<br>
>><br>
>> ARIN will restore organizations that were removed from the <br>
>> waitlist<br>
> at<br>
>> the adoption of ARIN-2019-16 to their previous position if <br>
>> their<br>
> total<br>
>> holdings of IPv4 address space amounts to a /18 or less. The maximum<br>
>> size aggregate that a reinstated organization may qualify for <br>
>> is a<br>
> /22.<br>
>> All restored organizations extend their 2 year approval by <br>
>> [number<br>
> of<br>
>> months between July 2019 and implementation of new policy]. <br>
>> Any<br>
> requests<br>
>> met through a transfer will be considered fulfilled and <br>
>> removed from<br>
> the<br>
>> waiting list.<br>
>><br>
>> Comments:<br>
>><br>
>> Timetable for implementation: Immediate<br>
>><br>
>> Anything Else: While attending ARIN 44 and discussing this <br>
>> with<br>
> other<br>
>> community members the vast majority indicated that they agreed <br>
>> that<br>
> some<br>
>> organizations were treated unfairly. This proposal is a remedy.<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://linkprotect.cudasvc.com/url?a=https%3a%2f%2flists.arin.net%2fmailman%2flistinfo%2farin-ppml&c=E,1,itejYWK1neA4HwQI2654uD6T84LDr-jtyvegBUSRLaqI3i7cGDsXGSLO9kZFAeEqibHLpNp9IQUPINbrQtts-4t2a9DQNRIijWuYbVTpZdvZJI2YmIU7zQMg&typo=1" target="_blank">
https://linkprotect.cudasvc.com/url?a=https%3a%2f%2flists.arin.net%2fmailman%2flistinfo%2farin-ppml&c=E,1,itejYWK1neA4HwQI2654uD6T84LDr-jtyvegBUSRLaqI3i7cGDsXGSLO9kZFAeEqibHLpNp9IQUPINbrQtts-4t2a9DQNRIijWuYbVTpZdvZJI2YmIU7zQMg&typo=1</a><br>
>> Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you experience any issues.<br>
>><br>
>><br>
>><br>
>> --<br>
>> ===============================================<br>
>> David Farmer <a href="mailto:Email%3Afarmer@umn.edu" target="_blank">
Email:farmer@umn.edu</a> Networking & <br>
>> Telecommunication Services Office of Information Technology <br>
>> University of Minnesota<br>
>> 2218 University Ave SE Phone: 612-626-0815 Minneapolis, MN<br>
>> 55414-3029 Cell: 612-812-9952<br>
>> ===============================================<br>
>> _______________________________________________<br>
>> ARIN-PPML<br>
>> You are receiving this message because you are subscribed to the ARIN <br>
>> 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://linkprotect.cudasvc.com/url?a=https%3a%2f%2flists.arin.net%2f" target="_blank">
https://linkprotect.cudasvc.com/url?a=https%3a%2f%2flists.arin.net%2f</a><br>
>> m <br>
>> ailman%2flistinfo%2farin-ppml&c=E,1,pr8_yOATR6fbNAoiwPjuIuQtJCW1Nm7ql<br>
>> k <br>
>> KG7uppvzhqUtK33qz6GCTJCwHGGeKePdcEaJZZdUUw-RTujqMB1FJ2DG6HTd2r6GM5s4H<br>
>> y<br>
>> nLV4b0vI3AnQPQ,,&typo=1 Please contact <a href="mailto:info@arin.net" target="_blank">
info@arin.net</a> if you <br>
>> experience any issues.<br>
>><br>
>><br>
>> _______________________________________________<br>
>> ARIN-PPML<br>
>> You are receiving this message because you are subscribed to the ARIN <br>
>> 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://linkprotect.cudasvc.com/url?a=https%3a%2f%2flists.arin.net%2f" target="_blank">
https://linkprotect.cudasvc.com/url?a=https%3a%2f%2flists.arin.net%2f</a><br>
>> m <br>
>> ailman%2flistinfo%2farin-ppml&c=E,1,RsBXYYW2wGypb0Y4GbeHTbKFC2827Z3js<br>
>> p <br>
>> at1aezQl0yTqcY6d2pTdFdOAraqUCnPZ-okcO1-ObFc2thTsKxGhJ1eTCN_Cv8UpPoW80<br>
>> d<br>
>> 6gOeCMy96nbc8z4g0yY0&typo=1 Please contact <a href="mailto:info@arin.net" target="_blank">
info@arin.net</a> if you <br>
>> experience any issues.<br>
>><br>
>><br>
>><br>
> _______________________________________________<br>
> ARIN-PPML<br>
> You are receiving this message because you are subscribed to 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://linkprotect.cudasvc.com/url?a=https%3a%2f%2flists.arin.net%2fm" target="_blank">
https://linkprotect.cudasvc.com/url?a=https%3a%2f%2flists.arin.net%2fm</a><br>
> ailman%2flistinfo%2farin-ppml&c=E,1,PZT3k6xZlfRBghEBxxufd4mu2Ve_KsVjNF<br>
> Fbz6LOCh9lpSIRtyNyDCvryXvevPimoqYvm4gDqykjaXQTjrj8V6QM-AY3-lYKC-1oXXBA<br>
> -awSsCEN&typo=1 Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you experience any
<br>
> issues.<br>
> _______________________________________________<br>
> ARIN-PPML<br>
> You are receiving this message because you are subscribed to the ARIN <br>
> 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://linkprotect.cudasvc.com/url?a=https%3a%2f%2flists.arin.net%2fmailman%2flistinfo%2farin-ppml&c=E,1,7Ni09CD1ljmFeIPgIlxPsmowhjbqJKIodiTfCwNOlmKhZ14Vr7dnwwRwrKtL9uTPbOXDI0KuQCaem9loK7wgsIhZJSpzBDhxgm9nAzbnXnOROSwc6DhT2yhm_ACE&typo=1" 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>
_______________________________________________<br>
ARIN-PPML<br>
You are receiving this message because you are subscribed to 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://linkprotect.cudasvc.com/url?a=https%3a%2f%2flists.arin.net%2fmailman%2flistinfo%2farin-ppml&c=E,1,jSkbKSWaXQTrJjPhLBntdV9jIQI-UsSYpp0q3iuVaeGYk6HUdkIB4W6MVA3fHRPmAMCtv9c1EfFGcAtCkdXzHF4hhRAul0g2d1qR1S6ldmacccek9g,,&typo=1" 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>
_______________________________________________<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://linkprotect.cudasvc.com/url?a=https%3a%2f%2flists.arin.net%2fmailman%2flistinfo%2farin-ppml&c=E,1,hyS_SZosmvXYPrvrXMHbg6QebKsHkOowbH5HPLbB1Ogb8NsE6ltoBtF9uES32VUocGEUKXMybl0Iw_K0lZuw0lKTa6WTlKO_SNTkC04HqhAhiAAEGLUn&typo=1" 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.<o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal"><br clear="all">
<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">-- <o:p></o:p></p>
<div>
<p class="MsoNormal">===============================================<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>
=============================================== <o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>