You are here: Home > Publications > RIPE Document Store > Address Space Managed by the RIPE NCC

Changes to Address Space Managed by the RIPE NCC

Legend (+) Added (-) Deleted
Changed Tag Added Tag Deleted
ripe-555: This document details the address space managed by the ripe-447: Address Space Managed By The RIPE NCC and the longest prefixes issued from different address ranges.
delete: <h2 class="ContentsHeading"> insert: <h2>

Table of Contents

delete: <p> 1. delete: <a class="anchor-link" href="#overview"> insert: <ol>
    insert: <ol>
      insert: <li>
    1. insert: <a href="#1"> Overview delete: </p> delete: <p> 2. delete: <a class="anchor-link" href="#special-purpose-ranges"> insert: </li>
    2. insert: <li>
    3. insert: <a href="#2"> Special Purpose Ranges delete: </p> delete: <p style="padding-left: 30px; "> 2.1. delete: <a class="anchor-link" href="#ipv6-pi-address-space"> IPv6 PI insert: </li>
    4. insert: </ol>
    insert: </ol>
insert: <blockquote>
2.a. insert: <a href="#2a"> Internet Exchange Points insert: </a> insert: <br />
2.b. insert: <a href="#2b"> Root Name Servers insert: </a> insert: <br />
2.c. insert: <a href="#2c"> Address Space delete: </a> delete: </p> delete: <p> 3. delete: <a class="anchor-link" href="#routing-decisions"> Used by Networks in Africa insert: </a> insert: <br />
2.d. insert: <a href="#2d"> Address Space Assigned for Anycasting TLD Nameservers insert: </a> insert: </blockquote>
insert: <ol>
    insert: <li>
  1. insert: <a href="#3"> Routing Decisions delete: </p> delete: <p> 4. delete: <a class="anchor-link" href="#longest-prefix-tables"> insert: </li>
  2. insert: <li>
  3. insert: <a href="#4"> Longest Prefix Tables delete: </p> insert: </li>
  4. insert: </ol>
insert: <hr />

delete: <a name="overview"> insert: <a name="1"> 1. Overview

This document details the address space managed by the RIPE NCC and the longest prefixes issued allocated or assigned from different address ranges.

All A list of all IPv4 and IPv6 address space managed allocated to the RIPE NCC by the RIPE NCC and the current status of each address range IANA is available as a insert: <b> route-set insert: </b> object in the RIPE Database. insert: </p>

insert: <p>

It can be found in the extended statistics file published daily at the URL below: delete: </p> delete: <p> delete: <a href="ftp://ftp.ripe.net/pub/stats/ripencc/delegated-ripencc-extended-latest"> ftp://ftp.ripe.net/pub/stats/ripencc/delegated-ripencc-extended-latest delete: </a> on the RIPE NCC website at: insert: <br />
insert: <a href="http://www.ripe.net/whois?-rTroute-set+RS-IP-ALLOCATIONS-TO-RIPE-NCC-FROM-IANA"> http://www.ripe.net/whois?-rTroute-set+RS-IP-ALLOCATIONS-TO-RIPE-NCC-FROM-IANA insert: </a> insert: </p>

insert: <p>

A whois client can get it with the following command: insert: <br />
insert: <tt> $ whois -h whois.ripe.net ' -rTrs RS-IP-ALLOCATIONS-TO-RIPE-NCC-FROM-IANA ' insert: </tt>

delete: <a name="special-purpose-ranges"> insert: <a name="2"> 2. Special Purpose Ranges

delete: <a name="ipv6-pi-address-space"> delete: </a> 2.1. insert: <a name="2a"> insert: </a> 2.a. Internet Exchange Points insert: </h3>

insert: <p>

Small IPv6 PI blocks have been assigned to Internet Exchange Points (IXPs) under the IPv6 Address Space Policy for Internet Exchange Points. insert: </p>

insert: <p>

All RIPE NCC IPv6 IXP assignments come from the 2001:7F8::/32 range and are registered in the RIPE Database. insert: </p>

insert: <p>

A full list of IPv6 IXP assignments can be obtained by querying the RIPE Database for all more specific insert: <b> inet6num insert: </b> objects. insert: </p>

insert: <p>

This can be done on the RIPE NCC website at: insert: <br />
insert: <a href="http://www.ripe.net/whois?-rm+2001:7F8::/32"> http://www.ripe.net/whois?-rm+2001:7F8::/32 insert: </a> insert: </p>

insert: <p>

It is possible to create a list of the IP ranges assigned by the RIPE NCC with a command line query like this: insert: <br />
insert: <tt> $ whois -h whois.ripe.net ' -KrmTi6 2001:7F8::/32 ' insert: </tt> insert: </p>

insert: <h3>

insert: <a name="2b"> insert: </a> 2.b. Root Name Servers

IPv6 blocks have been assigned to Root Name Servers under the IPv6 Addresses for Internet Root Servers in the RIPE Region policy. These assignments come from the 2001:7F8::/29 range and are registered in the RIPE Database. insert: </p>

insert: <h3>

insert: <a name="#2c"> insert: </a> 2.c. Address Space Used by Networks in Africa insert: </h3>

insert: <p>

Between October 2003 and April 2005, IPv4 allocations and assignments to Local Internet Registries (LIRs) and End Users in African countries north of the equator were made from 196.200.0.0/13. This range was part of a /8 also used by the insert: <a href="http://www.arin.net/"> American Registry for Internet Numbers insert: </a> (ARIN) for African allocations. Because the longest prefix ARIN allocated or assigned for 196/8 was /24, this was also the longest prefix the RIPE NCC assigned from 196.200.0.0/13. insert: </p>

insert: <h3>

insert: <a name="2d"> insert: </a> 2.d. Address Space Assigned for Anycasting TLD Nameservers insert: </h3>

insert: <p>

Policy proposal 2005-02 was accepted in September 2006 and allowed the RIPE NCC to assign single IPv4 and IPv6 prefixes to Top Level Domains (TLDs) for anycasting DNS. The RIPE NCC assigns IPv6 Provider Independent (PI) prefixes in accordance with the delete: <a href="http://www.ripe.net/ripe/docs/ipv6-policies.html#IPv6_PI_Assignments"> IPv6 Address Allocation and Assignment Policy delete: </a> . IPv4 assignments are /24 and are taken from 194.0.0.0/18. The IPv6 PI assignments smaller than a /32 are /48 and are taken from 2001:678::/29.

delete: <a name="routing-decisions"> insert: <a name="3"> 3. Routing Decisions

Routing decisions are the responsibility of network operators. Network operators taking routing decisions based on prefix length are requested and encouraged to route at least blocks of sizes corresponding to the longest prefix and larger.

delete: <a name="longest-prefix-tables"> insert: <a name="4"> 4. Longest Prefix Tables

delete: <p> The smallest prefix assigned by the RIPE NCC from any insert: <table class="invisible"> insert: <colgroup>insert: <col width="228">insert: <col width="193">insert: </colgroup>insert: <tbody>insert: <tr>insert: <td>insert: <td>insert: </tr>insert: <tr>insert: <td>insert: <td>insert: </tr>insert: <tr>insert: <td>insert: <td>insert: </tr>insert: <tr>insert: <td>insert: <td>insert: </tr>insert: <tr>insert: <td>insert: <td>insert: </tr>insert: <tr>insert: <td>insert: <td>insert: </tr>insert: <tr>insert: <td>insert: <td>insert: </tr>insert: <tr>insert: <td>insert: <td>insert: </tr>insert: <tr>insert: <td>insert: <td>insert: </tr>insert: <tr>insert: <td>insert: <td>insert: </tr>insert: <tr>insert: <td>insert: <td>insert: </tr>insert: <tr>insert: <td>insert: <td>insert: </tr>insert: <tr>insert: <td>insert: <td>insert: </tr>insert: <tr>insert: <td>insert: <td>insert: </tr>insert: <tr>insert: <td>insert: <td>insert: </tr>insert: <tr>insert: <td>insert: <td>insert: </tr>insert: <tr>insert: <td>insert: <td>insert: </tr>insert: <tr>insert: <td>insert: <td>insert: </tr>insert: <tr>insert: <td>insert: <td>insert: </tr>insert: <tr>insert: <td>insert: <td>insert: </tr>insert: <tr>insert: <td>insert: <td>insert: </tr>insert: <tr>insert: <td>insert: <td>insert: </tr>insert: <tr>insert: <td>insert: <td>insert: </tr>insert: </tbody>insert: </table> insert: <p>

insert: </p>

insert: <p>

insert: </p>

insert: <table class="invisible"> insert: <colgroup>insert: <col width="222">insert: <col width="187">insert: </colgroup>insert: <tbody>insert: <tr>insert: <td>insert: <td>insert: </tr>insert: <tr>insert: <td>insert: <td>insert: </tr>insert: <tr>insert: <td>insert: <td>insert: </tr>insert: <tr>insert: <td>insert: <td>insert: </tr>insert: <tr>insert: <td>insert: <td>insert: </tr>insert: <tr>insert: <td>insert: <td>insert: </tr>insert: <tr>insert: <td>insert: <td>insert: </tr>insert: <tr>insert: <td>insert: <td>insert: </tr>insert: <tr>insert: <td>insert: <td>insert: </tr>insert: <tr>insert: <td>insert: <td>insert: </tr>insert: <tr>insert: <td>insert: <td>insert: </tr>insert: <tr>insert: <td>insert: <td>insert: </tr>insert: <tr>insert: <td>insert: <td>insert: </tr>insert: <tr>insert: <td>insert: <td>insert: </tr>insert: <tr>insert: <td>insert: <td>insert: </tr>insert: <tr>insert: <td>insert: <td>insert: </tr>insert: <tr>insert: <td>insert: <td>insert: </tr>insert: <tr>insert: <td>insert: <td>insert: </tr>insert: </tbody>insert: </table> insert: <p>

insert: </p>

insert: <div id="sdfootnote1">
insert: <p>

insert: <a href="#sdfootnote1anc" name="sdfootnote1sym"> insert: </a> 1 See insert: <a href="#2"> Section 2 insert: </a> : Special Purpose Ranges insert: </p>

insert: </div>
insert: <div id="sdfootnote2">
insert: <p>

insert: <a href="#sdfootnote2anc" name="sdfootnote2sym"> insert: </a> 2 See insert: <a href="#2"> Section 2 insert: </a> : Special Purpose Ranges insert: </p>

insert: <p>

insert: </p>

insert: </div>
insert: <div id="sdfootnote3">
insert: <p>

insert: <a href="#sdfootnote3anc" name="sdfootnote3sym"> insert: </a> 3 2A00::/12 was allocated in October 2006, expanding 2A01::/16 which was allocated in December 2005, which incorporated the previously allocated 2A01::/23. insert: </p>

insert: </div>
Address Space Managed by the By The RIPE NCC