mesh.cat/meshname
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update protocol.md

Browse Source
This commit is contained in:
George 2020-03-24 07:37:30 -04:00
parent 737f7373bd
commit f7a59668ed
1 changed files with 2 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
protocol.md
View File

@ -5,8 +5,8 @@ Special-use naming system for self-organized IPv6 mesh networks.
## Motivation
Having a naming system is a common requirement for deploying preexisting
decentralized applications. Protocols like e-mail, XMPP and ActivityPub require
domain names for server to server communications.
decentralized applications. I.e., applications for e-mail, XMPP and ActivityPub
require domain names for server to server communications.
Self-organized networks like CJDNS and Yggdrasil Network use public-key
cryptography for IP address allocation. Every network node owns
@ -63,14 +63,3 @@ For "aiag7sesed2aaxgcgbnevruwpy.meshname." the authoritative server is
"200:6fc8:9220:f400:5cc2:305a:4ac6:967e".
The resolver then relays clients request to a derived server address and
relays a response back to the client.
## Why not .ip6.arpa
There is a special domain for reverse DNS lookups, but it takes 72 characters to
store a single value. The same value in .meshname takes 35 characters.
"e.7.6.9.6.c.a.4.a.5.0.3.2.c.c.5.0.0.4.f.0.2.2.9.8.c.f.6.0.0.2.0.ip6.arpa"
versus "aiag7sesed2aaxgcgbnevruwpy.meshname"
This saves twice amount of bandwidth and storage space. It is also arguably more
aesthetically appealing, even though that's not a goal.