<div dir="ltr">#1 to /52 or shorter. This makes more sense than anything else I have read.<div><br></div><div>-Chris</div><div><div class="gmail_extra">
<br><div class="gmail_quote">On Tue, Jun 6, 2017 at 12:43 PM, David Farmer <span dir="ltr"><<a href="mailto:farmer@umn.edu" target="_blank">farmer@umn.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jun 6, 2017 at 1:30 PM, Leif Sawyer <span dir="ltr"><<a href="mailto:lsawyer@gci.com" target="_blank">lsawyer@gci.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
The boundaries at /60, /56, and /48 have all been discussed. If one is more favorable than<br>
the other, and you would like to see the proposal edited to use that one, we will certainly<br>
take that under advisory.<br></blockquote><div><br></div><div>Personally, I find any of the three acceptable. I have a preference that "assignments longer than /56 not require SWIP", and "assignments /48 or shorter require SWIP".</div><div><br></div><div>While minimally acceptable, I would prefer to not create an incentive for providers to make assignments as long as /60. I would prefer providers to make assignments no longer than /56, therefore I believe assignments of /56 and longer should not require SWIP. Since assignments /48 and shorter could find their way into the DFZ, therefore I believe they should require SWIP for operational reasons. </div><div><br></div><div>In between /56 and /48 I'm mostly agnostic. But, I suppose we could go with "/52 or shorter" that way there isn't any confusion, that /56 does not require SWIP and /48 does require SWIP. </div></div><div class="gmail_extra"><br></div>Hope that helps.<span class="HOEnZb"><font color="#888888"><br clear="all"><div><br></div>-- <br><div class="m_1766030837816150828gmail_signature">==============================<wbr>=================<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" value="+16126260815" target="_blank">612-626-0815</a><br>Minneapolis, MN 55414-3029 Cell: <a href="tel:(612)%20812-9952" value="+16128129952" target="_blank">612-812-9952</a><br>==============================<wbr>================= </div>
</font></span></div></div>
<br>______________________________<wbr>_________________<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">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" rel="noreferrer" target="_blank">http://lists.arin.net/mailman/<wbr>listinfo/arin-ppml</a><br>
Please contact <a href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.<br></blockquote></div><br></div></div></div>
<br>
<font size="1" style="background-color:white"><span style="font-family:Arial,sans-serif"><span style="font:9px/11px Helvetica,Arial,sans-serif;color:rgb(153,153,153);text-transform:none;text-indent:0px;letter-spacing:normal;word-spacing:0px;float:none;display:inline!important;white-space:normal;background-color:rgb(255,255,255)">This e-mail message may contain confidential or legally privileged information and is intended only for the use of the intended recipient(s). Any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is prohibited. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, or contain viruses. Anyone who communicates with us by e-mail is deemed to have accepted these risks. This company is not responsible for errors or omissions in this message and denies any responsibility for any damage arising from the use of e-mail. Any opinion and other statement contained in this message and any attachment are solely those of the author and do not necessarily represent those of the company.</span></span></font>