<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hello,<br>
<br>
This draft policy will be discussed next week at the nanog PPC, in
addition we welcome feedback on this draft on PPML. Specifically
if you could comment on the following two points it would be
appreciated.<br>
<br>
Thanks,<br>
Andrew<br>
<br>
<br>
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
Does the community support raising the minimum requirement for
IXPs from 2 to 3?<br>
<br>
<br>
Does the community believe that additional clarity is needed to
define if an IXP uses the end-user or ISP fee schedule?<br>
<meta name="ProgId" content="PowerPoint.Slide">
<meta name="Generator" content="Microsoft PowerPoint 12">
<br>
<br>
<br>
On 1/29/2014 7:27 AM, ARIN wrote:<br>
</div>
<blockquote cite="mid:52E91DF0.9040909@arin.net" type="cite"><br>
<br>
<br>
## * ##
<br>
<br>
<br>
Draft Policy ARIN-2014-7
<br>
Section 4.4 Micro Allocation Conservation Update
<br>
<br>
Date: 29 January 2014
<br>
<br>
Problem Statement:
<br>
<br>
Two networks interconnecting are private peers. Three could be
considered an IXP. In light of exhaustion and the low reserve
available to CI _and_ the significant growth of IXP's in North
America, it is prudent to insure that there are minimum criteria
that are sensible in order to not waste address space on an
activity that is delineated by a minimum allocation vs. a /30. The
barrier to entry remains low regardless.
<br>
<br>
Policy statement:
<br>
<br>
Change the following paragraph in Section 4.4 from:
<br>
<br>
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.
<br>
<br>
To:
<br>
<br>
Exchange point operators must provide justification for the
allocation, including: connection policy, location, other
participants (minimum of three total), ASN, and contact
information. IXP's formed as non profits will be considered end
user organizations. All others will be considered ISPs.
<br>
<br>
Comments:
<br>
a.Timetable for implementation:
<br>
b.Anything else:
<br>
_______________________________________________
<br>
PPML
<br>
You are receiving this message because you are subscribed to
<br>
the ARIN Public Policy Mailing List (<a class="moz-txt-link-abbreviated" href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).
<br>
Unsubscribe or manage your mailing list subscription at:
<br>
<a class="moz-txt-link-freetext" href="http://lists.arin.net/mailman/listinfo/arin-ppml">http://lists.arin.net/mailman/listinfo/arin-ppml</a>
<br>
Please contact <a class="moz-txt-link-abbreviated" href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.
<br>
</blockquote>
<br>
</body>
</html>