2014-7 Previous Version [Archived]
OUT OF DATE?
Here in the Vault, information is published in its final form and then not changed or updated. As a result, some content, specifically links to other pages and other references, may be out-of-date or no longer available.
View the current policy proposal text.
the following version was archived on 25 March 2015.
Draft Policy ARIN-2014-7
Section 4.4 Micro Allocation Conservation Update
Date: 4 March 2014
Problem Statement:
Two networks interconnecting are generally considered to be private peers. The current policy allows an IXP to receive a micro-allocation with only two devices. Given IPv4 exhaustion and the growth of IXPs in North America it is prudent to raise the minimum criteria so that micro-allocation space is not wasted.
Policy statement:
Change the following paragraph in Section 4.4 from:
Exchange point operators must provide justification for the allocation, including: connection policy, location, other participants (minimum of two total), ASN, and contact information.
To:
Exchange point operators must provide justification for the allocation, including: connection policy, location, other participants (minimum of three total), ASN, and contact information.
Comments:
a.Timetable for implementation: Immediate
b.Anything else:
XXXXX
The following version was archived on 4 March 2014
Draft Policy ARIN-2014-7
Section 4.4 Micro Allocation Conservation Update
Date: 29 January 2014
Problem Statement:
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.
Policy statement:
Change the following paragraph in Section 4.4 from:
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.
To:
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.
Comments:
a.Timetable for implementation:
b.Anything else:
OUT OF DATE?
Here in the Vault, information is published in its final form and then not changed or updated. As a result, some content, specifically links to other pages and other references, may be out-of-date or no longer available.