<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=us-ascii"> <meta name="Generator" content="Microsoft Exchange Server">  <style></style> </head> <body> <font face="Arial" size="2"><span style="font-size:11pt;"> <div>Hi all</div> <div> </div> <div>My question is: Why RIPE NCC should go one step back instead one step forward?</div> <div><font size="2"><span style="font-size:10pt;"> </span></font></div> <div>I remember an idea to remove status "Provider Aggregatable" (PA) and "Provider Independent" (PI) for IPv6 addresses [see Ref 1 / Ref 2]. If we go ahead with this idea and open it for any kind of IP address, than final result is the same as current guidance request.</div> <div><font size="2"><span style="font-size:10pt;"> </span></font></div> <div>Ref 1: <a href="http://ripe62.ripe.net/presentations/148-wg.pdf /"><font color="blue"><u>http://ripe62.ripe.net/presentations/148-wg.pdf</u></font></a></div> <div>Ref 2: <a href="http://ripe63.ripe.net/presentations/143-wg3.pdf"><font color="blue"><u>http://ripe63.ripe.net/presentations/143-wg3.pdf</u></font></a></div> <div><font size="2"><span style="font-size:10pt;"> </span></font></div> <div>I think, I could accept request as our first step in direction of removing status "Provider Aggregatable" (PA) and "Provider Independent" (PI).</div> <div> </div> <div>Best regards,</div> <div>Olaf Sonderegger</div> <div><font size="2"><span style="font-size:10pt;"> </span></font></div> <div><font size="2"><span style="font-size:10pt;"> </span></font></div> </span></font> </body> </html>