Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
Check out the new SourceForge HTML5 internet speed test! No Flash necessary and runs on all devices. ×

Comment Re:Pretty cool (Score 1) 117

For most places and efficient low cost configs, I'd say maybe 30-40/year in energy cost.

The upload bandwidth is killer. The performance of accessing the media is terrible (when I access a local rip, it's super high quality and *instant* seeking, versus streams from netflix and the like.

Comment Re:Bit fields (Score 1) 115

Actually, I'd say it would be more of a nightmare. Here we have the devils we know. In that scenario, it would be hellish even *knowing* what can't handle things.

Every hop in the network not being certain whether the next hop could or could not handle the conversation would be a nightmare in the making.

Comment Re:Bit fields (Score 1) 115

It seems funny, because that *ultimately* is the reality of IPv6.

The difference is that in the above scheme, *knowing* whether a hop in the network could or could not do 'big addresses' would be more difficult. With IPv6, it allows things to be very clearly delineated whether the communication is IPv6 capable or not.

The biggest obstacle to IPv6 was the stubborn resistance to any form of NAT. That IPv6 should be all or nothing. The piece needed to make IPv6-only *clients* possible was carrier grade NAT64. Yes, on the server and as a carrier, you need IPv4 *and* IPv6, but the vast bulk of endpoints can be IPv6-only now, taking the pressure off of IPv4. Of course this would have been nice to do a decade ago instead of the last two years or so, so that new servers could have a more comfortable time getting IPv4.

Comment Re:Crypto? They *removed* that from IPv6... (Score 1) 115

I personally would rather *not* have crypto at the IP or TCP layer. Reason being is that in practical terms, updates *must* be delivered through kernel updates. Given the nature of crypto updates, I'd much rather have librariers in userspace be the channel for updates.

I don't think I need a big conspiracy about AH/ESP. They were really awkward approaches, and largely redundant with higher layer strategies.

The issues with DNS/DNSSEC are more reasonably addressed in the DNS layer. There is a lack of will to tackle that problem, but that's the same lack of will that would make implementing at a lower layer impractical as well.

Comment Re:I manage Internet connections in 148 locations. (Score 1) 115

When I pull up my cell phone ip information, it's IPv6.

Now that there's carrier-grade nat to allow ipv6-only endpoints to speak to ipv4-only hosts, it *finally* is plausible to offer most mobile/residential ipv6-only. So a lot of the people who are ipv6-only are precisely the ones that would never realize it.

For enterprise networks and internal networks, those are ipv4 and likely to stay ipv4-only (which is a bummer for software development, because IPv4/IPv6 agnostic code is still relatively rare, since there's so many subtle bugs trying to use AF_INET6 for both, and it's more complicated to have both AF_INET and AF_INET6 addresses).

Comment Re:acrobat reader dc, for those that want... (Score 1) 17

It's an inefficiency that is very intentional.

The software industry realized that for a lot of their users, they couldn't extract upgrade licenses from customers readily because they had already done *too* good a job. Functionality wise, a lot of people don't need anything newer than Photoshop 6 (released 16 years ago). A lot of people could use Office 97. Of course some things have slowly evolved technology wise that *ultimately makes people need updates and there's some forced updates (e.g. fun incompatibilities in ms office formats), In general though, update revenue became a big uncertainty.

So the solution is to switch to rental models, subscriptions, et al. Licenses that terminate when you stop paying, rather than the 'old' way of transactional purchase that has indefinite usage rights.

Now a software company can much more efficiently milk their userbase for money without really having to figure out meaningful value add beyond what they already do.

Comment Re:And how many (Score 3, Informative) 117

And how many are still running Win 7

Well as of last week StatCounter puts Win7 at 39.46% and Win10 at 24.33% of the desktop OS market share, of course that's not all devices running Win10. But a whole lot and after the free offer ended there's not been much migration at all. I suspect Win7 will be even harder to kill than WinXP and that wasn't easy.

Comment Re:Bit fields (Score 1) 115

that probably would not have made much of a difference. People would have assumed that this would never happen and would have made practical implementation assuming a fixed 32 bit space. By the time it became a practical problem, we would have had a creep of devices that does not follow the norm, and managing that would be a nightmare.

Yes, but it would have put more pressure on the existing user base like Y2K compliance to follow the "full" standard. Right now it's like we're on IPv4, tagged WORKS4ME so why bother with IPv6. But I know I've made many more "shortcuts" than limiting something to 4 billion...

Comment Re:This isn't really that hard to understand (Score 0) 597

Given this, attacking on the basis of "CLIMATE CHANGE" is the absolutely worst approach. The ignorance of your target audience will prompt them to respond contrary to your goals. Instead focus should be placed on the specifics; clean air emissions, water discharge standards, ect... Why? Because these are things people can understand, and they are immediately relevant to them.

You're breathing CO2 right now, it's "only" 0.04% but pretty much anything that is actually toxic would have killed you at those concentrations. The Apollo 13 astronauts remained functional at 2%, even 5% isn't usually fatal and it's actually the absence of oxygen that kills you not the CO2 itself. Not to mention it's essential for photosynthesis so plants grow, it's far from obvious that CO2 emissions are bad for the local environment. Pretty much all the bad things that happen locally are from things that are not CO2, like CO from unclean combustion, NOx and various other particles that get whirled into the air. It's not like humans shy away from a fireplace...

Comment UTF-8 style would have been better (Score 3, Insightful) 115

So the 1992 UTF-8 specification didn't exist when the 1983 IP specification was created, but they could have done:

First 2^31: 0(31)
Next 2^59: 110(29) 10(30)
Next 2^88: 1110(28) 10(30) 10(30)
Next 2^117: 11110(27) 10(30) 10(30) 10(30)

And just declared that for now it's 0(31) - still 2 billion addresses but the sky is the limit. Heck, they might even have used shorts (16 bit) that way and declared that hardware/software should update as the need approached:

First 2^15: 0(15)
Next 2^27: 110(13) 10(14)
Next 2^40: 1110(12) 10(14) 10(14)
Next 2^53: 11110(11) 10(14) 10(14) 10(14)
(...)
Next 2^140: 1111111111111111(0) 10(14) 10(14) 10(14) 10(14) 10(14) 10(14) 10(14) 10(14) 10(14)

As for PKI, that couldn't possibly have happened. US export regulations wouldn't have allowed it at the time, this was long before Zimmerman and PGP.

Slashdot Top Deals

If you're not part of the solution, you're part of the precipitate.

Working...