6 ms·
It's already 2013, so that's an aggressive schedule; it seems to imply the next-hop tech must already exist. Did you have something in mind? (Tone: Honest ques
by jerf 13y ago
It's already 2013, so that's an aggressive schedule; it seems to imply the next-hop tech must already exist. Did you have something in mind?
(Tone: Honest question. I'm curious.)
- ghshephard 13y agoThere is no candidate to replace IP for global routing connectivity in the next 20 years. I'll wager a long-bet at 10 to 1 odds up to $1,000 (you win $10,000) for anybody who thinks differently.
- tptacek 13y agoOk. Done. My email is in my profile.
- nknighthb 13y agoThomas always says this whenever IPv6 comes up. He wants some sort of "overlay" network. He's ambiguous on what this would look like, why it would be better than IPv6, and why IPv4 will suffice as its underlying protocol. My conclusion is that his application-level networking experience has fooled him into thinking he knows more than he does about actual network architecture, management, and performance issues. Or maybe he doesn't realize the issues even exist.
- JoachimSchipper 13y agoUm, you're aware that he wrote http://insecure.org/stf/secnet_ids/secnet_ids.html http://insecure.org/stf/secnet_ids/secnet_ids.html, worked for a networking (security) company (Arbor) for years, etc.? He may be wrong, and he may think that he knows more than he actually does, but he does know a thing or two. ;-) Regarding overlay networks: note that HTTP, WebSocket, Skype, BitTorrent and such are already looking quite a bit like an overlay network, and that increasing amounts of NAT-ting are making the classic point-to-point model of the internet more and more irrelevant. I'm not sure I particularly like this vision of the future, and I agree that the performance will be worse, but it's far from insane. (As to performance, note how everything is routed over HTTP these days, despite it being rather inefficient for lots of use cases.)
- nknighthb 13y agoForgive me, as I don't have time at the moment to review the paper in detail, but none of what I see skimming through it really contradicts what I already believed. Knowing how the protocols work is not the same thing as knowing how to architect and manage large networks. The "overlay" networks you speak of are already hamstrung by the shrinking ability to directly address endpoints on the Internet. IPv4's fundamental flaws when applied to billions of nodes cannot be papered over forever.
- wglb 13y agoI don't have time at the moment to review the paper in detail, But you have time to make multiple complaints about tptacek not knowing what he is talking about? May I suggest you withdraw from this line of argument?
- nknighthb 13y ago> May I suggest you withdraw from this line of argument? May I suggest that you look at the paper in question and realize it is one that requires careful and uninterrupted attention for an extended period of time to properly understand? May I also suggest that you not make assumptions as to what another person is or is not doing, and how it may interfere with their ability to do some things but not others? Or would you rather just be a judgmental, holier-than-thou asshole?
- tptacek 13y agoAs a reminder, this is what you said upthread: My conclusion is that his application-level networking experience has fooled him into thinking he knows more than he does about actual network architecture, management, and performance issues. Or maybe he doesn't realize the issues even exist. My conclusion is that you made that comment having absolutely no idea what my experience was, and then decided to get pissy when the facts didn't line up with your bet. I've made the same dumb bet on HN a bunch of times. "This is just some Ruby dork who knows fuck all about", I don't know, "tax law". It never works out for me, either. The thread is now full of technical commentary about the point I made. Lots of smart people disagree with me; no surprise! You've contributed none of that commentary. Maybe now's a good time to start? You seem to feel passionately about the issue.
- tptacek 13y agoWell, let's see. I ran all of technical operations for Chicago's most popular indie ISP, up through the point where we were default-free BGP4 peered, in the era where every customer connection every day was an OSPF recalculation. Then I took a job that required me to write the clientside for every protocol exposed on a "modern network" circa 1996, including FTP, TFTP, NFS, SunRPC, DNS (for which I had to write 3 different recursors and an authority server to do serverside-serverside testing), RIP(!), and lord knows what else. Our product was a network security scanner, before there was Nessus, that worked by actually testing for bugs instead of doing banner grabs. I moved to a research role in that job and built a testsuite for network intrusion detection systems based on a line-by-line audit the 4.4BSD IP stack, then used it to reverse engineer the behaviors of the Windows NT and Solaris (then closed-source) IP stacks, and used that to discover (with my then-partner Tim Newsham) 3 new classes of attacks/bugs on network observation tools. Incidentally: I did that research because I have an ethical problem with unchecked network surveillance. Half this site seems to think I'm a secret government agent. Then I started, with two friends, a chat company that pivoted into multicast content delivery. My role on the dev team was the routing system, which implemented a multicast link-state routing protocol and a multicast service model comparable to PIM; I was also the project manager for our global traffic management system, which took full BGP4 feeds from the networks of friends of mine that ran backbones, and used them to compute anycast DNS results. When that company failed because our VCs and the CEO they installed decided we should go head to head with Akamai and invest all our money in global colocation fees, I thought long and hard about where to go next and decided I didn't yet know enough about networking. So I took at a job as the team lead for Arbor Networks Peakflow DOS, an anti-DOS product now deployed on the backbones of to a first approximation all the Internets. Peakflow worked by consuming NetFlow records from the backbone Cats and GSRs of companies like AT&T; ie, it binned and computed stats for a large percentage of all the packets traversing the--- what would you call it? Yeah, the Internet. Your call whether my career experience as a network designer, a network operator, a provider of network management and performance monitoring tools, and a kernel network software developer is germane to the discussion. Have we dispensed with the part of this thread where we wonder whether I have any business having ideas about how the Internet might work, and move on to the part where you actually try to shoot down those ideas? The former conversation is irritating, because I'm re-explaining things you could have found out simply by reading my public LinkedIn profile. But I would love to be proven wrong on my ideas; that would involve me actually learning something. I think you now owe me your best shot at taking down the actual notion of a next-gen Internet built as an application-layer overlay.
- tptacek 13y agoSince I'm randomly coining terms here, let me try to be clearer. When I talk about next-hop transport, I mean, "the mechanism by which one node might connect to one or more other nodes in the topology". As soon as those hops form a connected graph --- a very easy problem to solve when your connection fabric is datagram delivery on IP --- routing over the topology is a Solved Problem. Think of what I mean by "next hop transport" as "the lowest common denominator of connectivity that allows any 2 hosts in the world, possibly by means of some number of intermediate hops, to talk to each other". Then, to be clear about what I'm saying --- though this is probably not how you'd design such a system in the real word, imagine we did this: * Stopped fussing about IPv6 (and IP multicast, although we've already stopped fussing about that). * Took IRC * Made it 8 bit clean and capable of delivering much larger messages. * Gave it a real routing protocol so that it could express biconnected graphs. * Built applications on top of that. That system would provide a service model that would be compatible with a superset of all Internet applications today --- it would allow point-to-multipoint applications along with point-to-point applications, it would admit to client-server, it could express caching and CDN topologies, and it would admit to logical addressing that would enable you to attach to lots of different endpoints on the network with the same, static address, in the same way as I can talk to you now on HN as "tptacek" despite the fact that my IP address is temporarily owned by GoGo Inflight.
- jerf 13y agoThank you for the clarification. I did not intend for it to explode like that... but I'm on the Internet, so I'm not surprised. I think I also see where you're going with this; we've got so many adhoc implementations of this already (I'll toss on XMPP as another example) that some sort of eventual agreement and standardization seems inevitable. Don't know where it'll come from or what it will look like, but Historical Imperative is calling for it.