Open Problem: Human Readable Naming #7
Conversation
|
Do not forget to link to: |
| > How do people try to solve this problem? | ||
|
|
||
| - [DNS](https://en.wikipedia.org/wiki/Domain_Name_System) - One of the first widely deployed solutions for Human readable names. | ||
| - |
There was a problem hiding this comment.
@yiannisbot what are the best resources to link about how ICN approaches naming?
There was a problem hiding this comment.
Need to have a more proper look to find all the resources, but the main point is that in ICN names are used to do routing in the network (i.e., involving network routers). The NDN (formerly CCNx) project started with hierarchical, human-readable name structure, but it later became apparent that having only human-readable names is not quite an option. It's impossible to guarantee that no two users will give the same name to some content. So, eventually you will need a (logically) centralised entity (DNS-like) to keep track of these. Furthermore, most such ICN architectures assume existence of ASes and ISPs, as well as some entity similar to ICANN.
A quick collection of nice papers is below, but happy to have another look towards some specific direction/problem:
|
Merging to be continued in a consequent PR in ipfs/notes |
No description provided.