If you RTFA, that's not at all what is going on here. (Supposedly) All governments of the world have either destroyed their stockpiles, or shipped them to the repositories in the US and Russia. Since that point, the UN has been pushing for the US and Russia to destroy their final (known) stockpiles. The US government has proposed that it hold off doing so for at least another five years (not centuries), during which it will spend another three billion on vaccine research.
LEDs are diodes. They require DC current to operate (unless of course you want them to flicker at 60Hz). You are already going to need that DC power supply to make them work.
Remember how everyone always uses that quote to the exact opposite of what was actually said? Gates was talking about the deficiencies of MSDOS, and how quickly it became apparent that 640KB would not be sufficient in the long term.
With standard IPv6 allocation, each subscriber would get their own/64. That means you personally have a globally addressable space on the order of four billion times large than the entire IPv4 space. You could address every atom in your house and have plenty to spare. Large companies can request up to a/48, and while that may appear to take up a significant portion of the address space, they can hand out some 250 trillion of these. Each of those original founding companies that were allocated a/8 would now get one of these instead. A large tier 1 ISP might be allocated a/32 at a time, allowing up to 16 thousand of these large businesses, tier 2 ISPs, or billions of individual subscribers. We could still allow for some four billion tier 1 ISPs with such large allotments, of which we currently have maybe a dozen.
Before APNIC ran out, we were going through addresses on the order of 20M per month. Lets say we go nuts, stop using NAT, and add all sorts of networked gadgets and do-dads, those companies that get a/48 will never in a thousand years be able to use up those 300 sextillion addresses. Even if the realities of branched networking mean they might want another block from another ISP in another geographic location, it's not going to be noticeable.
I understand what you're saying that we shouldn't be wastefully consuming these addresses, but the reality is that the address space is so large, we could be wasteful, and still have plenty of breathing room until the communication latencies make a unified internet no longer a viable option.
This is nothing more than a rectenna, scaled down to operate at optical wavelengths. Rectenna in the microwave band already operate with 85-90% usable generated electricity. The problem is that while we have electronics fast enough to rectify a microwave signal in the tens of GHz, we have nothing that even comes close to rectifying an optical signal in the hundreds of THz.
MASERs and rectenna already operate using this same principle, and similarly operate at 85% or better efficiency. Since they operate in the tens of GHz range, there are readily available electronics available to handle them.
A P90 is a weapon that you can pretty much look at, and understand that it's intended for close quarter combat, and not fancy long-distance competition shooting. It's a very business-like beast.
Except it is a bullpulp design, incorporating a 10.4" long barrel, much longer than most comparable submachineguns. That gives it significantly higher muzzle velocity and range than most traditional submachineguns.
When you consider that LED bulb will last 20-30 times longer than an incandescent, that network connectivity is only a fraction of the cost of the incandescent bulb.
Putting control at the end of the circuit means you need a dedicated circuit to each device. This allows you to just run one circuit for all your devices.
Actually, they said 4 billion addresses out to be enough for the small handful of military and research operations that will ever be on the internet. They had never planned it would be opened to the public at large.
There are a few. The biggest advantage to me of NAT is it seperates out the external (ISP, out of your control) side and the internal side. What if your ISP suddenly changes that first 64bit number.. or what if you switch ISPs?
Windows has WINS and OSX has ZeroConf (Bonjour) for their own local discovery. I had thought IPv6 had some local discovery mechanism that provided name support but I can't seem to find it. IPv6 capable consumer routers will likely begin offering local DNS services, using the router discovery protocols to automatically update themselves. There will certainly be some naming mechanism. Remembering IP addresses in IPv4 was annoying, but remembering IPv6 addresses is downright painful.
As some consumer routing hardware actually has these functions as seperate chips, in some situations you can actually have a router lose it's firewall capability while still keep working.
In IPv4 with traditional NAT, this is no issue, because being non publically routed addresses they won't make it out of your segment.. with IPv6 it's suddenly public. As originally stated, NAT in this case acts as a second layer.
I don't understand why they would even have a separate firewall, much less one on a wholly separate chip. NAT inherently behaves as a stateful firewall by its very operation. I can't thing of a reason why you would want to add a second stateful firewall outside of that, unless that's to protect its own external interface. Even then, that shouldn't need any protecting, since nothing should be listening on it.
NAT is a stateful firewall. My complaint was that NAT adds features that are nothing more than a work around for a deficient service provider. At best, it provides obscurity on top of existing firewalling behavior, which as the saying goes should never be confused with security.
How much more expensive? Once in mass production, a SoC with a microcontroller, network controller, powerline modem, and relay capable of 10-20W should be doable for a couple dollars. Considering the total operating cost of a LED bulb, that's only going to be a couple percent of its lifetime cost.
We did learn from IPv4, which is why IPv6 was designed with such an ungodly large address space that we do not need to be responsible. These are not intended for the standard incandescent bulb you have to replace once or twice a year. They are intended for the LED bulbs that you install once and then never touch again.
Technically, its only 2^64. The first 64-bits define a single subscriber on the internet. The second 64-bits are auto-generated to uniquely identify a machine or device, the improved version of the 48-bit MAC address.
Unless your provider charges you per connected machine, I don't see why it would really matter. I can't believe it makes any real difference in terms of security.
Each IPv6 address consists of a local segment and a global segment. The first 64-bits are the address assigned to the house or service customer. The second 64-bits are generated locally, optionally from the 32-bit MAC address. You could have billions of lightbulbs addressed in this manner, and still only consume a billionth of the usable address space. IPv6 is the very definition of overkill. Even with foolish use of it, we're not going to run into problems until we become a large interstellar society.
The only people who would even consider running NAT in IPv6 are those who don't really understand what NAT does. Namely, that if you have the available address space, it provides no advantage over a dumb firewall set to block everything.
Their potential as a drone is very useful. You can load up surveillance or communications packages, and let them loiter for months on end. NASA experimented with this a bit several years ago, but was shelved when unexpected turbulence over Hawaii caused excessive dihedral on the wing, eventually resulting in a breakup over the ocean.
The problem with manned flight is that between the pilot, cockpit structure, controls, avionics, water, food, and waste storage, you've got several hundred pounds of dead weight that must be centrally located on the wing. Should you want to operate at altitude, you're going to need a pressurized and heated cockpit and an oxygen supply or compressor pump. The centrally located payload results in significantly higher structural stress than if it were built into the wing, or located on multiple pylons distributed across the wing.
Well it doesn't benefit them either. The fact that they are not spending it means they are getting no benefit out of it, unless they are some strange being who enjoys physically playing with large sums of cash.
Emacs and C compilers? Pah! A virtual machine running in javascript is mad genius unheard of since using graphics cards as software driven DVB modulators.
If you RTFA, that's not at all what is going on here. (Supposedly) All governments of the world have either destroyed their stockpiles, or shipped them to the repositories in the US and Russia. Since that point, the UN has been pushing for the US and Russia to destroy their final (known) stockpiles. The US government has proposed that it hold off doing so for at least another five years (not centuries), during which it will spend another three billion on vaccine research.
Funny thing about mad geniuses... they're mad. I've got nothing but respect for the guy, but at times it seems he's too smart for his own sanity.
I think that would be a rectish.
IPv6 isn't very practical when you are doing low level administration, and need to refer to specific machines by IP.
Each internet subscriber gets allocated their own /64 block. That's some 18 septillion addresses for you to do with as you please.
LEDs are diodes. They require DC current to operate (unless of course you want them to flicker at 60Hz). You are already going to need that DC power supply to make them work.
Remember how everyone always uses that quote to the exact opposite of what was actually said? Gates was talking about the deficiencies of MSDOS, and how quickly it became apparent that 640KB would not be sufficient in the long term.
With standard IPv6 allocation, each subscriber would get their own /64. That means you personally have a globally addressable space on the order of four billion times large than the entire IPv4 space. You could address every atom in your house and have plenty to spare. Large companies can request up to a /48, and while that may appear to take up a significant portion of the address space, they can hand out some 250 trillion of these. Each of those original founding companies that were allocated a /8 would now get one of these instead. A large tier 1 ISP might be allocated a /32 at a time, allowing up to 16 thousand of these large businesses, tier 2 ISPs, or billions of individual subscribers. We could still allow for some four billion tier 1 ISPs with such large allotments, of which we currently have maybe a dozen.
Before APNIC ran out, we were going through addresses on the order of 20M per month. Lets say we go nuts, stop using NAT, and add all sorts of networked gadgets and do-dads, those companies that get a /48 will never in a thousand years be able to use up those 300 sextillion addresses. Even if the realities of branched networking mean they might want another block from another ISP in another geographic location, it's not going to be noticeable.
I understand what you're saying that we shouldn't be wastefully consuming these addresses, but the reality is that the address space is so large, we could be wasteful, and still have plenty of breathing room until the communication latencies make a unified internet no longer a viable option.
This is nothing more than a rectenna, scaled down to operate at optical wavelengths. Rectenna in the microwave band already operate with 85-90% usable generated electricity. The problem is that while we have electronics fast enough to rectify a microwave signal in the tens of GHz, we have nothing that even comes close to rectifying an optical signal in the hundreds of THz.
MASERs and rectenna already operate using this same principle, and similarly operate at 85% or better efficiency. Since they operate in the tens of GHz range, there are readily available electronics available to handle them.
A P90 is a weapon that you can pretty much look at, and understand that it's intended for close quarter combat, and not fancy long-distance competition shooting. It's a very business-like beast.
Except it is a bullpulp design, incorporating a 10.4" long barrel, much longer than most comparable submachineguns. That gives it significantly higher muzzle velocity and range than most traditional submachineguns.
If you think this can exhaust the IPv6 space in anything like the near term, you clearly don't understand the sheer scale of IPv6.
When you consider that LED bulb will last 20-30 times longer than an incandescent, that network connectivity is only a fraction of the cost of the incandescent bulb.
Putting control at the end of the circuit means you need a dedicated circuit to each device. This allows you to just run one circuit for all your devices.
You do realize that LED bulbs already have a DC power supply and micro-controller in them to operate, right?
Actually, they said 4 billion addresses out to be enough for the small handful of military and research operations that will ever be on the internet. They had never planned it would be opened to the public at large.
There are a few. The biggest advantage to me of NAT is it seperates out the external (ISP, out of your control) side and the internal side. What if your ISP suddenly changes that first 64bit number .. or what if you switch ISPs?
Windows has WINS and OSX has ZeroConf (Bonjour) for their own local discovery. I had thought IPv6 had some local discovery mechanism that provided name support but I can't seem to find it. IPv6 capable consumer routers will likely begin offering local DNS services, using the router discovery protocols to automatically update themselves. There will certainly be some naming mechanism. Remembering IP addresses in IPv4 was annoying, but remembering IPv6 addresses is downright painful.
As some consumer routing hardware actually has these functions as seperate chips, in some situations you can actually have a router lose it's firewall capability while still keep working.
In IPv4 with traditional NAT, this is no issue, because being non publically routed addresses they won't make it out of your segment .. with IPv6 it's suddenly public. As originally stated, NAT in this case acts as a second layer.
I don't understand why they would even have a separate firewall, much less one on a wholly separate chip. NAT inherently behaves as a stateful firewall by its very operation. I can't thing of a reason why you would want to add a second stateful firewall outside of that, unless that's to protect its own external interface. Even then, that shouldn't need any protecting, since nothing should be listening on it.
NAT is a stateful firewall. My complaint was that NAT adds features that are nothing more than a work around for a deficient service provider. At best, it provides obscurity on top of existing firewalling behavior, which as the saying goes should never be confused with security.
How much more expensive? Once in mass production, a SoC with a microcontroller, network controller, powerline modem, and relay capable of 10-20W should be doable for a couple dollars. Considering the total operating cost of a LED bulb, that's only going to be a couple percent of its lifetime cost.
We did learn from IPv4, which is why IPv6 was designed with such an ungodly large address space that we do not need to be responsible. These are not intended for the standard incandescent bulb you have to replace once or twice a year. They are intended for the LED bulbs that you install once and then never touch again.
Technically, its only 2^64. The first 64-bits define a single subscriber on the internet. The second 64-bits are auto-generated to uniquely identify a machine or device, the improved version of the 48-bit MAC address.
Unless your provider charges you per connected machine, I don't see why it would really matter. I can't believe it makes any real difference in terms of security.
Each IPv6 address consists of a local segment and a global segment. The first 64-bits are the address assigned to the house or service customer. The second 64-bits are generated locally, optionally from the 32-bit MAC address. You could have billions of lightbulbs addressed in this manner, and still only consume a billionth of the usable address space. IPv6 is the very definition of overkill. Even with foolish use of it, we're not going to run into problems until we become a large interstellar society.
The only people who would even consider running NAT in IPv6 are those who don't really understand what NAT does. Namely, that if you have the available address space, it provides no advantage over a dumb firewall set to block everything.
Their potential as a drone is very useful. You can load up surveillance or communications packages, and let them loiter for months on end. NASA experimented with this a bit several years ago, but was shelved when unexpected turbulence over Hawaii caused excessive dihedral on the wing, eventually resulting in a breakup over the ocean.
The problem with manned flight is that between the pilot, cockpit structure, controls, avionics, water, food, and waste storage, you've got several hundred pounds of dead weight that must be centrally located on the wing. Should you want to operate at altitude, you're going to need a pressurized and heated cockpit and an oxygen supply or compressor pump. The centrally located payload results in significantly higher structural stress than if it were built into the wing, or located on multiple pylons distributed across the wing.
Well it doesn't benefit them either. The fact that they are not spending it means they are getting no benefit out of it, unless they are some strange being who enjoys physically playing with large sums of cash.
It's just busybox, so you've got tftp, wget, nc, ftpget/put. The problem is there are no network drivers, so there is nowhere to go anyway.
Emacs and C compilers? Pah! A virtual machine running in javascript is mad genius unheard of since using graphics cards as software driven DVB modulators.