<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8">
</head>
<body>
<div style="font-family:sans-serif"><div style="white-space:pre-wrap"><div dir="auto">Hi,
</div><div dir="auto">
</div><div dir="auto">but the receiving party could (will?) announce more specific prefixes after the trade, therefore it wont make a big difference after all.
</div><div dir="auto">
</div><div dir="auto">Jörg
</div><div dir="auto">
</div><div dir="auto">On 23 Sep 2016, at 9:10, Ping IP wrote:
</div><div dir="auto">
</div></div>
<blockquote style="border-left:2px solid #777; color:#777; margin:0 0 5px; padding-left:5px"><div id="6E2B71D7-C83D-4B0F-A224-9F07089D71D4"><div dir="ltr"><div>Hello Jörg,</div><div><br></div><div>Although I used a /22 and /20 as an example. I deliberately mention IP addresses, since this idea can be used for IPv4 and IPv6.</div><div><br></div><div>Perhaps its too little, too late for IPv4. But it helps one of the goals of RIPE.</div><div><br></div><div>Best regards,</div><div><br></div><div>Abdelouahed</div><div>Ping IP network</div></div><div class="gmail_extra"><br><div class="gmail_quote">2016-09-22 16:04 GMT+02:00 Jörg Kost <span dir="ltr"><<a href="mailto:joerg.kost@premium-datacenter.de" target="_blank">joerg.kost@premium-datacenter.de</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
I like the idealism of this idea, but it is too little, too late and much too many work to save a few bytes on the ip4 routing table. This race is lost, adding more memory to the board or block and remove certain routes will be the solution. My focus shifted already to the future (?) disaggregation of ip6, where we had hit the 32k lately.<span class="HOEnZb"><font color="#888888"><br>
<br>
Jörg</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
On 22 Sep 2016, at 14:37, Ping IP wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello,<br>
<br>
One of the goals of RIPE is to aggregate IP addresses. I'd like to suggest<br>
the ability for a LIR and End User to exchange number of blocks of IP<br>
ranges for a greater block.<br>
<br>
For example:<br>
LIR/End User has 4 different /22 subnets and LIR/End User can exchange<br>
these subnets for 1 x /20 subnet.<br>
<br>
This gives a LIR or End User the possibility to announce larger IP subnets<br>
to the Internet. Helping the goal of aggregating the IP addresses on the<br>
Internet.<br>
<br>
According one of the RIPE trainer, this is currently not possible according<br>
the RIPE policy. Because there's no policy to give a LIR/End User this<br>
ability.<br>
<br>
I'm curious to what you think of this idea.<br>
<br>
Best regards,<br>
<br>
Abdelouahed<br>
Ping IP network<br>
</blockquote>
</div></div></blockquote></div><br></div></div></blockquote>
<div style="white-space:pre-wrap"><div dir="auto">
</div></div>
</div>
</body>
</html>