Content-centric networking with CCNx

Ok, but if you want this to scale, you need some sort of unique ID for your document. There's the GUID approach, but that's not human-writable in the slightest. The other option is something heirarchical, where different content producers take bits of the total namespace. Of course, this is what people call a URL... (Or at least a URI)

I'm still massively not convinced that there's anything nontrivial here. I should probably go and have a careful look at ccnx.org and see if I can work out what they're doing. (and why)