Hello,<br><br>I do see it differently. PI address space is easy to use, however, this allocation mechanism does not scale. Therefore was invented CIDR and PA allocation, if you do remember...<br><br>I do not want to say that there is no room for exceptional cases and PI allocations.<br>
<br>However, these must be limited in numbers (of allocations) and perhaps even in time. (you might receive it just for a couple of years.) PI allocation is not a privilage which will be inherited in time...<br><br><br>When I checked the RIPE website and learned that all the working group chairs will decide weather the 2011-02 policy proposal got concensus I was happy.<br>
<br> I still think that it would be dangerous to "release the djin" from the bottle, without any capability to control "the djin" in the future.<br>
<br>I also recommend to study <a href="http://www.ietf.org/rfc/rfc4984.txt" target="_blank">http://www.ietf.org/rfc/rfc4984.txt</a>.<br><br>I
do not object to allow a few exceptional PI allocations, however, a
well defined and understandable safeguarding limit should be implemented
immediately. Later it could be too late.<br>
<br>My proposal was and is to include immediately in 2011-2: If the
number of allocated IPv6 PI slots reaches the number of LIRs in the
region then the PI allocation should be stopped and the PI allocation
policy must be reviewed.<br>
<br>The number of LIRs is a sociological-political term and not a
technical one, but at least clearly understandable by politicians and
managers, and it is reasonably not too high not too low.<br><br>AND this
way the same rule could be applied in all RIRs. Applying the same rule everywhere I consider as a
very important aspect. The other RIRs could easily accept the same.<br>
<br>Anyhow, the number of entries in the global routing tables is just a
global issue. Any related policy should be made at global level, and a
faire manner.<br><br>Best,<br><br>Géza<br>.<br><br><br><br><br><br><div class="gmail_quote">On Mon, Nov 7, 2011 at 11:10 AM, DI. Thomas Schallar <span dir="ltr"><<a href="mailto:t.schallar@avalon.at">t.schallar@avalon.at</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><u></u>
<div bgcolor="#ffffff" text="#000000">
Hello!<br>
<br>
Turchanyi Geza schrieb am 07.11.2011 10:02:
<div class="im"><blockquote type="cite">nothing stops th IPv4 PI owners to use IPv6 PA....</blockquote>
<br></div>
Nothing stops anybody of using PA, neither in IPv4 nor in v6. That's
not the question.<br>
<br>
But any reasons, why somebody wants/needs IPv4 PI space will usually
fully
apply to IPv6 also. It would seem stupid to me, to have IPv4 ("the
past") as PI but IPv6 ("the future") as PA. That won't make sense. What
changed between my v4 PI application and my v6 PI application? If I
won't need PI on v6 any more, I probably won't need it on v4 any longer.<br>
<br>
Siple question: do I need my machines to have provider independend IP
addresses or not? If yes, then I need <u>ANY</u> address (IPv4, IPv6,
IPvSomething) to be PI and not PA.<br>
<br>
So, if somebody already has IPv4 PI space, he/she should more or less
automatically receive v6 PI under the same conditions as for v4. He/she
just has to reason, why some default /48 won't be enough. Thats my
opinion.<br>
<br>
regards,<br><font color="#888888">
Thomas<br>
</font></div>
</blockquote></div><br>