In my vague understanding of TCP, I thought that the retry timers were supposed to have a random element to them. In fact, some systems talk of using cryptographic random sources so that the delays aren't predictible.
If that isn't the case in implementations, it would seem to be implementation error, not really a fault with the protocol itself.
Remember, though, we have multiple cellular technologies in use in the US. They would probably have to provide several different services to make it useful for people.
There also still is the in-flight phone that many planes have now.
Although the airlines, and the FAA might end up not carring about cell phones in use while in flight, the cellular carriers certainly will.
The whole concept that allows cell phones to work (that the signal strength at distant cells will be much weaker) only works when all of the phones are close to the surface of the earth. When the users are above the surface significantly, the relative distance between the user and multiple cells isn't very much.
A single user in a airplane making a cell call could easily consume the resources that a few hundred users would on the ground.
Filling the sky with people talking on cell phones could easily render most cell networks nearly useless.
Re:Way too dumb-downed - no real info here
on
The Basics Of RAM
·
· Score: 1
Although I wouldn't be quite so harsh on them as that, it does annoy me when articles attempt to simplify something, and end up being wrong.
I'm sorry, but EDO, fast page and the like are not methods for refreshing less, but ways to get the data out of the device faster.
Perhaps explaining that reading DRAM is destructive would help understanding as well.
Slashdot Mirror
So, reading other information, it looks like they're desciring just a weakness in the multicast support, which as far as I know, is rarely used.
I don't expect an attack like this to be able to effect me.
In my vague understanding of TCP, I thought that the retry timers were supposed to have a random element to them. In fact, some systems talk of using cryptographic random sources so that the delays aren't predictible.
If that isn't the case in implementations, it would seem to be implementation error, not really a fault with the protocol itself.
Remember, though, we have multiple cellular technologies in use in the US. They would probably have to provide several different services to make it useful for people.
There also still is the in-flight phone that many planes have now.
Although the airlines, and the FAA might end up not carring about cell phones in use while in flight, the cellular carriers certainly will.
The whole concept that allows cell phones to work (that the signal strength at distant cells will be much weaker) only works when all of the phones are close to the surface of the earth. When the users are above the surface significantly, the relative distance between the user and multiple cells isn't very much.
A single user in a airplane making a cell call could easily consume the resources that a few hundred users would on the ground.
Filling the sky with people talking on cell phones could easily render most cell networks nearly useless.
I'm sorry, but EDO, fast page and the like are not methods for refreshing less, but ways to get the data out of the device faster.
Perhaps explaining that reading DRAM is destructive would help understanding as well.