This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[address-policy-wg] Re: [ppml] Just say *NO* to PI space -- or how to make it less destructive
- Previous message (by thread): [address-policy-wg] Re: [ppml] Just say *NO* to PI space -- or how to make it less destructive
- Next message (by thread): [address-policy-wg] Re: [ppml] Just say *NO* to PI space -- or how to make it less destructive
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Tim Streater
tim.streater at dante.org.uk
Tue Apr 25 11:15:54 CEST 2006
At 03:39 21/04/2006, Stephen Sprunk wrote: >ARIN Region origin ASes present in the Internet Routing Table: 10637 >... >ARIN Region transit ASes present in the Internet Routing Table: 986 > >To me, that says we have 9651 non-transit ASes in ARIN-land today. > >Now, if every one of those ASes got an assignment under 2005-1, we'd kick up the size of the v6 routing table to 14 times its current size -- but it'd still be only 1/18th of the current v4 table. Where's the problem? [...] >OTOH, it's ridiculously easy to get PIv4 space today (512 hosts and two pipes or tunnels), and there's not all that many companies doing it. It's not growing much either. The doors are already wide open for a land rush and nobody is taking ARIN up on >it. Why does everyone assume it'll happen with v6 if it's not happening with v4, which _is_ useful today? This is perhaps the most pertinent question to have been asked during this thread and I'm not sure I saw any answer to it. So I'll ask it again. What is the evidence that using v4's PI policy for v6 would lead to a land rush of catastrophic proportions and the routing table becoming huge? All I've seen so far is hand-waving doomsayers. Remember that to get PI space at all you have to know what you are doing, and you have to justify the usage. And the process takes a certain time. All of these would tend to discourage the casual enquirer. -- Tim
- Previous message (by thread): [address-policy-wg] Re: [ppml] Just say *NO* to PI space -- or how to make it less destructive
- Next message (by thread): [address-policy-wg] Re: [ppml] Just say *NO* to PI space -- or how to make it less destructive
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]