What is there to pay for?

• the authors are academics that are being paid from a grant or by their employer -- they're not being paid by the journal;
• the authors typeset their paper themselves, using TeX or a word processor;
• the reviewers are fellow academics, who are not paid by the journal (they're usually anonymous, so they don't even receive kudos for their work);
• discussion happens mostly over e-mail, which is already paid for.

So what remains is the salary of the editor and some administrative overhead, which should not be too onerous for even a minor institution.

By European standards, France is a large country (roughly 1000km across), with some rather sparsely populated areas (the Northern Alps and the Massif Central). France also has a strong tradition of massive, nation-wide infrastructure projects (we've had a comprehensive high-speed train network since the 1980s), so a nation-wide broadband infrastructure is a natural thing to do.

That thing is continent-sized, not country-sized.

You are aware that the CIA put the Iranian dictator into power in 1953, toppling Iran's democratically-elected government in the process? The 1979 "Islamic Revolution" merely replaced a dictatorship controlled by the USA with one that wasn't.

Could you please explain?

According to the network administrators I've spoken to (admittedly a biased sample), almost all the malware traffic they're seeing is over IPv4. They say they'll deal with IPv6 malware when it appears.

The closest thing to a NAT specification is RFC 2663, an informational RFC that was published a good four years after NAT got deployed. It explicitly speaks about deep packet inspection:

One of the most popular internet applications "FTP" would not work with the definition of NAT as described. The following sub-section is devoted to describing how FTP is supported on NAT devices. FTP ALG is an integral part of most NAT implementations. Some vendors may choose to include additional ALGs to custom support other applications on the NAT device.

(ALG means "Application Layer Gateway".)

Yes, it should have been called ISP-side NAT (as opposed to the more usual customer-side NAT), but the marketing people thought otherwise.

--jch

It's natural that people should be focusing on the web, but the web is really a non-issue -- we know how to proxy HTTP efficiently, so HTTP sites staying on IPv4 is at worst a minor inconvenience.

What urgently needs to move are protocols that are difficult to proxy, either because they have a complex structure (BitTorrent, SIP) or because the added latency hit is problematic (SIP, Skype, most online games). You really want enough of your BitTorrent peers to implement IPv6 support, so you can get your Linux distributions fast.

According to Wikipedia, it's 8.74×10^10 m/s^2. If you integrate that over fourty years, that's 17000 km, or 55 ms light-speed delay, which should not be too difficult to detect.

--jch

--jch

Since it's not clear from your post, the Surface (especially the crippled RT version) cannot do most of that.

See?

Thanks for your concern, but I'm quite productive on my cheap netbook — the battery lasts over 8 hours, and the keyboard is good enough for a sustained 65wpm. The only reason I'd consider a tablet is the weight: the netbook weighs 1.1kg, which is 400g more than a lightweight tablet. But I wouldn't consider anything as crippled as the Surface.

Compared to a laptop.

The netbook I currently use on trips cost €220. Since it's fully encrypted, it means that having it stolen or leaving it on the train is a fairly minor annoyance (I've had one stolen already).

Since I have a nice laptop at home and a nice desktop at work, I'd gladly replace it with a tablet, as long as I can encrypt the flash, view PDFs, run LaTeX, and plug in a projector. But not at that price.

I've always wondered why FSF Emacs couldn't implement a package system...

$ host -t aaaa lwn.net
lwn.net has no AAAA record
$ host -t aaaa arstechnica.com
arstechnica.com has no AAAA record
$ host -t aaaa tomshardware.com
tomshardware.com has no AAAA record
$ host -t aaaa phoronix.com
phoronix.com has no AAAA record
$ host -t aaaa smallnetbuilder.com
smallnetbuilder.com has no AAAA record

You're expected to have a stateful firewall at the very same place where you have a NAT right now. This is described in RFC 4864.