<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
When I got my IXP allocation I was told that I couldn't host any
infrastructure on it - web sites, monitoring boxes, mail servers
and that it was only to be given out to exchange members. I use
other IP space to host the exchange's web, mail and monitoring
services.<br>
<br>
It seems like a pretty poor way to "game the system" and get IP
space since it's a /24 and the initial scrutiny is pretty tough.<br>
<br>
Aaron<br>
<br>
<br>
<div class="moz-cite-prefix">On 1/9/2014 4:53 PM, CJ Aronson wrote:<br>
</div>
<blockquote
cite="mid:CAC6JZKQ6oLFG_Hdzc1BkvH76WBTh_72C0DPDxUQkJ9wq412JZA@mail.gmail.com"
type="cite">
<div dir="ltr">Just for reference the policy with regard to IXPs
says this below. I believe that the point was that the IXP had
to have at least two customers and all this other information
that they are providing a credible IXP in order to get a micro
allocation.
<div>
-----Cathy<br>
<div><br>
</div>
<div><br>
<div>"<span
style="color:rgb(0,0,0);font-family:arial,helvetica,sans-serif;font-size:18px;line-height:1.5em">Exchange
point operators must provide justification for the
allocation, including: connection policy, location,
other participants (minimum of two total), ASN, and
contact information. ISPs and other organizations
receiving these micro-allocations will be charged under
the ISP fee schedule, while end-users will be charged
under the fee schedule for end-users. This policy does
not preclude exchange point operators from requesting
address space under other policies."</span></div>
</div>
</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Thu, Jan 9, 2014 at 2:41 PM, Martin
Hannigan <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:hannigan@gmail.com" target="_blank">hannigan@gmail.com</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">
<div>
<div>
<div><br>
</div>
Someone pointed me at 4.4 and noted that it says that
an IXP can receive an allocation if two parties are
present. The common understanding in the industry is
that two parties connected are private peering and
three on a common switch "could" be an IXP. <br>
<br>
</div>
Is there a reason not to bump this number up to three in
light of prevailing circumstances and conservation of
the infrastructure pool? If two is arbitrarily low, it's
a good time to make three arbitrarily low. I think it
would be wise in terms of insuring that resources are
being used effectively.<br>
</div>
<div><br>
Thoughts?<span class="HOEnZb"><font color="#888888"><br>
</font></span></div>
<span class="HOEnZb"><font color="#888888"><br>
<br>
-M<<br>
<br>
<br>
</font></span></div>
<br>
_______________________________________________<br>
PPML<br>
You are receiving this message because you are subscribed to<br>
the ARIN Public Policy Mailing List (<a
moz-do-not-send="true" href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).<br>
Unsubscribe or manage your mailing list subscription at:<br>
<a moz-do-not-send="true"
href="http://lists.arin.net/mailman/listinfo/arin-ppml"
target="_blank">http://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
Please contact <a moz-do-not-send="true"
href="mailto:info@arin.net">info@arin.net</a> if you
experience any issues.<br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List (<a class="moz-txt-link-abbreviated" href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).
Unsubscribe or manage your mailing list subscription at:
<a class="moz-txt-link-freetext" href="http://lists.arin.net/mailman/listinfo/arin-ppml">http://lists.arin.net/mailman/listinfo/arin-ppml</a>
Please contact <a class="moz-txt-link-abbreviated" href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.</pre>
</blockquote>
<br>
</body>
</html>