[arin-ppml] 4.4 Micro Allocations and IXP requirements

[CJ Aronson]

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.
-----Cathy


"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."


On Thu, Jan 9, 2014 at 2:41 PM, Martin Hannigan <hannigan at gmail.com> wrote:

>
> 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.
>
> 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.
>
> Thoughts?
>
>
> -M<
>
>
>
> _______________________________________________
> PPML
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
> Unsubscribe or manage your mailing list subscription at:
> http://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact info at arin.net if you experience any issues.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20140109/0d9964df/attachment.htm>