Joergen Hovland; First of all, if you insist writing your name beyond ASCII, that's fine if it is common local practice within your country. However, you should accept the fact that your international mail is often treated as SPAM.
One important factor not explained yet very well is that BGP converges slowly as the number of ASes increases, which is another reason to limit the global routing table size.
You can try but you can't stop the evolution(tm).
I don't.
A number like that or any other number will be just as "fatal" like the 640kb
Who said 8192 of the global routing table size fatal? It, of course, is doable, as exemplified by the current reality with
100K.
problem was in the 80's in the long run. The problem with the current IPv6 specification as I see it is purely technical and should be dealt with by the vendors making the IP routers. There is more than one way to implement routing algorithms, and several of them could equally give the best performance. Of course it would help if the RIR's tried not to hand out more than 1 prefix per LIR.
Wrong. It does impose unnecessary restriction on mergers of LIRs.
If a LIR is multihomed they should be allocated a prefix.
If the LIR covers large enough (a lot lot larger than 200), yes of course.
If not then people will stick to IPv4 until we really run out of ip's and keep sticking to it.
Sure. It is exactly why I suggest giving v4 blocks to ISPs, only when the ISPs publicly announce that they will fully support v6 shortly , which was presented several years ago at Amsterdam RIPE meeting. At that time, many expected, without technical reasons, that IPv6 will prevail.
Then we would have major problems deprecating IPv4. PI allocations doesn't exist anymore with IPv6 so that problem is solved..?
The only technical way to deprecate v4 is to exhaust the v4 address space. It should be noted that NAT delayed the exhaustion and delayed v6 deployment. It should also be noted that it was good because v6 is still faulty not to be deployed widely. Masataka Ohta