Interim Policy proposal for IPv6 Address Assignment Policy for Internet Exchange Points

Following discussion between the WG-Chairs and the NCC we have the 
following proposed draft.

To enable allocations to be made as soon as possible we are 
soliciting comments over the next few days but unless there are any 
issues we would like to start making allocations by the end of next 
week, ie 7th September 2001.

Please send any comments to the LIR-WG list <lir-wg at ripe.net>

We propose a joint session to be held at RIPE40 where we can discuss 
the initial size allocations, information required in the forms and 
other issues raised by the community after which we will formalise 
the proposal.

Thanks

	Fearghas

EIX-WG Chair

--

IPv6 Address Assignment Policy for Internet Exchange Points
===========================================================

1. Abstract
-----------

This document describes a policy for Internet Exchange Points (IXPs)
under which unique IPv6 address space to be used for the
infrastructure of the Internet Exchange Point can be obtained from a
Regional Internet Registry (RIR).

2. Background
-------------

It has been recognised that there are scenarios in which it is not
desirable for IXPs to obtain address space from one of the Internet
Service Providers (ISPs) connecting at the IXP. In these cases it is
viable to have unique IPv6 address space assigned directly from an
RIR. This address space is needed to adress the Exchange fabric.

This issue has been brought forward to the RIPE community in May 2000
and has subsequently been discussed at RIPE Meetings and on public
RIPE mailing lists.  The conclusions of these discussions are
described in this document.  It is expected that the same policy will
be accepted in the ARIN and the APNIC region at which point it will be
incorporated in the Global IPv6 Policy document.

3. Definition
-------------

An Internet Exchange Point is defined as a physical network
infrastructure (layer 2) operated by a single entity with the purpose
to facilitate the exchange of Internet traffic between Internet
service providers. The number of Internet Service providers connected
should at least be three and there must be a clear and open policy for
others to join. Addresses needed for other purposes (e.g. additional
services provided to the members) should be aquired through other
appropriate means ( e.g. an upstream ISP).

4. Policy
---------

An IXP that seeks to obtain an IPv6 address assignment by the RIR in
its region, needs to submit a request to that RIR. IXPs operating in
the RIPE NCC service region should use the 'IPv6 Request Form for
Internet Exchange Points'
(http://www.ripe.net/ripe/docs/ipv6request-exchangepoint.html).

After approval of the request, the RIR will make the assignment.

Since the address space does not need to be routable globally and an
IXP is expected to only have one subnet, a /64 (64 bits of address
space) will be assigned in most cases.

In the case the IXP is using multiple fabrics (e.g. unicast separated
for multicast), multiple /64s can be assigned to the IXP.

IP Address requests can only be handled if the requestor is a Local
Internet Registry (LIR) or if the request made through an existing
LIR.

5. Other Considerations
-----------------------

It should be noted that ISPs usually do not announce address space
used on the IXP mesh itself to their peers. That means the address
space assigned under this policy is likely not to be routable
globally.