This document relates to RIPE policy proposal 2010-07 - Ambiguity cleanup on IPv6 Address Space Policy for IXP. If approved, it will replace 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.
ADDITION TO DOCUMENT >> | The new text is shown in blue. |
ORIGINAL TEXT |
NEW TEXT
|
The text from the current policy document that will be replaced is displayed here. |
The proposed new text will be displayed here. |
All other text in the document will not be replaced.
1.0 Introduction
2.0 Definition
3.0 Policy
4.0 Warning
5.0 Obtaining the Address Space
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.
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”.
Networks assigned under this policy may not be globally routable.
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/