You are here: Home > Participate > Policy Development > Policy Proposals > Language Clarification in “IPv6 Address Space Policy For Internet Exchange Points”

This policy proposal has been withdrawn

How to read this draft document:

This document relates to the policy proposal 2014-09, “Language Clarification in “IPv6 Address Space Policy For Internet Exchange Points”. If approved, it will modify ripe-451. To show you how the new document would be different to the old one, we have highlighted any new text or changes to the existing text.

We indicate changes to existing text in the document like this:

ORIGINAL TEXT

NEW TEXT

The text from the current policy document that will be replaced is displayed here.

The proposed text change will be displayed here.

 

Contents

1.0 Introduction
2.0 Definition
3.0 Policy
4.0 Warning
5.0 Obtaining the Address Space

1.0 Introduction

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.

2.0 Definition

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.

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). 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) must be acquired through the appropriate means (e.g. an upstream ISP).

3.0 Policy

Requesting organisations that meet the definition in section 2.0 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.

Otherwise, a /48 will be assigned.

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”.

4.0 Warning

Networks assigned under this policy may not be globally routable.

5.0 Obtaining the Address Space

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 RIPE Document Store at:
http://www.ripe.net/ripe/docs/ipv6request-exchangepoint.html

Get Involved

The Address Policy Working Group develops policies relating to the allocation and registration of Internet number resources (IPv4 and IPv6 addresses and ASNs) by the RIPE NCC and its members. Anyone with an interest in Internet numbering issues is welcome to observe, participate and contribute to the WG. To post a message to the list, send an email to address-policy-wg@ripe.net. Please note that only subscribers can post messages.

RIPE Forum

The RIPE Forum is an additional way to participate in RIPE community mailing list discussions using a web-based interface rather than an email client.

Check out the forum

Please contact if you need more information.

Stay up to date!

Follow @PDO_RIPE_NCC on Twitter.