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.)
which is a bad thing.
It would be less of a bad thing if IPv4 connectivity (specifically: what ASN was advertising the IPv4 prefixes your traffic was associated with when it traversed, say, Telecom Malaysia) wasn't the sine qua non of global connectivity, in the same sense that nobody cares what IP address you use when you connect to IRC.
Unless someone is using it already.
Then you need to choose another port.
Which you need to communicate to the other clients behind the NATs around the world. Fine, we'll just update the DNS server with an SRV record. You probably will always have a spare public IPv4 address to map the ports 53 to something on the inside network, so this might work.
Until your CGN does not have enough IPv4 addresses/ports to permanently allocate one to you. Oh, by the way this is a great way to introduce a "premium" tier service with a public IP address - if you really want to run a server then you can buy an address. So doing the PBX-style circuit switching with NATs is not really in the economic interest of the ISPs. (Not saying that they need to do all the accounting/logging).
If the app is awesome enough that the users will pay extra to get the public address - great.
That will help to further exhaust the IPv4 addresses and drive the prices up. Rinse, repeat.
I am of course exaggerating.
But this presentation from NANOG may be a less biased view (though Lee's employer does deploy IPv6, so you can argue it is biased):
http://www.nanog.org/sites/default/files/wed.general.howard....
Full disclosure: I am into this IPv6 thing. Before that, I spent ~10 years of my life at a random 5-letter vendor to find the bugs in the code and misconfigurations causing outages in people's NATs. It's refreshing to be able to use access-lists again. (the latter statement is only partially correct, but this is a topic for another rant, IPv6 has tons of its warts as well :-)
(I am actually opposed to overlays uber alles, partly because I think it may actually happen.)
A --- |> --- <| --- B
then getting from "A" to "B" is not easy. And the "cones" may be of varying degree of aggressiveness when it comes to filtering [1]. You can not guarantee that you can always establish connectivity between the two, even in a presence of the third party - with the addresses being more and more precious, the SPs will move from full-cone to more restricted NAPTs.
Besides these hurdles, moving large volumes of traffic atop overlays is not very optimal - I heard anecdotes that when Tor is abused in this manner, it is quite slow. Skype (and I guess probably Tor as well) uses supernodes that are not behind the NAPT to establish the communication. As there is less and less places for it.
So, the quality of communication over overlay degrades more and more.
Meanwhile, the bigger players will just place the caches close to eyeballs or directly peer with the eyeball providers. [2]
So, I think Lee's scenario is quite plausible.
Pretty much the only things keeping holding IPv4 in my home network are the client device bugs [3] and Skype. The web works quite well on DNS64.
I think the economics will take care of things. There are users on IPv6. A few clever interns last year made a website [4] that aggregates various IPv6-related stats. Take a look at the situation with users e.g. in Germany, Belgium, Switzerland. Yes, it is still not a whole lot but it is growing - and these three give the impression of how it might happen - sometimes steady, sometimes the switch will just turn on.
I am very curious to hear some VC chime in on this matter - what do they think about the prospects of business growth in the situation of the constrained address space and uneven competition. It is not the case today because ARIN still has numbers. Give it a couple of years.
[1] https://en.wikipedia.org/wiki/Network_address_translation [2] http://blogs.broughturner.com/2009/04/googles-peering-and-ca... [3] https://ripe66.ripe.net/archives/video/1196/ [4] http://6lab.cisco.com/
I think a lot of crappy 1980s protocol architecture is based on a fear of forwarding packets that (to invoke a shorthand) Moore's Law has addressed for us.
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.
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?
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?
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.
I made the comment based on the fact that the only thing you ever talk about actually doing is security-related. On everything else, you just pontificate context-free.
You implied earlier I should have looked at your "public linkedin profile". You should know that, for me, your profile contains nothing but your current and past employers, and your university. Nothing about what you did there. What was I supposed to conclude from that?
I've spent most of my career working for companies that do video-related work, but if you ask me a question about MPEG transport streams, I'll refer you to the guy who, y'know, actually deals with MPEG.
At this point I am pissy, yes, but that's not because I was wrong, it's because of the asshole who decided he knows better what my personal time commitments are than I do.
> The thread is now full of technical commentary about the point I made.
No, it isn't. The thread is full of cursory rejections of your equally cursory commentary. There is absolutely nothing interesting about any of it, because it's all surface bullshit that everybody already knows. There are no details. There's nothing concrete. There's nothing new. Boring, hand-wavy crap.
Propose something concrete, something that actually addresses the obvious criticisms you already know are going to be leveled, and I might get interested.
Right now, all I'm interested in is ignoring HN for a while.
Have a good weekend. Ignoring HN can definitely be a healthy thing sometimes.
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.
And I'd be happy to shoot down your ideas, if you had any. All you have is your regular content-free rant against IPv6 that you constantly re-post.
> Half this site seems to think I'm a secret government agent.
No, we just think you're a strict authoritarian who gives the American left a bad name.
https://news.ycombinator.com/item?id=5587264
https://news.ycombinator.com/item?id=3408523
All you've said so far is "Boo! New ideas bad!"
But neither thread is one of substance, only complaints and a vague "we need a general overlay network". Not one word about what it should look like. How it should work. Nothing.
If you want to argue about an idea, articulate one.
Edit: I see in the second thread you actually did say something about a directory service, so I guess that is one word. But as far as I can tell, you just described yet-another-DNS-replacement. If I were generous, maybe I would call it an Active Directory competitor.
Boo! You continue to say. New ideas bad! How dare you, of all people, assault the old ideas!
Edit: Ah, you've edited it to clarify. You're just going to be your usual self. How disappointing. Broadly speaking, you're an interesting, intelligent person I would love to know better and to learn from. But you can't stop yourself from being the get-off-my-lawn guy.
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.