Now IPv6 enabled
I did some interesting IPv6 and DNS testing the other day with a customer. I decided to put a little blog post together on my findings. You can read the post at the Secure64 blog about DNS
Tags: DNS, IPv6, secure64
This entry was posted
on Monday, July 9th, 2012 at 4:08 pm and is filed under Ipv6 tips and tricks.
You can follow any responses to this entry through the RSS 2.0 feed.
You can leave a response, or trackback from your own site.
Sorry if this is off topic, but the traffic is so low now I thought it wouldn’t matter. It seems Huston is predicting RIPE depletion in just nine days from now on September 21, but the prediction here is not for about five more months. Is Huston way off? Why the difference?
Mindbuilder, if you look at RIPE’s chart it suggests Huston is on the money!
Link got munged there: http://www.ripe.net/internet-coordination/ipv4-exhaustion/ipv4-available-pool-graph
For what it’s worth, the Huston prediction may still be slightly optimistic considering the apparent last-minute rush for addresses. I’d guess that RIPE will run out early next week.
And today they’ve gone!
Thanks, Looks like I have to adjust my predictions here a little….
I must have some reserve space that I’m counting that should be there.
The strange thing is that some space that are allocated does not show up in the RIPE file.
A few examples are 220.127.116.11 – 18.104.22.168 that does not show up in the latest delegated-ripe file.
however, if you do a whois it says that this network is delegated to EWE tel in Germany.
Same thing with 22.214.171.124/21. Not mentioned in the statistics file, but whois says Jump Internet in Romania.
There are plenty of those examples. Somebody from Ripe that can explain?
I’m not from RIPE, but whois for 126.96.36.199/15 gives a netname of “DE-EWETEL-20120914″, so I’m guessing it’s newly-allocated address space and will show up in the next daily update of delegated-ripe. 188.8.131.52/21 is similarly named.
Those are only two examples. there are plenty of other (enough for RIPE to last until next year).
For example, what is 184.108.40.206 – 220.127.116.11 and why can’t they use that?
18.104.22.168, ok when did they do that? why?
22.214.171.124 is reserved for http://www.ripe.net/ripe/policies/proposals/2010-01
126.96.36.199 was moved to Afrinic in 2005. Why? Because RIPE african members became Afrinic members together with their space.
For years you were saying that you knew about some secret ranges that RIPE lost but should use and were refusing to name them. And now, when it’s too late, you started revealing your findings. Nice.
BTW, where were you getting your data from?
Grahm: I expect the real question about the temporary space /13 was this: why retain the /13 temporary address pool when RIPE has nothing left to allocate/assign except that and the final /8? The temporary pool is only allocated for short periods (1 month or so for /14, longer with renewals for /13 or smaller), so these can be reclaimed quickly when RIPE eventually needs the addresses. Using them now would only gain you an extra day or so in the final rush we saw and lose the ability to assign address space to conferences and the like post-depletion.
I could well be wrong, but I expect the data comes from the RIPE delegated prefixes file (mirrored at http://bgp.potaroo.net/stats/ripe/delegated, but there will be an official link somewhere at RIPE) and the IANA equivalent. If you know the RIR got a /8 from IANA, you can then look for gaps in their allocation records. Of course, that falls down a bit for the reassigned-to-Afrinic addresses and the temporary pool, and there seem to be gaps in that file regardless (188.8.131.52 for Sky Broadband).
rb12345: “delegated” does not have free space. For 1.5 years already there is also an “extended” RIPE file, with free space listed. ftp://ftp.ripe.net/pub/stats/ripencc/
It’s a good thing to find missing bits and tell RIPE that they lost them. But maybe better do this before they switched to /22 per cust.
Why is this a gap?
It wasn’t meant to be a gap, but I think I simply missed that line in my rather quick search through the file. (Thanks for finding the links to the original RIPE source too!)
My personal assumption though is that there are no missing bits after all, just reassigned space like the Afrinic example.
Mail (will not be published) (required)
When will RIPE be depleted of IPv4 addresses?
The IPv4 Depletion site is proudly powered by WordPress
| Entries (RSS)
| Comments (RSS). Designed by Free CSS Templates Copyright 2010 - Stephan Lagerholm