Here, in New England, I normally see 20% packet loss between Comcast
and Level3 in NewYork using MTR. It has been as high as 60% in the
past so this is an improvement.
James Michael Keller wrote:
Remember that a number of ISP's 'core' routers are going to have ICMP rate limits in place when one of their interfaces is the target. While you may see high packet loss across an ISP link, unless you are getting similar numbers from all hops past that point you aren't looking at real packet loss, since the transit packets are getting through fine. It's just the routers themselves that are ignoring requests or discarding responses in favor of pushing routed packets.
Yes, the routers after Level3's edge router don't show similar packet loss, so this must be the edge router just de-prioritizing ICMP. Thank you for pointing out my mistake.
How long do you think it will be until Sarbanes Oxley and SAS 70 auditors
start requiring disclosure of IPv4 exhaustion as a business continuity
risk, as well as the presence or lack thereof of an IPv6 plan?
When do you plan on telling your customers? (afterwards?)
Ahhh, you don't have any customers that have to plan to buy equipment 2
years in advance. Ok, I understand.
Mike.
ps. 1000 days assumes no rush, speculation, or hoarding. Do people do
that?
pps. Of course these are provocative comments for amusement.
ppps. Or not if you don't have any kind of IPv6 plan. Sorry, sorry...
+----------------- H U R R I C A N E - E L E C T R I C -----------------+
Mike owns Hurricane Electric. HE.net has the most v6 routes, peering, and pretty much any other metric you can dream up. His .sig says "Wholesale IPv4 and IPv6 Transit". What do you think his plan is?
More important question: Perhaps you should spend 15 seconds researching things before you send obviously ignorant comments to 10K of your not-so-close friends?
No worries, the Internet is going to end in 2010, and the world ends on December 21, 2012. I don't think we'll be needing IPv6 in that case.
Has anyone ever figured out how to make multi-homing of customers who only have a /64 assigned to them work? Are the routers on the going to be able to handle the billion routing prefixed that will be introduced? Are there any IP Management software packages that won't bankrupt the world's economy for IPv6 charges?
Maybe the world really will end, and it's all due to IPv6!
ppps. Or not if you don't have any kind of IPv6 plan. Sorry, sorry...
Does it take most network operators more than 1000 days to make an IPv6 plan and start implementing it?
I suppose there is always some network running obsolete gear out somewhere, but their upstream guy may provide them something to avoid the pain (like reclaimed v4 space) or a gateway or other service.
I guess another way to say it is... if you can afford for the planning and implementation to have so many layers of sign-off and buy-in it takes years, you can afford the costs, in everything else, to implement it.
Not to mention, piggyback off of all the published BCPs, improved tools and software, and other things that 2 more years will provide.
Since nobody mentioned it yet, there are now less than 1000 days projected
until IPv4 exhaustion:
No worries, the Internet is going to end in 2010, and the world ends on December 21, 2012. I don't think we'll be needing IPv6 in that case.
Has anyone ever figured out how to make multi-homing of customers who only have a /64 assigned to them work?
how are your /32 v4 announcements working out?
longest prefix I carry in my v6 table are a /48s...
There are only 28224 ASes in announced in the v4 routing system how many non-agregatable announcements will they represent if they all participate in v6 tomorrow?
I've heard all kinds of numbers, you can probably dig something out of the archives.
But my understanding is there are far greater than 10K mailboxes which receive NANOG, especially if you include exploders. Could someone from the mail admin team confirm?
Not to mention, you want to be able to do the regular antispoofing etc and your security devices (which might be based on L2 switches doing DHCP snooping) doesn't do IPv6, so you need to replace them (or live with lower security) and this needs serious budget.
ps. 1000 days assumes no rush, speculation, or hoarding. Do people do
that?
pps. Of course these are provocative comments for amusement.
I keep on saying: its just a mathematical model, and the way this will play
out is invariably different from our best guesses. So to say "well there's x days to go" is somewhat misleading as it appears to vest this model
with some air of authority about the future, and that's not a good idea!
IPv4 address allocation is a rather skewed distribution. Most address allocations are relatively small, but a small number of them are relatively large. Its the the timing of this smaller set of actors who are undertaking
large deployments that will ultimately determine how this plays out. It
could be a lot faster than 1000 days, or it could be slower - its very
uncertain. There could be some "last minute rush." There could be a change
in policies over remaining address pools as the pool diminishes, or ....
So, yes, the pool is visibly draining and you now can see all the way to
the bottom. And it looks like there are around 3 years to go ... but thats with an uncertainty factor of at least +/- about 1 1/2 years.
Unless you're expecting those organisations to be really nice and make that address space available to other organisations (ie. their RIR/LIR, or the highest bidder on ebay), then I don't see how that's relevant - whether they've got machines on those addresses or not, from an outsider's point of view the address space is unavailable for them to use.
..or, maybe your thought is that at some point these guys will start using addresses in those /8s, and stop requesting new allocations from their RIR/LIR, which will in turn slow down IPv4 allocations? I'm not sure, but licking my finger and sticking it out the window suggests that allocations to those with little-utilised /8s is a fairly small percentage.
