<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi Nick,<br>
<br>
<div class="moz-cite-prefix">On 02/09/2015 16:27, Nick Hilliard
wrote:<br>
</div>
<blockquote cite="mid:55E7073A.4000908@inex.ie" type="cite">
<pre wrap="">On 02/09/2015 14:55, Sascha Luck [ml] wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Does IXP space come out of a separate pool from any other ipv4?
</pre>
</blockquote>
<pre wrap="">
from what I understand, it comes out of a dedicated /16. RIPE NCC will be
able to confirm whether this is a contiguous /16 or not.</pre>
</blockquote>
<br>
185.1.0.0/16 is the /16 reserved for IXP assignments. <br>
<br>
However, according to the RIPE-649: "<i>IP space returned by IXPs
will be added to
the reserved pool maintained for IXP use</i>" [1].
This means that we will also make new IXP assignments from an IP
block different than 185.1.0.0/16,
when re-using the "IP space returned by IXPs".
<br>
<br>
[1] <a class="moz-txt-link-freetext" href="https://www.ripe.net/publications/docs/ripe-649#61">https://www.ripe.net/publications/docs/ripe-649#61</a><br>
<br>
I hope this clarifies<br>
<br>
Andrea Cima<br>
RIPE NCC<br>
<br>
</body>
</html>