That does not mean that Denmark will pay you any damage on your house. It means you get to sue me under danish law. The danish citizen (me) will then pay you the damages, if so determined by the danish judge.

All the other speculation such as a $100 million USD bounds has no basis in danish law and so will not be required. If I can't pay you, that too will play out accordingly to danish laws. Most likely that means it is just too bad for you. You wont be getting anything from the danish government either way.

It is the only way a civilized country can act - by following the laws by that country. A country is not a person that you can say "they owe me because the treaty says they are responsible" - you are only owed money if the laws of the country concur. And let me tell you right ahead, there are no laws in Denmark to the effect that government will step in and pay damages on behalf of a citizen if said citizen is unable to pay. And neither is there any such law in the US to my knowledge. If a SpaceX rocket drops on my car, I get to sue SpaceX in an american court for a new car.

Your tiny DSL would be overwhelmed by even the smallest DoS attack imaginable. You would not be getting 1 or 2 Mbps - you would be getting absolutely nothing through at all.

It is more likely that your DSL is having trouble delivering the usual 16 Mbps due to electrical interference. Your ISP may be able to fix it by lowering your speed, which sucks, but it might be more stable. Or there might be nothing that can be done unless you can locate the source of the noise. Trouble is that the source might not anywhere near your home.

I dont know what the robot would do. But you on the other hand would hit the baby and then crash after realizing that you just hit a baby.

By this point you are being tracked as the guy that blocked everything else. There is only going to be one of you.

DHCP is not used on home routers with ipv6. Your devices pick random addresses using privacy extension and duplicate address detection.

There are actually 2^128 possible IPv6 addresses. Ok, then you can cut it down by looking at BGP etc as proposed. But consider that the minimum IPv6 network every user gets is a /64 = every user has 2^64 addresses on his home network, just scanning one single user is not feasible. Not to even think of scanning the entire internet.

You can split an IPv6 address into blocks. The first 32 bits tells you what ISP. This is the part where the BGP trick can help. The next 32 bits is the network number. And the remaining 64 bits known as the interface identifier are more or less random assigned by the computers.

You can assume that the user router will respond to the all zero interface identifier. It would therefore be feasible to scan the routers. Every single ISP would take as long as scanning the entire IPv4 internet. But that means they could do it in 45 minutes apparently (longer for bigger ISPs with more /32s). Of course the routers should be configured to ignore anything from outside, but so should the IPv4 routers.

But actually hitting peoples computers, printers and so on, even assuming no firewalls, is simply not possible. It is not even the bandwidth of the attacker that limits you, but the bandwidth of the target user. How long would it take to transfer 2^64 packets down the average users crappy DSL?

On top of that you get privacy extension. This is a system where your computer changes address at random at regular intervals (at least once a day). If you did spend millions of years to do a scan, you would very likely never find a working address because the targets are moving.

EV batteries deteriorate just like all other batteries. What you want to ask is how fast? That depends entirely on what car. Just like the batteries lasted much better on his old Mac.

Because the EV battery is such an expensive part of the car and a car is expected to last much longer than a laptop, they will do more to make it last longer. One trick is to stop charging at 80% and never go below 20%. Laptops will happily go to 100% even knowing this will kill the batteries quickly. And the user might run

Another is to climate control the battery. More expensive EVs like Tesla has climate control on the battery, so it will always be at optimum temperature. I have never seen a laptop with this feature. Nissan left this out on the first Leaf and got in a lot of trouble when the batteries started to deteriorate too fast in Arizona.

You should also remember that less capacity is not the same as failed. You probably would not replace the battery in an old EV just because it has shorter range now. Instead you sell it to someone who is fine with the shorter range. You will pay for it by getting a lesser resale value, but this is still cheaper than replacing the battery.

The 12V battery in an ICE car is something completely different. You can not assume that EV batteries will fail in 5 years, just because your 12V battery is crap. In fact may EVs come with 8 years of warranty on the battery.

Almost all Toyota Prius all the way back to the 1997 models are still running on their original battery.

This is not about getting 100 Gbps to your home. It is about building ISP networks with faster links. They are apparently not even trying to invent the 100 Gbps technology, they are just going to find out how it can be managed in a large network.

The ZDNET article only shows that Google has a /32. I own a /32 too so that is not extraordinary in any way whatsoever. In fact every ISP gets a /32, that is the minimum allocation these days...

The Royal Pingdom article lists Sixxs as the source. That would be the same link as I initially provided and which now lists the /13 as "returned". In fact it was never allocated, that was just some person that made that interpretation on his own.

The Royal Pingdom article does claim that the next largest allocation is a /19 to France Telecom, so no foundation for a /16 to Google there. I find it likely that the /16 rumour is just someone mistaking a /32 for a /16. It is an easy enough mistake to make. Google does have at least a /29 from RIPE but no /16 or anything like that.

The DoD assignment does seem a bit excessive. But they are the exception not the rule. I also wonder what ARIN can really do when the government of the US tells them to jump. The only thing they can do is to ask "how high?".

The RIRs always spreads the assignments so there is nothing strange in that. The idea is that if one of those /22 some day would need to be expanded, that is possible because there likely will be no adjacent assignment. This does not mean the space is reserved as such. If the world some day is lacking address space they will start allocating that space to somebody else.

It is also quite possible that IANA will ask ARIN to use some more of that /13 before ARIN can get more space from IANA.

I was partly wrong in my first response. The Sixxs guys does not seem to keep proper track of things. Here is the allocations that the US Department of Defense has:

http://whois.arin.net/rest/org/USDDD/nets

They got 22x /22. However whoever calculated that equals one /13 is mistaken. It equals 69% of a /17. You need a bit less than 5 bits to express 22 nets. Apparently some guy noticed that most of those 22 networks were allocated from the same /13 block, but that in no way means the remaining of that /13 is reserved to DoD. If it was it would have been allocated to them.

There seems to be no foundation for the claim that Google got any exceedingly large allocations. They got two /32 from ARIN: http://whois.arin.net/rest/org/GOGL/nets

Google also got a /29 from RIPE. And possible more similar sized networks from other regions, which seems reasonable given their size.

Can you tell us what to the Google /16 block is? If not we can assume this is just wrong.

The /13 was returned. The largest allocated prefix is currently /19: http://www.sixxs.net/tools/grh/dfp/

The internet is the _only_ connection my TV has. I skipped buying cable and terrestrial is not an option here.

It just happens that my TV can actually show a lot of TV content with just Internet. The national TV is available as streaming. And I got Netflix and HBO Nordic. I am never going to buy cable again.

Comparing the TV to the fridge, toaster and toilet is so misguided. The TV has a very real reason to be on the internet: The internet is the pipe to entertainment that I am viewing on the TV. It is the coax port on the TV that is going to be obsolete in the future. Already people like me are not using it anymore.

I want to se your C code for this simple Haskell function:

f x y = x*y

When applied to just one argument:

g = f 5

You get back an one argument function that will multiply by 5:

g 4 equals 20.

h = f 10

h 4 equals 40.

Your task is to write a C function, that does not memory leak (although it is hard enough even if you are allowed to leak), that based on some parameter will return a another function that is different each time. Like in the above Haskell code, I shall be able to invoke your C function multiple times, for example with the values 5 and 10 and get back new functions that will multiply with 5 and 10. The later must of course not override the behaviour of the former.

The article was written by the guy that did the driver, I think we can assume he knows his stuff.

No it appears that if you want to switch more than 10-18 Gbit/s the computer would have a memory bandwidth problem. Trying to use multiple cores and NUMA might improve on that, but I do not think you would manage to build a 24 port switch that switches at line speed this way :-).

But if you could somehow get an external switch to do 99% of the work, this might work...

I am not sure how much more we can get out of this discussion. From my side I believe you are going too far in trying to make a problem out of something that actually works quite well for some very large companies (Google and HP!). Packets need to be delayed when the controller needs to be queried and that is true for both OpenFlow and traditional switches. We are just fighting over some nano or possible microseconds here with no one showing that it actually matters. It very likely does not matter for the use case that Google uses for, or they wouldn't be doing it. At my company we are using it too and it works very well for us. We are an ISP by the way.

There might indeed exist a work case where a 10G flow just pops into existing out of nowhere and where even 1 microsecond delay on the forwarding of that stream is not acceptable. I am just having a real hard time imaging that case.