ARIN Letter Says Two More Years of IPv4
dew4au writes "A reader over at SANS Internet Storm Center pointed out a certified letter his organization received from ARIN. The letter notes that all IPv4 space will be depleted within two years and outlines new requirements for address applications. New submissions will require an attestation of accuracy from an
organizational officer. It also advises organizations to start addressing publicly accessible assets with IPv6. Is ARIN hoping to scare companies into action with the specter of scarce resources? This may be what's needed to spur adoption since there appears to be no business case for IPv6 deployment."
When IPv6 was announced, one of the benefits was that everything could have its own IP address; even your toaster!
So as for a business case, what about the internet toaster business? If we don't switch to IPv6, what will they do?
There's no -1 for "I don't get it."
Nothing gets fixed until it breaks so fully that people can't ignore it any longer. ARIN should just hand out the last of their IP assignment already and then we can move on with actually deploying IPv6.
I just got back from the ARIN meeting this week and the letters are, indeed, a "scare tactic". Network providers keep reporting that PHBs won't spend any money on IPv6 even though engineers are begging for it. Most corporate officers probably think IP is only Intellectual Property and this is an attempt to draw their attention to the fact that the network world as they know it is going to end soon and that the only way to avoid serious problems is to either stop growing or to start IPv6 deployment. PHBs sometimes get the idea when they realize that not spending some money will lead to big problems in a few years. Others figure that if it's over a year away, it really does not matter because it won't impact their bonus this year, so it may not work, but we can hope.
Kevin Oberman, Network Engineer, Retired
I want IPv6 support, but there are lots of pieces still not in place. I am actually using Miredo (Teredo implementation) when I am on the move and Sixxs when I am at home. These are more stop-gap solutions and until the necessary entities start allowing to get on board properly.
My parents live in France and they are with Free.fr who offers IPv6 as a standard option. On the other hand I am living in Canada and not one of the service providers offer IPv6 in any shape or form. One questioned about it they blame their up-stream provider. Even if they are ready the only IPv6 ready router for the home is the Apple Airport Extreme, and even then there is a blocker issue for connecting to Sixxs.net (Apple's bug). Linksys, D-Link and Buffalo are still not ready with a public release and you are left trying to see if the version of DD-WRT you need for IPv6 supports your router. Chances are you will be looking at eBay for a router that has enough flash to support it.
Like the Swine Flu outbreak, I get the feeling that few entities are going to be rushing to do any work until there is media frenzied panic.
There is no killer application for IPv6, since its just infrastructure. On the other hand the lack of a NAT can make certain application solutions easier to implement, since you don't need to do any NAT busting or other fancy tricks. Of course since internal addresses are now all routable, you will certainly need to make sure that you have a real firewall on the gateway device.
Once you are on IPv6 you can start playing around with IPv6 torrent and http://ipv6.google.com/ , if you are curious.
Jumpstart the tartan drive.
...because whoever is in charge of it does such a crummy job of explaining what it is and why I should care, and more importantly, why my folks should care.
I got my router set up to use IPv6 (an Apple Time Capsule), and I went searching for some IPv6 love and found practically none. Yes I got to Google, and yes I found a few websites that seemed to do little more than blink(!) "hooray, you are connecting using IPv6! Your address is ..."
IPv6 needs both a killer app (IPv6-only Twitter, anyone?) and some ready-to-explain-why-you-can't-get-to-it documentation that will get the people to *demand* that they have IPv6 addresses.
Until then, it's a 32-bit address space world.
Case in point. Thought it was supposed to be 2010? Now it's 2011.
IPv4 addresses won't magically be exhausted one night. They'll just start getting more expensive.
Advice: on VPS providers
As I keep pointing out on each IPv6 story, there will be little motivation to move to IPv6 until you can hit major sites, like cnn.com and slashdot.org, using nothing but IPv6 packets.
We've made a bit of progress, in that now, if you have IPv6 connectivity to "the Internet", you can in theory do the name resolution entirely by IPv6 packets, now that the root name servers support IPv6.
Note to the "a little knowledge is a dangerous thing" crowd: yes, you can form an IPv6 packet with an IPv4 address, but that doesn't mean the target machine will actually be able to understand it - it is still a completely different packet type than an IPv4 packet.
So, does slashdot.org have IPv6 enabled? Does the colo housing slashdot.org's servers route IPv6 packets from the Internet to the slashdot.org servers? Can "the Internet" route IPv6 packets to the colo?
If a tech site like slashdot.org doesn't have the ability to handle IPv6 traffic, then why should I get all hot and bothered about trying to get IPv6? And if I'm not going to demand it, then why should my ISP spend the effort to supply it?
www.eFax.com are spammers
ARIN really is the most trustworthy source you could have for a claim like that, though. Sure, many have made the claim before, but this is the next best thing to having Jesus, Moses, Mohamed, Buddha, and Thor all sit down with you around a burning bush and explain the importance of implementing IPv6.
A slashdotter who didn't build his own computer is like a Jedi who didn't build his own lightsaber.
They're already more expensive. The expense increase has been down in the noise for customers - that will no longer be true by the end of the year, and it will hurt by mid 2010.
IPv4 is no longer too cheap to meter. If that's not a business case for IPv6 I don't know what is.
I can get IPV6 from my co-lo provider, but my server control panel (Plesk) doesn't support it ..
So I can serve up "You see this page because you just installed Apache" ... in IPv6..
(wooo!)
= Grow a brain...
Every few months, another prediction comes out that IPv4 is doomed and that we are going to run out of addresses. Those dire predictions never come true, and the predicted date keeps getting extended. When are we truly going to run out? Nobody knows. What will happen is that IPv6 won't become a priority until things start breaking. That's just how it goes.
With this junk IPv4 toaster?
How about they take back the Class A address space owned by companies who probably aren't even utilizing it. Here's a list of a few companies who have class A licenses and you wonder how much of it they are even using:
General Electric 3.0.0.0 - 3.255.255.255
IBM 9.0.0.0 - 9.255.255.255
Xerox Palo Alto Research Center 13.0.0.0 - 13.255.255.255
Hewlett-Packard 15.0.0.0 - 15.255.255.255
Hewlett-Packard (originally DEC, then Compaq) 16.0.0.0 - 16.255.255.255
Apple Inc. 17.0.0.0 - 17.255.255.255
Massachusetts Institute of Technology 18.0.0.0 - 18.255.255.255
Ford Motor Company 19.0.0.0 - 19.255.255.255
Royal Signals and Radar Establishment 25.0.0.0 - 25.255.255.255
Halliburton Company 34.0.0.0 - 34.255.255.255
Why the hell do some of these companies even need 16+ million addresses? I can't see them utilizing the space available, but maybe someone here can enlighten me on how that is done (aside from trying to justify a public IP address for every workstation).
At least we got two more years. Then we can start using phone numbers. IPv6 is insane, unless everybody carries their own DNS cache. Talk about vulnerable!...
...wait, didn't they say the same thing then??!?
You're right. The ipv4 address report at potaroo is a prediction based on modelling and it does change. A while back I started recording the reports and plotting the changes in predictions. It's a bit disappointing that I didn't start before the world began to end because I bet the graph would be a much more interesting shape. Anyway, current predictioned date are getting further away - the number of days remaining at the time the report is made remains roughly constant.
Graphs at http://atchoo.org/ipv4/
Do you have any better hostages?
It's not just some small alarmist group raising a bell over nothing. We will run out of IPv4 at some point. Some estimates say two years, some say eight. Could be more, could be less. At any rate, we WILL run out. Why not adopt a clearly better alternative while we've got time? How can it be disadvantageous?
"If you keep doing what you've always done, you'll keep getting the results you've always gotten."
I think ipV6 is to much of a move. IP addresses are nice and easy to remember like phone numbers. Yes IPv6 has short hand, but it is still harder.
Why couldn't we just add another octect. So my new IP is 1.24.101.1.15. That gives use 2^40 (~1 trillion) versus 2^128(unfuckincredibly big). We made way to big of a jump.
There is also virtually no need to upgrade to v6 for internal communications. We have 10, 172 and 192 which is more then enough for even the largest companies.
I guess we are going to become even more dependent on DNS for everything. I can't imagine someone actually typing a full ipV6 hex address. Mabye the easy ones ::::::b00b:8008
Which one of them set fire to the bush? I wanted to eat those blueberries!
Comment of the year
What would most likely happen is the backbones switch to IPv6, and then the whole IPv4 range can be NAT'd to end users. Most home routers all have the same IP address, 192.168.10.1, and they all run fine. The only difference is your "real" outside IP will be IPv6. Each ISP could assign the whole IPv4 range to their customers.
I would be more worried about IP ports, when computers and networks get fast enough to handle 65,535 connections at a time.
If we had a measurement that said that only 25% of the entire address space is in use at any one time, then maybe would would rethink our choices.
Peak Oil for the internet :-)
Check out my sysadmin blog!
According to my maths, 2^48 addresses on a home lan is enough to individually address every pixel on 32 million 4096x2048 HD displays...
I have 6 IPs just for personal use. Every big networking company that controls some portion of the Internet is set for IPv4 space for a while. There just isn't room for anyone new to enter into the market. This is a huge advantage for those already established companies. I don't think they intentionally planned it this way, but the scarcity of address is a short term advantage for too many businesses for us to simply ignore that and keep pushing IPv6 as if is of some automatic benefit to everyone. Don't get me wrong, I would be thrilled if Comcast and others moved me over to IPv6. Maybe with a massive address space scanning IP blocks for SSH logins and open firewalls would no longer be as a productive use of botnet time.
“Common sense is not so common.” — Voltaire
People have had plenty of warning already, they should just one Saturday give away the remaining IPv4 addresses. And perhaps several key organizations should turn off IPv4 on all equipment they control. Yes, it will cause plenty of havoc and people only have themselves to blame, and moreover can't expect the people who actually implement things (do actual work, as opposed to the PHB's) to work around the existing crap forever.
Actually, I would claim that that's not a big deal. The big problem is that IPv6 just doesn't provide a sensible migration path from IPv4. The idea that we're all going to wake up one day and switch off IPv4 at once just doesn't cut it. More precisely, an IPv4 node just has no way of talking to an IPv6 node. If we built some sort of standardized IPv4-to-IPv6 NAT technology that was invisible to existing IPv4 nodes, then IPv6 could be adopted gradually and incrementally with minimal cost (the cost could be rolled into the cost of general network gear upgrades).
Are you adequate?
This all sounds like peak oil. Addresses won't run out, but the business case will magically spring up when IPv4 addresses become more expensive than implementing alternatives.
True confidence comes not from realising you are as good as your peers, but that your peers are as bad as you are.
If the Pope declares ex cathedra that thou shalt use IPv6, I will convert to Catholicism immediately.
Go green: turn off your refrigerator.
Why no IPv5?
They can pry IPv4 from my tired, RSI-affected-due-to-:-overuse fingers. I'm not about to rely on DNS when debugging and testing my networks. Sure, it's a petty, localized, small scale view, but I don't care.
Most schools and universities are not affected so much by the economy, and most schools and universities don't need a business case to make this switch.
To a monopoly, IPv4 is a better business case. The artificial scarcity of less than 2^32 addresses will keep the cash rolling in.
Actually I've just read a report from Netcraft that shows that IPv4 is dying!
Again, the problem is hoarding of unused IPv4 addresses.
We'd be just fine if it weren't for folks like MIT that have way more IP's than they need.
Of course, when a resource gets tight, the folks who have it become kings. You can bet your behind no company is going to give up it's v4's without a fight.
I'm glad that IPv6 is based upon a stewardship model rather than an ownership model. And also that the v6 guys are leaving 87 percent of the potential v6 namespace unallocated
if you think spam is bad now wait till the spammers go ipv6, those DNSBL lists will be impossibly large (unusable)
when the spammers have trillions of addresses to choose from the stream will become an ocean
Networks need to start migrate to IPv6 as soon as possible. The site www.ipv4depletion.com is a good starting point to see how bad the problem actually is.
And hording addresses will not do you any good. What are you going to use them for when the rest of the world is using IPv6?
All you wanted to know about IPv4 exhaustion, and more.
Predictions aren't facts. They're guesses. The assumptions that go into them can change, and given the number of factors that affect Internet usage growth, they *do* change. The current best guess suggests 2012; the past six months have seen a bit of a reduction in growth, likely due to some sort of global recession.
And, IPv4 exhaustion is a fairly well defined term, meaning either the date IANA allocates its last /8 or the date an RIR allocates its last free block. Price won't go up until *after* exhaustion, because before then, all you need to do is demonstrate a need and you get your allocation from your RIR for the same annual fee everyone else pays. Exhaustion will be an *event*: it will happen at a specific time and date.
"this is the next best thing to having Jesus, Moses, Mohamed, Buddha, and Thor all sit down with you around a burning bush and explain the importance of implementing IPv6."
Yep, but that's not like hearing cthulhu's ghetto hoopti pulling up your drive way.
Fuck systemd. Fuck Redhat. Fuck Soylent, too. Wait, scratch the last one.
When IPv6 was announced, one of the benefits was that everything could have its own IP address; even your toaster!
Wait a minute... Is IPv6 just a clever marketing scheme for NetBSD?
Others figure that if it's over a year away, it really does not matter because it won't impact their bonus this year, so it may not work, but we can hope.
Emphasis mine. Don't they think about next year's bonus too?
I don't know about you guys, but my attitude to work is this: do good work that's valuable to your employer for a reasonable compensation, and prefer to do The Right Thing(tm) when justifiable.
Do PHBs have a different attitude?
IPv6 needs [...] a killer app
And if I own the killer app, can you please explain to me why I don't offer it over via IPv4 also, and multiply my ad revenue by $BIGNUM?
Maybe if I'm someone like Mark Shuttleworth who is willing to gamble money on cool technology with a hope (but no certainty) of making it self-sustaining (or possibly breaking even).
But there are only so many of those people.
The top level authorities are working like mad to arrange the infrastructure for the new flu shot. It might not be here until next September. At lower levels they are trying to calm everyone down, and quietly hoping lots of people get this while it is a non killer flu. That way if it becomes stronger next year it will spread more slowly and infect fewer people. They all are really working quite hard now. Although the ones slaughtering pigs are pretty misguided.
I'd argue there is never going to be a killer app for IPv6 because it is nothing more than window dressing on the same old, boring protocols. The true killer app will be on a protocol that is nothing like TCP/IP... say a working mesh protocol where there is no notion ports, IP addresses or any of that nonsense. Where you don't care where the data you get comes from as long as it is authentic. That is the future. Bit torrent is the closest we have to that future and bit-torrent is nothing but a hack of TCP/IP. If the protocol stack was built from the ground up to not care about the source of data, only that it is authentic, *then* you'd have a killer app.
IPv6 is boring and it isn't even mainstream. How about we cook up something new. Remember when TCP/IP was the new kid on the block and most games had dual or tri-network stacks (TCP/IP, IPX/SPX, Netbeui)? It only took like a few years before all that nonsense went away and we all settled on TCP/IP. Basically, overnight. The same thing *will* happen again. Only it will *not* be IPv6. Mark my words. We've outgrown what IP gives us... The mesh is the future.
Nobody will adopt IPv6 because it is just a larger tree. It doesn't scale the way we are now using it. The way we are starting to use our network is peer-2-peer--dare I even say "cloud-like"?
We dont care where the information comes from, only that it is the real deal. It could come from some data center, some server pool, a microwave, the cell phone, the car stereo, or your neighbors TV... doesn't matter. As long as I know the data is authentic, the source doesn't matter. That is exactly what bit-torrent is about. Only bit-torrent needs a tracker because of the deficenies of TCP/IP. If the network was all about data and how to get to it, rather than maintaining connections between two devices, we wouldn't need trackers or bit-torrent. And when you think about it, this is how it needs to be. Otherwise all the traffic has to aggrigate through larger and larger "central" links--down the tree and back up the tree to the other side. That is what we have now--it is the mindset of IP... you start and the edge node and work in than out to another edge... This doesn't scale and it gives a lot of power to the guys with the big pipes (i.e. your cable company or mega-ISP). Bit-torrent is really a mesh of interconnected goo. That is how it should be--only as a fundamental feature of the network. Focus on the data, not on end to end connections.
IPv6 is more of the same. The fact that it is hierarchical is a bug, not a feature.
Because I believe they are becoming a hindrance to moving onto something better. The future will have layers, yes, but it might not look like the ones in the OSI model.
Why the hell doesn't ARIN just refuse to issue IPv4 allocations to providers that aren't ready for IPv6.
They could also just set a hard deadline for anyone with an allocation to support IPv6 or their IPv4 allocation is forfeit.
We NEED IPv6 because the asses that have huge allocations will never willingly give them back and probably involve lawyers to fight it out.
I've been harassing my ISP for years to provide native IPv4/IPv6.
Instead of hogging these, they should just give them up. They don't need all these addresses.
Sounds like you have never worked with large corporations? Believe me this isn't going to happen, since even if it was technically feasible the politics and bureaucracy would just you insane. Anyhow, who is to say that whole blocks aren't being used? Chances are you will find many partially used blocks instead of lots of block that are completely unused, and that different bickering departments are holding on to different blocks. Believe me, moving to IPv6 is a much more realistic and simpler way forward.
Jumpstart the tartan drive.
The big problem is that IPv6 just doesn't provide a sensible migration path from IPv4.
In many ways this is true, but at the same time there is only so much a sensible migration path can do. As some point you will get to the IPv6 haves and IPv6 have-nots. Those who don't have IPv6 will have to decide whether they need it or can find a way to getting it. In many ways this is no different than when people were still moving away from propriety network protocols to IPv4, the difference is the number of users.
If we all start having systems using dual IPv4/IPv4 stacks now, and having real IPv6 connectivity now, then things won't break when suddenly IPv4 addresses can no longer be allocated. The thinking here is that at that point people won't know whether they are using IPv6 or IPv4, unless they are specifying numerical addresses. This is why the delay in making IPv6 available to everyone increases the chance of breakage becoming evident.
BTW I believe Vista is already using Teredo tunnelling standard, though I would like someone to be able confirm this?
Jumpstart the tartan drive.
Actually, I would claim that that's not a big deal. The big problem is that IPv6 just doesn't provide a sensible migration path from IPv4. The idea that we're all going to wake up one day and switch off IPv4 at once just doesn't cut it. More precisely, an IPv4 node just has no way of talking to an IPv6 node. If we built some sort of standardized IPv4-to-IPv6 NAT technology that was invisible to existing IPv4 nodes, then IPv6 could be adopted gradually and incrementally with minimal cost (the cost could be rolled into the cost of general network gear upgrades).
Haven't you heard about Dual-Stack Lite (DS-Lite)? http://tools.ietf.org/html/draft-ietf-softwire-dual-stack-lite-00
Why couldn't we just add another octect. So my new IP is 1.24.101.1.15.
If you are going to add another octect, which will invariably still break many things, you might as well just accept that going with the extra 12 octects is not much worse.
Jumpstart the tartan drive.
There are 2 problems with IPv6 that are common problems with non-solutions:
1: It is highly disruptive
2: It doesn't solve the problem
The FUNDAMENTAL problem with IPv4 is that it has a LIMITED amount of addresses.
To fix the problem the solution needs to remove the limit, NOT make the limit further away.
IPv6 still has a limit to it, so when you explain to people why they should move to IPv6, you also explain why they should distrust IPv6 as a solution.
When you then explain that it will require a complete re-structuring of the internet infrastructure, they will realise that it can't work. Even if it could, they can safely wait for everyone else to do it first.
So, does anyone have a suggestion for an enhancement to IPv4 that is backwardly compatible and allows for an ever-increasing address space?
Odd, according to the news, 'OMG teh economy are collapsing!!'. Since thousands of multination corporations are going bankrupt every day, why can't their address space be recycled?
They whose government reduces their essential liberties for temporary security, receive neither liberty nor security.
Running out of ports isn't a very significant problem.
The OS tracks a connection as a tuple of (local ip, local port, remote ip, remote port). You'll only run into problems if you try to create a lot of connections to the *same host*. A typical server makes a small number of connections to any given client, so the port numbers can be reused.
If you really do want to create tons of connections between a pair of hosts, you could just add more IPv6 addresses to one of the endpoints to get virtually unlimited port space.
Who pays for ipv4 addresses? They're handed out free FFS.
There are some ISPs who see it as a cash cow (some of the more unscrupulous ones even try to charge you *monthly* for them) - but it's got nothing to do with scarcity.
Instead of using numbers from 0 to 255, we could use four Real numbers. Or how about going real imaginative and use a tuple consisting of complex numbers as an IP address?
Thank you, for putting the lie to this oft-repeated non-sense. Every time there is a discussion about IPv6, someone (usually multiple someones) repeats this rubbish about "IPv6 is not a solution because it too is limited - just a larger limit). Yes, it is limited but it is so large that mankind will not run out of addresses until we either literally spread to many millions of planets throughout the galaxy, each populated by Billions of people, and/or start creating unfathomably large numbers of Nanoscopic electronic devices and individually addressing them with IPv6 addresses. I suppose when we reach the day when your body is filled with nanites that repair damaged cells, destroy cancer and virus infected cells, supplement the immune system, etc, so that you can have almost-immortality, at that point, we *might* start coming close to exhausting the IPv6 address space.
Because, even if everyone has TVs, cars, computers, cell phones, bicycles, refrigerators, stoves, microwaves, home security cameras and security control systems, etc, etc, individually IPv6 addressed, we wouldn't come anywhere near to running out of address space with IPv6.
...they keep saying that in $SMALL_NUM years we'll be out of IP addresses, and $SMALL_NUM years goes by without incident. The sky persistently fails to fall.
Call it the peril of poor predictions, but I'm now officially not worried because the claims have so often been false.
The point about hoarding is a big one. The amount of address space held by US governement entiies ie huge. I've worked with/in several .gov networks and the address allocation in most can chartiably called ineffecient. There are networks of 25K - 50K hosts that use multiple class B and class C allocations, with everything using routable IP addresses, regardless of need.
IPv6 will create some serious growing pains. We have more 20 years of the world wide web and IPv4 w/VLSM experience as an industry. There's a number of things we take for granted in the conventions, and even the protocols that IPv6 can put into question.
Spyder
How many years has it been that we've been getting these "we're gonna run out of IP addresses" articles? It's no wonder no one takes these warning seriously: we've all been subjected to a dramatic demonstration of the boy-crying-wolf parable for some time now.
... the IPv4 address space has been "about" to run out. And indeed, the "officially" allocated address space is depleting, though the correlation between "allocated" and "necessarily in use" is tenuous.
However, even if the number of addresses available for "necessarily in use" interfaces were disappearing fast, it does not automatically follow that IPv6 is the solution.
The real drawback with IPv6 is that, as long as 32 bits are enough, there's no incentive to consider all the training/testing/form-filling that's required to deploy something you won't use - but unless everyone (or pretty much everyone) deploys it before a 33rd bit is inevitable, the "post apocalypse" guys on the network are in some sort of partitioned wilderness. You're not going to get a wide uptake of IPv6 by IPv4 users unless there's a real threat that their IPv4 address will stop working and that's not going to happen.
It's also not the case that we currently have a fully-connected and addressable network of endpoints. In fact it's pretty disconnected and some truly atrocious hacks are required to get application-layer protocols to deal with address-translated networks. IPv6 isn't going to make that go away.
It's much more likely that IPv4 will stay as a network access protocol and there'll be some further application-level hackery (faking DNS results to return temporarirly-assigned IPv4 addresses, etc) which allows the network to transition to a larger number of endpoints in an evolutionary fashion. It won't be entirely pretty, but at least it will be (humanly) possible.
Unfortunately, the more time people spend peddling the idea of IPv6 as a solution, the less time there'll be to cobble together the inevitable grubby hack.
You don't need to change your internal network. You don't need to believe in IPv6.
You just need to add IPv6 addresses to your email and web servers, and if this is beyond you, just get someone with real skillz to do it, instead of whining like some unemployed mainframe programmer.
Actually assignments from RIR's to customers are shown here:
/8 equivalents. This indeed is not "12 to 14", but shows that the reclamation of several 'Class A" addresses would still only give us more months, not years.
<http://www.nro.org/documents/presentations/nro-jointstats_03-31-09.pdf>, on page 4.
This has been growing steadily, and was more than 12
...they keep saying that in $SMALL_NUM years we'll be out of IP addresses, and $SMALL_NUM years goes by without incident. The sky persistently fails to fall.
Call it the peril of poor predictions, but I'm now officially not worried because the claims have so often been false.
Actually, quite incorrect... the number of years left has changed because we're actually getting closer. The IETF working group looking at this said [in 1994]:
The linear growth model, presented by Tony Li, included these last two data points while the logistic model, presented by Frank Solensky, did not. Both models currently suggest that IPv4 addresses would be depleted around 2008, give or take three years.
http://mirror.switch.ch/ftp/doc/ietf/ale/ale-minutes-94dec.txt
Not bad for 15 years ago... Now what excuse are you going to use for not being prepared when we run out?