<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 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@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><font size=2 color="#1f497d" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>While I agree with the general direction David is heading, his text is still overly complex to deal with the goal. This whole thread only requires 3 lines:<o:p></o:p></span></font></p><p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></font></p><p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Reallocations MUST provide SWIP.<o:p></o:p></span></font></p><p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Requests by the assignee MUST provide SWIP.<br>Anything appearing independently in the global routing table SHOULD provide SWIP.<o:p></o:p></span></font></p><p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></font></p><p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>All the rest is noise that doesn’t add to solving any problem known to mankind, and is simply an artifact of the IPv4-think insane conservation mindset. Size is irrelevant in both protocol versions, and even if you think it is, the only time it comes up is in #3. In any case the length of #3 might change over time, and there is no reason the policy text needs to change to track it. If something is independent, no matter what it’s length is, the intent is to have accurate contact info. <o:p></o:p></span></font></p><p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></font></p><p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Saying anything more is trying to legislate ISP behavior, which is explicitly outside the scope of ARIN.<o:p></o:p></span></font></p><p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></font></p><p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Tony<o:p></o:p></span></font></p><p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></font></p><p class=MsoNormal><a name="_MailEndCompose"><font size=2 color="#1f497d" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></font></a></p><div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";font-weight:bold'>From:</span></font></b><font face=Tahoma><span style='font-family:"Tahoma","sans-serif"'> ARIN-PPML [mailto:arin-ppml-bounces@arin.net] <b><span style='font-weight:bold'>On Behalf Of </span></b>David Farmer<br><b><span style='font-weight:bold'>Sent:</span></b> Sunday, July 23, 2017 7:03 AM<br><b><span style='font-weight:bold'>To:</span></b> arin-ppml@arin.net<br><b><span style='font-weight:bold'>Subject:</span></b> Re: [arin-ppml] Draft Policy ARIN-2017-5: Equalization of Assignment Registration requirements between IPv4 and IPv6 - updated 2017-07-21<o:p></o:p></span></font></p></div></div><p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:10.0pt'><o:p> </o:p></span></font></p><div><p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:10.0pt'>The rewrite is a pretty good step forward, and I support this policy as written, but I also would like to see some additional changes. <o:p></o:p></span></font></p><div><p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:10.0pt'><o:p> </o:p></span></font></p><div><p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:10.0pt'>The following is a summary of what I would like to see the overall policy look like, it is not in policy language but provided as list of requirement, with some additional notes, then I note what I think is missing from the current proposed policy text;<o:p></o:p></span></font></p><div><p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:10.0pt'><o:p> </o:p></span></font></p></div><div><div><p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:10.0pt'>Reallocations:<o:p></o:p></span></font></p></div><div><p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:10.0pt'>- All reallocations* MUST have a SWIP provided regardless of size.<o:p></o:p></span></font></p></div><div><p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:10.0pt'><o:p> </o:p></span></font></p></div><div><p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:10.0pt'>Reassignments: <o:p></o:p></span></font></p></div><div><p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:10.0pt'>- For prefixes shorter than /48 a SWIP MUST be provided.<o:p></o:p></span></font></p></div><p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:10.0pt'>- For prefixes at /48 or longer a SWIP is provided at the discretion** of the ISP, except; <o:p></o:p></span></font></p><div><p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:10.0pt'> - If requested by the end-user, then a SWIP MUST be provided, or;<o:p></o:p></span></font></p></div><div><p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:10.0pt'> - If intended to appear in global routing table, then a SWIP SHOULD*** be provided.<o:p></o:p></span></font></p></div><div><p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:10.0pt'><o:p> </o:p></span></font></p></div><div><p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:10.0pt'>* Reallocations are made to other ISPs which then can make reassignments, for IPv6 it is RECOMMENDED that all ISPs obtain an allocation directly from ARIN, however reallocations are still permitted. Further, reallocations for prefixes /48 or longer are NOT RECOMMENDED. SWIPs for reallocations need to be required because the abuse and other POC for the down stream ISP need to be know.<o:p></o:p></span></font></p></div><div><p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:10.0pt'><o:p> </o:p></span></font></p></div><div><p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:10.0pt'>** There should be some guidance (NOT policy enforced by ARIN) to ISPs making reassignments at /48 or longer: SWIPs for business customers, especially those with information technology(IT) operations sophisticated enough to handle their own abuse and/or technical incidents, are of interest to the community. SWIPs for residential customers (individual persons) are NOT normally of interest to the community.<o:p></o:p></span></font></p></div><div><p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:10.0pt'><o:p> </o:p></span></font></p></div><div><p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:10.0pt'>*** This might be more appropriate as MUST, however as ARIN does not define routing policy, therefore SHOULD seems more appropriate.<br clear=all><o:p></o:p></span></font></p></div></div><div><p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:10.0pt'><o:p> </o:p></span></font></p></div></div><div><p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:10.0pt'>So, I think the following is missing from the current proposed policy text;<o:p></o:p></span></font></p></div><div><p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:10.0pt'><o:p> </o:p></span></font></p></div><div><p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:10.0pt'>1. Any mention of reallocations, but this wasn't in the original policy either <o:p></o:p></span></font></p></div><div><p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:10.0pt'>2. A requirement that SWIP is provided if requested by end-user<o:p></o:p></span></font></p></div><div><p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:10.0pt'>3. Guidance for SWIPs for /48 or longer, while these SWIPs aren't required, some guidance still might be useful.<o:p></o:p></span></font></p></div><div><p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:10.0pt'><o:p> </o:p></span></font></p></div><div><p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:10.0pt'>Thanks<o:p></o:p></span></font></p></div><div><p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:10.0pt'><o:p> </o:p></span></font></p><div><p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:10.0pt'>On Fri, Jul 21, 2017 at 11:44 AM, Leif Sawyer <<a href="mailto:lsawyer@gci.com" target="_blank">lsawyer@gci.com</a>> wrote:<o:p></o:p></span></font></p><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#993366" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366'>Happy Friday, everybody.</span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#993366" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366'> </span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#993366" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366'>As promised, here is the latest rewrite of the draft policy below, and it will soon be updated at:</span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#993366" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366'><a href="https://www.arin.net/policy/proposals/2017_5.html" target="_blank">https://www.arin.net/policy/proposals/2017_5.html</a></span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#993366" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366'> </span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#993366" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366'>There are two changes noted in the policy statement: the first of which reflects what seems to be the current</span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#993366" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366'>consensus of the PPML regarding netblock sizing; the second is to strike language that may be read as either restrictive</span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#993366" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366'>or non-operational.</span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#993366" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366'> </span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#993366" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366'>----</span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#993366" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366'> </span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#993366" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366'>Problem Statement:</span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#993366" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366'> Current ARIN policy has different WHOIS directory registration requirements for IPv4 vs IPv6 address assignments. </span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#993366" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366'> IPv4 registration is triggered for an assignment of any address block equal to or greater than a /29 (i.e., eight IPv4 addresses).</span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#993366" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366'> In the case of IPv6, registration occurs for an assignment of any block equal to or greater than a /64, which constitutes one entire IPv6 subnet and is the minimum block size for an allocation.</span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#993366" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366'> Accordingly, there is a significant disparity between IPv4 and IPv6 WHOIS registration thresholds in the case of assignments, resulting in more work in the case of IPv6 than is the case for IPv4.</span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#993366" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366'> There is no technical or policy rationale for the disparity, which could serve as a deterrent to more rapid IPv6 adoption.</span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#993366" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366'> The purpose of this proposal is to eliminate the disparity and corresponding adverse consequences.</span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#993366" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366'> </span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#993366" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366'>Policy statement:</span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#993366" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366'> 1) Alter section 6.5.5.1 "Reassignment information" of the NRPM to strike "/64 or more addresses" and change to "/47 or more addresses, or sub-delegation of any size that will be individually announced,"</span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#993366" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366'>and </span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#993366" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366'> 2) Alter section 6.5.5.3.1. "Residential Customer Privacy" of the NRPM by deleting the phrase "holding /64 and larger blocks"</span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#993366" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366'> </span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#993366" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366'>Comments:</span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#993366" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366'>a. Timetable for implementation:</span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#993366" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366'> Policy should be adopted as soon as possible.</span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#993366" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366'> </span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#993366" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366'>b. Anything else:</span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#993366" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366'> Author Comments:</span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#993366" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366'> IPv6 should not be more burdensome than the equivalent IPv4 network size.</span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#993366" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366'> Currently, assignments of /29 or more of IPv4 space (8 addresses) require registration</span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#993366" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366'> The greatest majority of ISP customers who have assignments of IPv4 space are of a single IPv4 address which do not trigger any ARIN registration requirement when using IPv4.</span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#993366" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366'> This is NOT true when these same exact customers use IPv6, as assignments of /64 or more of IPv6 space require registration. </span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#993366" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366'> Beginning with RFC 3177, it has been standard practice to assign a minimum assignment of /64 to every customer end user site, and less is never used. </span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#993366" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366'> This means that ALL IPv6 assignments, including those customers that only use a single IPv4 address must be registered with ARIN if they are given the minimum assignment of /64 of IPv6 space. </span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#993366" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366'> This additional effort may prevent ISP's from giving IPv6 addresses because of the additional expense of registering those addresses with ARIN, which is not required for IPv4.</span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#993366" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366'> The administrative burden of 100% customer registration of IPv6 customers is unreasonable, when such is not required for those customers receiving only IPv4 connections.</span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#993366" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366'> </span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#993366" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366'> </span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#993366" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366'>---</span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#993366" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366'> </span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#993366" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366'>Leif Sawyer</span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#993366" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366'>Advisory Council</span></font><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=2 color="#993366" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366'> </span></font><o:p></o:p></p></div></div><p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:10.0pt'><br>_______________________________________________<br>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="http://lists.arin.net/mailman/listinfo/arin-ppml" target="_blank">http://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></span></font></p></div><p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:10.0pt'><br><br clear=all><o:p></o:p></span></font></p><div><p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:10.0pt'><o:p> </o:p></span></font></p></div><p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:10.0pt'>-- <o:p></o:p></span></font></p><div><p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:10.0pt'>===============================================<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: <a href="tel:(612)%20626-0815" target="_blank">612-626-0815</a><br>Minneapolis, MN 55414-3029 Cell: <a href="tel:(612)%20812-9952" target="_blank">612-812-9952</a><br>=============================================== <o:p></o:p></span></font></p></div></div></div></div></div></div></body></html>