User:Elifarley/pds: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
== | {{category=Wireless mesh network}} | ||
A decentralized name resolution system which provides strong authentication and name | ==Peer Domain System== | ||
'''A decentralized name resolution system which provides strong authentication and prevents name conflicts.''' | |||
One of the design goals is to make it easy to share name resolution data. | |||
==Design Goals== | |||
*strong auth | |||
*prevent name conflicts | |||
*easy to use | |||
*scalable | |||
*no single point of failure | |||
*integration with existing internet infrastructure (dns, browsers) | |||
*hard to take down | |||
==Use Cases== | |||
===single record=== | ===single record=== | ||
PDR - Peer domain record - can be pasted on twitter, discussion forums, web pages, emails and so on | PDR - Peer domain record - can be pasted on twitter, discussion forums, web pages, emails and so on | ||
| Line 20: | Line 32: | ||
* | * | ||
===pdz file=== | ===pdz file=== | ||
a .pdz file has all records of a given domain. A pds client retrieves the file using a dht like kademlia, bittorrent or other p2p apps. Users can also save such files in a specific folder called pdz | a .pdz file has all records of a given domain. A pds client retrieves the file using a dht like kademlia, bittorrent or other p2p apps. Users can also save such files in a specific folder called pdz, which should be shared with everyone. | ||
<code> | <code> | ||
name#scope@signer.pdz | name#scope@signer.pdz | ||
</code> | </code> | ||
Revision as of 05:17, 13 March 2011
Template:Category=Wireless mesh network
Peer Domain System
A decentralized name resolution system which provides strong authentication and prevents name conflicts.
One of the design goals is to make it easy to share name resolution data.
Design Goals
- strong auth
- prevent name conflicts
- easy to use
- scalable
- no single point of failure
- integration with existing internet infrastructure (dns, browsers)
- hard to take down
Use Cases
single record
PDR - Peer domain record - can be pasted on twitter, discussion forums, web pages, emails and so on
#pdr domain scope record-type value expiry-date signer digest
- #pdr magic string
- domain is the name to be resolved
- scope helps prevent name conflicts
- record-type can be a, aaaa, cname
- value can be an ip, standard dns name, other pds name
examples:
#pdr openfarmtech 20110311 c openfarmtech.org 0 elifarley 2afqgwk6
- expiry is optional
- signer is optional
pdz file
a .pdz file has all records of a given domain. A pds client retrieves the file using a dht like kademlia, bittorrent or other p2p apps. Users can also save such files in a specific folder called pdz, which should be shared with everyone.
name#scope@signer.pdz