Last Call - ARIN Policy Proposal 2001-3

[Louis Lee]

For those of you who did not make it to ARIN IX, I think it's worth noting
that the verbiage regarding the routability of public exchange point
allocations has been removed.  The compromise is that these allocations be
made from a specific block so that individual ISPs can make the decision
whether or not to filter this block.

However, it is still important for the community to understand the
implication of filtering exchange allocations.  I had suggested that CLEW
would include a blurb on this matter in some sort of best-practices manual.
I invite the community to contribute to this effort on the CLEW mailing list
by suggesting the pros and cons of routing exchange allocation.

 http://www.arin.net/policy/wrkgroups.html#clew

(One thing I am wondering about is what is scope of the problem if all the
exchange allocations are in the routing table.  Just how many blocks have
already been assigned?  And what kind of growth are we talking about?)

As a public exchange provider, Equinix will be re-evaluating our requirement
that our Exchange participants *not* announce the Exchange IPs to their
peers.  Since this policy came about, in part, because of ARIN's policy, we
will re-examine our policy if Policy 2001-3 is ratified.

Louie
-------------------------------------------------------
Louis Lee                             louie at equinix.com
Staff Network Engineer             office: 650/316-6162
Equinix, Inc.                         fax: 650/316-6903
http://www.equinix.com/



-----Original Message-----
From: Member Services [mailto:memsvcs at arin.net]
Sent: Friday, April 19, 2002 6:59 AM
To: arin-announce at arin.net; ppml at arin.net; v6wg at arin.net
Subject: Last Call - ARIN Policy Proposal 2001-3


*** Last Call - Policy Proposal 2001-3 *** 

IPv6 Micro-assignments
 
ARIN will make micro-allocations to critical infrastructure providers of
the Internet, including public exchange points, core DNS service
providers (e.g. ICANN-sanctioned root, gTLD, and ccTLD operators) as
well as the RIRs and IANA.  These allocations will be no longer than a
/24 using IPv4 or a /48 using IPv6. Multiple allocations may be granted
in certain situations.

Exchange point allocations MUST be allocated from specific blocks
reserved only for this purpose. All other micro-allocations WILL be
allocated out of other blocks reserved for micro-allocation purposes.
ARIN will make a list of these blocks publicly available.

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.