Discuss mailing list

[novaking AT eztv.se]

Also found here: http://wiki.opennicproject.org/dotKEYTLD

.key is chartered for use with our peer to peer based DNS concept. (
http://dot-p2p.org/ )
The .key TLD is a validation mechanism for the .p2p TLD, the .key TLD
offers peer-to-peer records with guaranteed integrity in a peer-to-peer
system.

Domain Resolution

A simple explanation of how domain resolution is done through the
peer-to-peer network.

Introduction

The following terms are used below:

* DNS client - This is often your operating system on behalf of your web
browser.
* P2P client - The peer-to-peer component of Trust4.
* DNS server - The DNS server component of Trust4 which serves answers to
your DNS client.

Resolution

* Your DNS client asks the DNS server for a domain such as 'domain.p2p'.
* The P2P client asks your immediate peers for the answer to 'domain.p2p'.
At most, it waits 1.5 seconds due to the limited timeout that DNS clients
have.
* It determines the correct 'domain.p2p' -> 'domain.p2p.hash.key' based on
the trust order of your peers. This is the only stage whereby records can
not be verified for integrity.
* The DNS server returns the CNAME record. It is important that it returns
the CNAME record and does not attempt to do the record lookup for
'domain.p2p.hash.key' transparently, due to the fact that except in very
limited circumstances, the DNS client would timeout before it managed to
return the results for the CNAME record.
* The DNS client realizes it has a CNAME record, and re-requests the
answers for 'domain.p2p.hash.key'.
* The P2P client asks your immediate peers for the answer to
'domain.p2p.hash.key'.
* This time around, the P2P client has a 'hash', which is the hash of the
public key that is transferred along with the records.
* The P2P client verifies that the public key in the records is correct,
and then verifies that the record data is signed correctly using the full
public key and the signature that was transferred along with the record
data.
* If the record data is intact, the DNS server returns the records to the
DNS client.

Contacts

TiAMO - tiamo AT tfr.org
NovaKing - novaking AT eztv.se

#dns-p2p @ efnet.org


> Also found here: http://wiki.opennic.glue/dotP2PTLD
>
>
> OpenNIC .p2p Charter
>
> .p2p is chartered for use with our peer to peer based DNS concept. (
> http://dot-p2p.org/ ) The primary service will allow people to use a
> decentralized open DNS system. The purpose of this TLD is to allow people
> using traditional methods of DNS to gather information about this new
> concept and to also control domain registrations through the use of
> http://nic.p2p
>
> .p2p domain names are first come, first serve, excluding those reserved
> for .p2p operational matters (www.p2p, nic.p2p, opennic.p2p) for domain
> spam prevention, to qualify for a domain you must own at least one domain
> of the same name in the existing TLD scope (eg: test.p2p requires you to
> own test.com/.net/.org/etc)
>
> To prevent domain fraud on commonly used domains (eg: google.*) alexa
> top1000 will be locked to the owner of the highest ranking domain that
> appears on the alexa rankings ...
>
> Reselling of domains/subdomains, as a domain is controlled by a member, we
> have no direct say in how it's operations are handled. All domains handled
> through nic.p2p will be freely available to all members.
>
> Contacts
>
> TiAMO - tiamo AT tfr.org
> NovaKing - novaking AT eztv.se
>
> #dot-p2p @ efnet.org
>