According to this interesting article:
The fundamental idea behind Content Centric Networking is that to retrieve a piece of data, you should only have to care about what you want, not where it’s stored. Rather than transmitting a request for a specific file on a specific server, a CCN-based browser or device would simply broadcast its interest in that file, and the nearest machine with an authentic copy would respond. File names in a CCN world look superficially similar to URLs (for example, /parc.com/van/can/417.vcf/v3/s0/Ox3fdc96a4…) but the data in a name is used to establish the file’s authenticity and provenance, not to indicate location.
Such changes could make things much more interesting for the years to come. Instead of worrying about where content was stored, you simply have a cache in your house that hosts all of your files and ask for them… Once they are found they are delivered to your desktop. If they are not on your local network, they can be downloaded from the internet, cached, and delivered to your desktop or mobile device… which would reduced much congestion on the internet.