<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><br></div><div>Anyone want to debate why there is any multi homing requirement in 2014? </div><div><br></div><div>Best,</div><div><br></div><div>-M<</div><div><br></div><div><br><br><br></div><div><br>On Nov 19, 2014, at 22:18, John Von Stein <<a href="mailto:John@qxccommunications.com">John@qxccommunications.com</a>> wrote:<br><br></div><blockquote type="cite"><div>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (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: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;}
@font-face
{font-family:Verdana;
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:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.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]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Speaking from recent / current experience, the multi-homing requirement is a bit of a challenge for tweener-sized organizations like QxC. We are too big for underlying fiber carriers to comfortably continue
to supply our need for IP addresses but not in the position to carry the financial, technical or operational challenges of multi-homing. This was a very significant cost commitment for QxC and I can imagine this is not achievable for other like-sized ISPs.
Granted, we are better off for it now but had I known how much of a financial and technical hurdle this really was then I probably would not have done it. I just needed more IP addresses to continue to grow my biz and would have much rather spent the money
and manpower on marketing/sales/customer acquisition. Multi-homing is a nice-to-have luxury that none of my customers are willing to pay for so it is simply a cost of entry to get the IP addresses we need to continue to grow our customer base.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">As such, I support dropping multi-homing as a prerequisite for an IP allocation.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="color:#1F497D">Thank you,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">John W. Von Stein<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">CEO<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black"><image001.jpg></span><span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="color:#1F497D">102 NE 2<sup>nd</sup> Street<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="color:#1F497D">Suite 136<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Boca Raton, FL 33432<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Office: 561-288-6989<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><a href="http://www.qxccommunications.com/"><span style="color:blue">www.QxCcommunications.com</span></a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Verdana","sans-serif";color:black">This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.</span><span style="color:#1F497D"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> <a href="mailto:arin-ppml-bounces@arin.net">arin-ppml-bounces@arin.net</a> [<a href="mailto:arin-ppml-bounces@arin.net">mailto:arin-ppml-bounces@arin.net</a>]
<b>On Behalf Of </b>Richard J. Letts<br>
<b>Sent:</b> Wednesday, November 19, 2014 1:24 PM<br>
<b>To:</b> Steve King; <a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a><br>
<b>Subject:</b> Re: [arin-ppml] Multi-homing justification removed?<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">I believe the intent was there.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">orgs that have a justifiable/provable need for a /24 were been restricted by their current/lone provider being unwilling to give them enough address space. Not everyone has the ability to change providers, and
if you can’t change providers then you certainly would not be able to multihome..<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt;line-height:12.0pt"><b><span style="color:#111111">Richard Letts</span></b><span style="font-size:7.5pt;color:gray"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></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 #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> <a href="mailto:arin-ppml-bounces@arin.net">arin-ppml-bounces@arin.net</a> [<a href="mailto:arin-ppml-bounces@arin.net">mailto:arin-ppml-bounces@arin.net</a>]
<b>On Behalf Of </b>Steve King<br>
<b>Sent:</b> Wednesday, November 19, 2014 9:47 AM<br>
<b>To:</b> <a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a><br>
<b>Subject:</b> [arin-ppml] Multi-homing justification removed?<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The changes implemented in ARIN-2014-13, specifically the removal of 4.3.2.2, appear to have removed the multi-homing justification for a /24 for end users. Previously, the need to multi-home, and proof of contracts with multiple upstream
providers, was sufficient to justify a /24 to participate in BGP.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">For reassignments from ISPs, the language remains in 4.2.3.6. Users can justify a /24 via a requirement to multi-home rather than utilization rate. However this revision appears to leave utilization rate as the only criterion for direct
end-user assignments.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Was this the intent or possibly an overlooked side effect of the change?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><u><span style="color:black"> </span></u><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:black">Steve King<o:p></o:p></span></b></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:black">ICON Aircraft</span><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:black">
</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
</div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>PPML</span><br><span>You are receiving this message because you are subscribed to</span><br><span>the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).</span><br><span>Unsubscribe or manage your mailing list subscription at:</span><br><span><a href="http://lists.arin.net/mailman/listinfo/arin-ppml">http://lists.arin.net/mailman/listinfo/arin-ppml</a></span><br><span>Please contact <a href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.</span></div></blockquote></body></html>