First, don't read apenwarr for the info, read the paper.[1] Unfortunately, that still won't carry you that far because there's a whole lot of "community knowledge" that is carried in DS papers that you don't get unless you read a lot of them or are in the community.
CCN is not an actual proposal. It's a pie-in-the-sky networking redesign.
Do you know what would be required to implement CCN? Go read the paper. The hardware cost alone is insane. This is not coming any time soon. Be prepared for IPv6 for the next 20 years at least.
I'll take your word for how pie-in-the-sky CCN really is, I skimmed through the paper without a critical eye. However ...
> Be prepared for IPv6 for the next 20 years at least.
I have, for the last 10 (or more?) I think it was 1999 when I was thinking "I should probably implement IPv6 in this project, because next year it's going to be everywhere".
I think you mean "be prepared for IPv6 to be the up-and-coming protocol for the next 20 years at least".
Maybe not CCN, but I suspect it's more likely that a killer-app with it's own tunnelled-in-IPv4 protocol is more likely to take over than IPv6. BitTorrent had a chance to do that, but didn't. I can't point to the next one myself.
First, don't read apenwarr for the info, read the paper.[1] Unfortunately, that still won't carry you that far because there's a whole lot of "community knowledge" that is carried in DS papers that you don't get unless you read a lot of them or are in the community.
CCN is not an actual proposal. It's a pie-in-the-sky networking redesign.
Do you know what would be required to implement CCN? Go read the paper. The hardware cost alone is insane. This is not coming any time soon. Be prepared for IPv6 for the next 20 years at least.
[1] http://sites.google.com/site/zhongrenshomepage/Networking%20...