Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror

Comment: Re: The answer has been clear (Score 1) 390

by jd (#49575883) Attached to: Why the Journey To IPv6 Is Still the Road Less Traveled

Multiple IPs was one solution, but the other was much simpler.

The real address of the computer was its MAC, the prefix simply said how to get there. In the event of a failover, the client's computer would be notified the old prefix was now transitory and a new prefix was to be used for new connections.

At the last common router, the router would simply swap the transitory prefix for the new prefix. The packet would then go by the new path.

The server would multi-home for all prefixes it was assigned.

At both ends, the stack would handle all the detail, the applications never needed to know a thing. That's why nobody cared much about remembering IP addresses, because those weren't important except to the stack. You remembered the name and the address took care of itself.

One of the benefits was that this worked when switching ISPs. If you changed your provider, you could do so with no loss of connections and no loss of packets.

But the same was true of clients, as well. You could start a telnet session at home, move to a cyber cafe and finish up in a pub, all without breaking the connection, even if all three locations had different ISPs.

This would be great for students or staff at a university. And for the university. You don't need the network to be flat, you can remain on your Internet video session as your laptop leaps from access point to access point.

Comment: I'll tell you why I don't use it. (Score 5, Insightful) 359

by Lord Kano (#49557777) Attached to: Google Insiders Talk About Why Google+ Failed

Google Answers.
Google Shopping.
Goog-411.
Google Buzz.
Google Wave.
Google Video.
iGoogle.

I don't trust Google to keep it around once it's no longer in Google's best interests to do so and since social networking isn't Google's focus or primary source of revenue, I can't trust that.

It's not that I begrudge them the decision to do what's in their own best interests but I have that same decision to make and Google+ doesn't align with them.

LK

Comment: Re:280km (Score 1) 189

by JanneM (#49523715) Attached to: Maglev Train Exceeds 600km/h For World Record

For the Osaka-Tokyo route, the Shinkansen made the difference between an overnight business trip or return the same day. That made it insanely popular. With the new train, you can not just make a set of meetings; you can do a full days work and still get back the same day (even more so for Nagoya of course).

Many people here get stationed at offices in other cities for months or years, and leave their families behind. They effectively do a weekly commute, and come home only on weekends. For a lot of people this would let them get home more often or even stay home and make this a daily commute. Expensive, but on the other hand the company doesn't have to pay for a second short-term apartment and the other costs of two households.

Comment: Re: How about basic security? (Score 5, Informative) 390

by jd (#49516499) Attached to: Why the Journey To IPv6 Is Still the Road Less Traveled

IPSec is perfectly usable.

Telebit demonstrated transparent routing (ie: total invisibility of internal networks without loss of connectivity) in 1996.

IPv6 has a vastly simpler header, which means a vastly simpler stack. This means fewer defects, greater robustness and easier testing. It also means a much smaller stack, lower latency and fewer corner cases.

IPv6 is secure by design. IPv4 isn't secure and there is nothing you can design to make it so.

Comment: Re: Waiting for the killer app ... (Score 3, Informative) 390

by jd (#49516451) Attached to: Why the Journey To IPv6 Is Still the Road Less Traveled

IPv6 would help both enormously. Lower latency on routing means faster responses.

IP Mobility means users can move between ISPs without posts breaking, losing responses to queries, losing hangout or other chat service connections, or having to continually re-authenticate.

Autoconfiguration means both can add servers just by switching the new machines on.

Because IPv4 has no native security, it's vulnerable to a much wider range of attacks and there's nothing the vendors can do about them.

Comment: Re: DNS without DHCP (Score 4, Informative) 390

by jd (#49516387) Attached to: Why the Journey To IPv6 Is Still the Road Less Traveled

Anycast tells you what services are on what IP. There are other service discovery protocols, but anycast was designed specifically for IPv6 bootstrapping. It's very simple. Multicast out a request for who runs a service, the machine with the service unicasts back that it does.

Dynamic DNS lets you tell the DNS server who lives at what IP.

IPv6 used to have other features - being able to move from one network to another without dropping a connection (and sometimes without dropping a packet), for example. Extended headers were actually used to add features to the protocol on-the-fly. Packet fragmentation was eliminated by having per-connection MTUs. All routing was hierarchical, requiring routers to examine at most three bytes. Encryption was mandated, ad-hoc unless otherwise specified. Between the ISPs, the NAT-is-all-you-need lobbyists and the NSA, most of the neat stuff got ripped out.

IPv6 still does far, far more than just add addresses and simplify routing (reducing latency and reducing the memory requirements of routers), but it has been watered down repeatedly by people with an active interest in everyone else being able to do less than them.

I say roll back the protocol definition to where the neat stuff existed and let the security agencies stew.

Comment: What is wrong with SCTP and DCCP? (Score 4, Interesting) 84

by jd (#49503031) Attached to: Google To Propose QUIC As IETF Standard

These are well-established, well-tested, well-designed protocols with no suspect commercial interests involved. QUIC solves nothing that hasn't already been solved.

If pseudo-open proprietary standards are de-rigour, then adopt the Scheduled Transfer Protocol and Delay Tolerant Protocol. Hell, bring back TUBA, SKIP and any other obscure protocol nobody is likely to use. It's not like anyone cares any more.

Comment: Re: Must hackers be such dicks about this? (Score 1) 270

by jd (#49500235) Attached to: FBI Accuses Researcher of Hacking Plane, Seizes Equipment

He claimed he could hack the plane. This was bad and the FBI had every right to determine his motives, his actual capabilities and his actions.

The FBI fraudulently claimed they had evidence a crime had already taken place. We know it's fraudulent because if they did have evidence, the guy would be being questioned whilst swinging upside down over a snake pit. Hey, the CIA and Chicago have Black Sites, the FBI is unlikely to want to miss out. Anyways, they took his laptop, not him, which means they lied and attempted to pervert the course of justice. That's bad, unprofessional and far, far more dangerous. The researcher could have killed himself and everyone else on his plane. The FBI, by using corrupt practices, endanger every aircraft.

Comment: Re: Must hackers be such dicks about this? (Score 1) 270

by jd (#49500221) Attached to: FBI Accuses Researcher of Hacking Plane, Seizes Equipment

Did the FBI have the evidence that he had actually hacked a previous leg of the flight, or did they not?

If they did not, if they knowingly programmed a suspect with false information, they are guilty of attempted witness tampering through false memory syndrome. Lots of work on this, you can program anyone to believe they've done anything even if the evidence is right in front of them that nothing was done at all. Strong minds make no difference, in fact they're apparently easier to break.

Falsifying the record is self-evidently failure of restraint.

I have little sympathy for the researcher, this kind of response has been commonplace since 2001, slow-learners have no business doing science or engineering. They weren't exactly infrequent before then.

Nor have I any sympathy for the airlines. It isn't hard to build a secure network where the security augments function rather than simply taking up overhead. The same is true of insecure car networks. The manufacturers of computerized vehicles should be given a sensible deadline (say, next week Tuesday) to have fully tested and certified patches installed on all vulnerable vehicles.

Failure should result in fines of ((10 x vehicle worth) + (average number of occupants x average fine for unlawful death)) x number of vehicles in service. At 15% annual rate of interest for every year the manufacturer delays.

Comment: Re:Wasn't quite the revolution ... (Score 1) 134

by JanneM (#49481743) Attached to: Chinese Ninebot Buys US Rival Segway

I appreciate your idea, but I don't think it's that good a fit for the Segway.

People that can't walk a mile most likely needs their own assistance tech - a walker, a wheelchair - on the bus or train as well. And people that don't have time to walk a mile or two won't be helped by a thing that barely moves above walking speed. A bicycle rental spot (or free city bikes) would be more helpful and less costly.

How can you do 'New Math' problems with an 'Old Math' mind? -- Charles Schulz

Working...