User:Elifarley/pds: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 19: | Line 19: | ||
*signer is optional | *signer is optional | ||
* | * | ||
=== | ===pdz file=== | ||
a . | a .pdz file has all records of a given domain. A pds client retrieves the file using a dht like kademlia, bittorrent. Users can also save such files in a specific folder called pdz | ||
<code> | <code> | ||
name | name#scope@signer.pdz | ||
</code> | </code> | ||
[category:software] | [[category:software]] | ||
Revision as of 02:54, 13 March 2011
peer domain system
A decentralized name resolution system which provides strong authentication and name conflict prevention.
single record
can be pasted on twitter, discussion forums, web pages and so on
#pdsr domain scope record-type value expiry-date signer digest
- #pdsr magic string
- domain is the name to be resolved
- scope helps prevent name conflicts
- record-type can be a, c
- value can be an ip, standard dns name, other pds name
examples:
#pdsr 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. Users can also save such files in a specific folder called pdz
name#scope@signer.pdz