You are here: Home > Publications > RIPE Document Store > IPv6 Address Space Policy For Internet Exchange Points

Changes to IPv6 Address Space Policy For Internet Exchange Points

Legend (+) Added (-) Deleted
Changed Tag Added Tag Deleted
ripe-451: ripe-256: IPv6 Address Space Policy For Internet Exchange Points (IXPs) are used to exchange Internet traffic between different Internet Service Providers (ISPs).
delete: <h2> Contents delete: </h2>

1.0 delete: <a href="#1"> Introduction delete: </a> delete: <br /> 2.0 delete: <a href="#2"> Definition delete: </a> delete: <br /> 3.0 delete: <a href="#3"> Policy delete: </a> delete: <br /> 4.0 delete: <a href="#4"> Warning delete: </a> delete: <br /> 5.0 delete: <a href="#5"> Obtaining the Address Space delete: </a> delete: </p> delete: <h2> delete: <a id="1" name="1"> delete: </a> 1.0 Introduction delete: </h2> delete: <p> Internet Exchange Points (IXPs) are used to exchange Internet traffic between different Internet Service Providers (ISPs). Many Exchange Point operators require address space for the peering mesh that is independent from any of the address space in use by member networks. delete: </p> delete: <h2> delete: <a id="12" name="2"> delete: </a> 2.0 Definition delete: </h2> delete: <p> An Internet Exchange Point is defined as a physical network infrastructure (layer 2) operated by a single entity whose purpose is to facilitate the exchange of Internet traffic between ISPs. delete: </p> delete: <p> There must be a minimum of three ISPs connected 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 acquired through the appropriate means (e.g. an upstream ISP). delete: </p> delete: <h2> delete: <a id="13" name="3"> delete: </a> 3.0 Policy delete: </h2> delete: <p> Requesting organisations that meet the definition in section delete: <a href="#2"> 2.0 delete: </a> may receive address space to meet their needs. If the requesting organisation is confident that it will never need more than a single network then a /64 will be assigned. delete: </p> delete: <p> Otherwise, a /48 will be assigned. delete: </p> delete: <p> The prefix will be assigned by the RIPE NCC directly to the IXP, upon a request properly submitted to the RIPE NCC, either directly or through a sponsoring LIR. IXP IPv6 address assignments are subject to the policies described in the RIPE NCC document entitled “Contractual Requirements for Provider Independent Resources Holders in the RIPE NCC Service Region”. delete: </p> delete: <h2> delete: <a id="14" name="4"> delete: </a> 4.0 Warning delete: </h2> delete: <p> Networks assigned under this policy may not be globally routable. delete: </p> delete: <h2> delete: <a id="15" name="5"> delete: </a> 5.0 Obtaining the Address Space delete: </h2> delete: <p> Address space for IXPs qualifying under this policy can be requested by using the form "IPv6 Request Form for Internet Exchange Points" available from the This RIPE Document Store at: delete: <br /> delete: <a href="http://www.ripe.net/ripe/docs/ipv6request-exchangepoint.html"> http://www.ripe.net/ripe/docs/ipv6request-exchangepoint.html delete: </a> is available in ASCII and PDF

RIPE Documents Search