User:Elifarley/pds - Revision history

Elifarley: /* name */

2011-03-31T01:48:07Z

name

← Older revision		Revision as of 01:48, 31 March 2011
Line 64:		Line 64:
	===name===		===name===
	* regexp: '''/[a-z0-9][a-z0-9-]{2,998}[a-z0-9]/'''		* regexp: '''/[a-z0-9][a-z0-9-]{2,998}[a-z0-9]/'''
	* ''~~'-'~~'' must not follow another ''~~'-'~~''		* a ''dash'' must not follow another ''dash''
	* Examples:		* Examples:
	** ~~p2p-foundation~~		** openfarmtech
	** p2p-foundation		** p2p-foundation

Elifarley at 01:20, 31 March 2011

2011-03-31T01:20:43Z

← Older revision		Revision as of 01:20, 31 March 2011
Line 5:		Line 5:
	==Introduction==		==Introduction==

	Basically, PDS keeps domain name data in '''.pdz''' or '''.pdr''' text files, which contain signed associations of ~~names~~ to IPs (~~or CNAMEs, that is,~~ aliases to other names, DNS- or PDS-based).		Basically, PDS keeps domain name data in '''.pdz''' or '''.pdr''' text files, which contain '''signed associations''' of '''domains''' to '''targets''', which can be IPs, CNAMEs (aliases to other names, DNS- or PDS-based)...

	These files are simple enough so that their domain associations can be easily spread by pasting their content on Twitter, discussion forums, web pages, emails, and so on. Users can simply copy a PDR text line found on a page and paste it on a text file inside the PDS application folder. Or they try to access a domain, and if it's not found among the currently available PDR files, the PDS client will automatically try to fetch it using Bit Torrent or a DHT-based map.		These files are simple enough so that their domain associations can be easily spread by pasting their content on Twitter, discussion forums, web pages, emails, and so on. Users can simply copy a PDR text line found on a page and paste it on a text file inside the PDS application folder. Or they try to access a domain, and if it's not found among the currently available PDR files, the PDS client will automatically try to fetch it using Bit Torrent or a DHT-based map.



Line 24:		Line 25:

	==Standard Syntax==		==Standard Syntax==
	Full syntax:		''To test the regexp, see http://regexpal.com/''
	'''~~name~~:~~suffix~~#revision@signer'''
			Full (or ''DRS'') PDS identifier syntax:
			'''domain#revision@signer'''

			DRS = Domain, Revision, Signer

			That is, domain '''domain''' at revision '''revision''' signed by '''signer'''.

			This can be put on a browser's address bar. The browser will query the local PDS client (which provides a standard DNS interface for applications, so that any current application can use it) for the target of that domain. See some response examples:
			# '''openfarmtech#revision@signer''' has target 68.169.49.115
			# '''domain#revision@signer''' has target (or points to) IP 68.169.49.115, 61.210.99.87
			# '''domain#revision@signer''' has target (or points to) CNAME other-domain-being-aliased

			One can also query a partial PDS identifier:

	''~~To test~~ the ~~regexp~~, ~~see http~~:~~//regexpal~~.~~com/~~''		DS-type identifier syntax:
			'''domain@signer'''

			This means the user wants the latest association for '''domain''' as reported by signer '''signer'''.

			DR-type identifier syntax:
			'''domain#revision'''

			This means the user wants the association for '''domain''' at a specific revision number as reported by the trusted signer for that domain. (Yes, users can configure the order of trusted signers for specific domains).

			Instead of configuring trusted signers for a certain domain, the user can simply store a PDR file inside a folder named ''trusted''. All PDR or PDZ files inside that folder will be blindly trusted (that is, signature checking won't be strict, so that you can use null signatures).

			D-type identifier syntax:
			'''domain'''

			This type of identifier is similar to the DR-type, but instead of requesting a specific revision, the user wants the latest revision for that domain.

			===domain===
			'''domain''' = '''name:suffix'''
			* Domain to be resolved

	===name===		===name===
	* Name to be resolved		* regexp: '''/[a-z0-9][a-z0-9-]{2,998}[a-z0-9]/'''
	* regexp: '''/[a-z0-9-]*/'''		* '''-''' must not follow another '''-'''
			* Examples:
			** p2p-foundation
			** p2p-foundation

	===suffix===		===suffix===
	* Helps prevent name conflicts; provides error checking.		* Helps prevent name conflicts; provides error checking.
	* Format: '''ABC''' ~~with~~:		* Format: '''ABC''' where:
	** '''ABC''' must match '''/[a-zA-Z0-9]{3}/'''		** '''ABC''' must match '''/[a-zA-Z0-9]{3}/'''
	** The domain owner can only choose '''A''' and '''B'''		** The domain owner can only choose '''A''' and '''B'''
	** '''C''' is a checksum		** '''C''' is a checksum calculated over '''name:AB'''
	** If '''A''' is a ''letter'', '''B''' must be a ''digit''		** If '''A''' is a ''letter'', '''B''' must be a ''digit''
	** If '''A''' is a ''digit'', '''B''' must be a ''letter''		** If '''A''' is a ''digit'', '''B''' must be a ''letter''
Line 63:		Line 99:

	===revision===		===revision===
	Like an SVN revision number		Like an SVN revision number. Every time the domain owner chooses to update his domain (that is, choose another target for the

	===signer===		===signer===

Elifarley at 00:14, 31 March 2011

2011-03-31T00:14:38Z

← Older revision		Revision as of 00:14, 31 March 2011
Line 26:		Line 26:
	Full syntax:		Full syntax:
	'''name:suffix#revision@signer'''		'''name:suffix#revision@signer'''

			''To test the regexp, see http://regexpal.com/''

	===name===		===name===
	* Name to be resolved		* Name to be resolved
	* regexp: '''/[a-z0-9-]*/''' )		* regexp: '''/[a-z0-9-]*/'''

	~~''To test the regexp, see http://regexpal.com/''~~
	===suffix===		===suffix===
	* Helps prevent name conflicts ~~and~~ provides error checking.		* Helps prevent name conflicts; provides error checking.
	* Format: '''ABC''' with:		* Format: '''ABC''' with:
	** '''ABC''' must match '''/[a-zA-Z0-9]{3}/'''		** '''ABC''' must match '''/[a-zA-Z0-9]{3}/'''
	** The domain owner can only choose '''A''' and '''B'''		** The domain owner can only choose '''A''' and '''B'''
	** '''C''' is a checksum		** '''C''' is a checksum
	** If '''A''' is a letter, '''B''' must be a digit		** If '''A''' is a ''letter'', '''B''' must be a ''digit''
	** If '''A''' is a digit, '''B''' must be a letter		** If '''A''' is a ''digit'', '''B''' must be a ''letter''
	** ~~Examples~~:		** Some '''valid''' examples:
	*** b4c		*** b4c
	*** b4C		*** b4C
Line 49:		Line 50:
	*** 4bC		*** 4bC
	*** 4BC		*** 4BC
			*** b47
			*** B47
			*** 4b7
			*** 4B7

			** Some '''invalid''' examples:
			*** bc5
			*** bcr
			*** Bcr
			*** 45c
			*** 45r

	===revision===		===revision===
	Like an SVN revision number		Like an SVN revision number

	===signer===		===signer===
	Identifies the public key that should be used to check the signature		Identifies the public key that should be used to check the signature

Elifarley at 00:07, 31 March 2011

2011-03-31T00:07:05Z

← Older revision		Revision as of 00:07, 31 March 2011
Line 16:		Line 16:
	* Be an [[wikipedia: Application Layer\| Application Layer]] protocol able to work under IPv4 and IPv6 [[wikipedia: Network Layer\| Network Layer]] protocols.		* Be an [[wikipedia: Application Layer\| Application Layer]] protocol able to work under IPv4 and IPv6 [[wikipedia: Network Layer\| Network Layer]] protocols.
	*prevent name conflicts		*prevent name conflicts
	*provide error checking on names
	*hard to take down		*hard to take down
	*easy to use		*easy to use
	*scalable		*scalable
			*provide error checking on names
	*		*
	*integration with existing internet infrastructure (dns, browsers, bit torrent, twitter, dot p2p)		*integration with existing internet infrastructure (dns, browsers, bit torrent, twitter, dot p2p)

	==Standard Syntax==		==Standard Syntax==
	'''name:~~NCS~~#revision@signer'''		Full syntax:
			'''name:suffix#revision@signer'''

			===name===
			* Name to be resolved
			* regexp: '''/[a-z0-9-]*/''' )

			''To test the regexp, see http://regexpal.com/''
			===suffix===
			* Helps prevent name conflicts and provides error checking.
			* Format: '''ABC''' with:
			** '''ABC''' must match '''/[a-zA-Z0-9]{3}/'''
			** The domain owner can only choose '''A''' and '''B'''
			** '''C''' is a checksum
			** If '''A''' is a letter, '''B''' must be a digit
			** If '''A''' is a digit, '''B''' must be a letter
			** Examples:
			*** b4c
			*** b4C
			*** B4c
			*** B4C
			*** 4bc
			*** 4Bc
			*** 4bC
			*** 4BC

	* '''name''': name to be resolved		===revision===
	* '''NCS''': Named CheckSum (any better name for this?) - provides error checking and helps prevent name conflicts		Like an SVN revision number
	* '''revision''': Like an SVN revision number		===signer===
	* '''signer~~''':~~ Identifies the public key that should be used to check the signature		Identifies the public key that should be used to check the signature

	* DHT key 1: (name, ~~NCS~~)		==Keys==
	* DHT key 2: (name, ~~NCS~~, signer)		* DHT key 1: (name, suffix)
	* DHT key 3: (name, ~~NCS~~, signer, revision)		* DHT key 2: (name, suffix, signer)
			* DHT key 3: (name, suffix, signer, revision)

	Questions:		Questions:
Line 39:		Line 64:

	Examples:		Examples:
	* 3 levels (name:~~NCS~~#revision@signer)		* 3 levels (name:suffix#revision@signer)
	** openfarmtech:4h#5@elifarley		** openfarmtech:4h#5@elifarley
	* 2 levels (name:~~NCS~~):		* 2 levels (name:suffix):
	** openfarmtech#4H		** openfarmtech#4H
	* 1 level (name):		* 1 level (name):
Line 89:		Line 114:
	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
	<code>		<code>
	#pdr name:~~NCS~~#revision record-type value expiry-date signer digest		#pdr name:suffix#revision record-type value expiry-date signer digest
	</code>		</code>
	* #pdr magic string		* #pdr magic string
Line 108:		Line 133:

	<code>		<code>
	name:~~NCS~~@signer.pdz		name:suffix@signer.pdz
	</code>		</code>

Elifarley: /* single record */

2011-03-20T14:50:24Z

single record

← Older revision		Revision as of 14:50, 20 March 2011
Line 89:		Line 89:
	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
	<code>		<code>
	#pdr name NCS revision record-type value expiry-date signer digest		#pdr name:NCS#revision record-type value expiry-date signer digest
	</code>		</code>
	* #pdr magic string		* #pdr magic string
Line 96:		Line 96:
	examples:		examples:
	<code>		<code>
	#pdr openfarmtech h2 5 c openfarmtech.org - elifarley 2afqgwk6		#pdr openfarmtech:h2#5 c openfarmtech.org - elifarley 2afqgwk6
	#pdr openfarmtech h2 5 c openfarmtech.org - - t9fqj6kf		#pdr openfarmtech:h2#5 c openfarmtech.org - - t9fqj6kf
	</code>		</code>

Elifarley: /* Use Cases */

2011-03-20T14:49:16Z

Use Cases

← Older revision		Revision as of 14:49, 20 March 2011
Line 89:		Line 89:
	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
	<code>		<code>
	#pdr name ~~scope~~ record-type value expiry-date signer digest		#pdr name NCS revision record-type value expiry-date signer digest
	</code>		</code>
	* #pdr magic string		* #pdr magic string
	* record-type can be a, aaaa, cname		* record-type can be a, aaaa, cname
	* value can be an ip, standard dns name, other ~~pds~~ name		* value can be an ip, standard dns name, other PDS name
	examples:		examples:
	<code>		<code>
	#pdr openfarmtech h2 c openfarmtech.org 0 elifarley 2afqgwk6		#pdr openfarmtech h2 5 c openfarmtech.org - elifarley 2afqgwk6
			#pdr openfarmtech h2 5 c openfarmtech.org - - t9fqj6kf
	</code>		</code>

Elifarley: /* Image Syntax */

2011-03-19T00:13:21Z

Image Syntax

← Older revision		Revision as of 00:13, 19 March 2011
Line 56:		Line 56:

	==Image Syntax==		==Image Syntax==
	Encode PDR using [[wikipedia: QR code]] ( a 2D barcode).		Encode PDR using [[wikipedia: QR code\| QR code]] / [[wikipedia: SPARQCode\| SPARQCode]] ( a 2D barcode).

			'''TODO''' Experiment with various 2D barcodes at the [http://barcode.tec-it.com/barcode-generator.aspx?LANG=en Online Barcode Generator]

	==Date format==		==Date format==

Elifarley: /* DNS-style syntax */

2011-03-18T23:54:17Z

DNS-style syntax

← Older revision		Revision as of 23:54, 18 March 2011
Line 54:		Line 54:
	Examples:		Examples:
	* openfarmtech.p2p		* openfarmtech.p2p

			==Image Syntax==
			Encode PDR using [[wikipedia: QR code]] ( a 2D barcode).

	==Date format==		==Date format==

Elifarley: /* See Also */

2011-03-18T13:36:15Z

Elifarley at 13:29, 18 March 2011

2011-03-18T13:29:17Z

← Older revision		Revision as of 13:29, 18 March 2011
Line 16:		Line 16:
	* Be an [[wikipedia: Application Layer\| Application Layer]] protocol able to work under IPv4 and IPv6 [[wikipedia: Network Layer\| Network Layer]] protocols.		* Be an [[wikipedia: Application Layer\| Application Layer]] protocol able to work under IPv4 and IPv6 [[wikipedia: Network Layer\| Network Layer]] protocols.
	*prevent name conflicts		*prevent name conflicts
			*provide error checking on names
	*hard to take down		*hard to take down
	*easy to use		*easy to use
	*scalable		*scalable
			*
	*integration with existing internet infrastructure (dns, browsers, bit torrent, twitter, dot p2p)		*integration with existing internet infrastructure (dns, browsers, bit torrent, twitter, dot p2p)

	==Standard Syntax==		==Standard Syntax==
	'''name:NCS#~~serial~~@signer'''		'''name:NCS#revision@signer'''

	''NCS'': Named ~~Check Sum~~ (any better name for this?)		* '''name''': name to be resolved
			* '''NCS''': Named CheckSum (any better name for this?) - provides error checking and helps prevent name conflicts
			* '''revision''': Like an SVN revision number
			* '''signer''': Identifies the public key that should be used to check the signature

			* DHT key 1: (name, NCS)
			* DHT key 2: (name, NCS, signer)
			* DHT key 3: (name, NCS, signer, revision)

			Questions:
			* <span style="color: red">'''signer'''</span>: How to get the signer's public key?

	Examples:		Examples:
	* 3 levels (name:NCS#~~serial~~@signer)		* 3 levels (name:NCS#revision@signer)
	** openfarmtech:4h#5@elifarley		** openfarmtech:4h#5@elifarley
	* 2 levels (name~~#scope~~):		* 2 levels (name:NCS):
	** openfarmtech#~~20110310~~		** openfarmtech#4H
	* 1 level (name):		* 1 level (name):
	** openfarmtech		** openfarmtech

	===Questions===		===Questions===
	''~~serial~~'' should be serial or date?		''revision'' should be serial or date?

	==DNS-style syntax==		==DNS-style syntax==
Line 44:		Line 56:

	==Date format==		==Date format==
	See [[wikipedia:Base32]]		See [[wikipedia: Base32]]
			Let's use z-base-32: [http://philzimmermann.com/docs/human-oriented-base-32-encoding.txt human-oriented base-32 encoding]

	YYYDDDSSS		YYYDDDSSS
Line 50:		Line 63:
	DDD from 0 to 365		DDD from 0 to 365
	SSS from 0 to		SSS from 0 to


	==Implementation Ideas==		==Implementation Ideas==
Line 72:		Line 84:
	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
	<code>		<code>
	#pdr ~~domain~~ scope record-type value expiry-date signer digest		#pdr name scope record-type value expiry-date signer digest
	</code>		</code>
	* #pdr magic string		* #pdr magic string
	* domain is the name to be resolved
	* scope helps prevent name conflicts
	* record-type can be a, aaaa, cname		* record-type can be a, aaaa, cname
	* value can be an ip, standard dns name, other pds name		* value can be an ip, standard dns name, other pds name
	examples:		examples:
	<code>		<code>
	#pdr openfarmtech ~~20110311~~ c openfarmtech.org 0 elifarley 2afqgwk6		#pdr openfarmtech h2 c openfarmtech.org 0 elifarley 2afqgwk6
	</code>		</code>

Line 92:		Line 102:

	<code>		<code>
	name~~#scope~~@signer.pdz		name:NCS@signer.pdz
	</code>		</code>

	==See Also==		==See Also==
	* [[wikipedia: Zooko's triangle]]		* [[wikipedia: Zooko's triangle]]
	*		* [http://zooko.com/distnames.html Names: Decentralized, Secure, Human-Meaningful: Choose Two]
			* [http://www.waterken.com/dev/YURL/Analogy/ YURL: Naming vs. Pointing]
			* [[wikipedia: Mnet (Computer program)]]
			* [[wikipedia: ZRTP]]
			* [[wikipedia: Kademlia]]

← Older revision		Revision as of 13:36, 18 March 2011
Line 110:		Line 110:
	* [http://www.waterken.com/dev/YURL/Analogy/ YURL: Naming vs. Pointing]		* [http://www.waterken.com/dev/YURL/Analogy/ YURL: Naming vs. Pointing]
	* [[wikipedia: Mnet (Computer program)]]		* [[wikipedia: Mnet (Computer program)]]
			* Evil Geniuses Transport Protocol - [http://mnet.sourceforge.net/EGTP.html EGTP]
	* [[wikipedia: ZRTP]]		* [[wikipedia: ZRTP]]
	* [[wikipedia: Kademlia]]		* [[wikipedia: Kademlia]]
			* [http://dot-p2p.org/index.php?title=Main_Page Dot p2p]