Changes to Address Space Managed By The RIPE NCC

Table of Contents insert: </h2>

insert: <li>
1. insert: <a class="anchor-link" href="#1"> Overview insert: </a> insert: </li>
insert: <li>
2. insert: <a class="anchor-link" href="#2"> Special Purpose Ranges insert: </a> insert: </li>
insert: <blockquote>

insert: <p>

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 class="anchor-link" href="##2c"> Address Space 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: <br />
2.e. insert: <a href="#2e"> IPv6 PI Address Space insert: </a> insert: </p>

insert: </blockquote>

insert: <li>
3. insert: <a href="#3"> Address blocks transferred to the RIPE NCC insert: </a> insert: </li>
insert: <li>
4. insert: <a href="#4"> Routing Decisions insert: </a> insert: </li>
insert: <li>
5. insert: <a href="#5"> Longest Prefix Tables insert: </a> insert: </li>
insert: </ol>

insert: <a name="1"> insert: </a> 1. Overview insert: </h2>

This document details the address space managed by the RIPE NCC and the longest prefixes allocated or assigned from different address ranges. insert: </p>

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

It can be found 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>

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> insert: </p>

insert: <a name="2"> insert: </a> 2. Special Purpose Ranges insert: </h2>

insert: <a name="2a"> insert: </a> 2.a. Internet Exchange Points insert: </h3>

Small IPv6 blocks have been assigned to Internet Exchange Points (IXPs) under the insert: <a href="https://www.ripe.net/publications/docs/ipv6-policy-ixp.html"> IPv6 Address Space Policy for Internet Exchange Points insert: </a> . 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: <a name="2b"> insert: </a> 2.b. Root Name Servers insert: </h3>

IPv6 blocks have been assigned to Root Name Servers under the insert: <a href="https://www.ripe.net/publications/docs/ipv6-rootservers.html"> IPv6 Addresses for Internet Root Servers in the RIPE Region insert: </a> policy. These assignments come from the 2001:7f8::/29 range and are registered in the RIPE Database. insert: </p>

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

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: <a name="2d"> insert: </a> 2.d. Address Space Assigned for Anycasting TLD Nameservers insert: </h3>

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 IPv4 assignments are /24 and are taken from 194.0.0.0/18. The IPv6 assignments are /48 and are taken from 2001:678::/29. insert: </p>

insert: <a id="2e" name="2e"> insert: </a> 2.e. IPv6 PI Address Space insert: </h3>

Policy proposal 2006-01 was accepted in April 2009 and allowed the RIPE NCC to assign IPv6 Provider Independent (PI) prefixes. The IPv6 PI assignments are taken from 2001:678::/29. insert: </p>

insert: <a id="3" name="3"> insert: </a> 3. Address blocks transferred to the RIPE NCC insert: </h2>

During various transfer activities some legacy address blocks, issued by the InterNIC and other entities to users inside the RIPE NCC service region in the past, were transferred under the RIPE NCC administration. Also some blocks from /8 allocations from the IANA to the RIPE NCC were later transferred to other RIRs. insert: </p>

As a result, RIPE NCC maintains only part of address space mentioned in the “Longest Prefix Tables” below. insert: </p>

insert: <a id="4" name="4"> insert: </a> 4. Routing Decisions insert: </h2>

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. insert: </p>

insert: <a id="5" name="5"> insert: </a> 5. Longest Prefix Tables insert: </h2>

The following table shows longest prefixes allocated or assigned by the RIPE NCC for each listed range. insert: </p>

insert: </p>

insert: </p>

insert: </p>