Breaking: P2P DNS to take on ICANN after US domain seizures
 

http://get.dot-p2p.com/dot-p2p.png

http://blogs.computerworld.com/17444...urce=rss_blogs

http://dot-p2p.org/index.php?title=Main_Page

What do you guys think? Will it take off?

It's not about filesharing my ass, lol.

Here is more on it: http://torrentfreak.com/bittorrent-b...eizures-101130

this says a little something:2 cents:
The project has been embraced by many familiar names in the P2P-community. Former Pirate Bay spokesman Peter Sunde is among them,

it will just end up as a spamming, scamming, and pirating network that will ultimately get filtered by every isp out there... :2 cents:


.

Read the article. It can't be filtered because, at least in it's current planned form, users run a program on their computer that enables the .p2p TLD.

Those users have internet connections?

My point was that ISPs could not simply block the .p2p TLD. I'm not sure what your point is though...

Not sure how it can be implemented, but if the P2P "botnet" (if you can call it that) is serving as the root-servers for this tld, then surely ISPs can simply filter out UDP traffic to port 53 with "not established" flags - ie direct DNS requests....

What are the benefits of it? (besides being able to run shady stuff without risk of getting shut down)

You stated "It can't be filtered".. Mine is "it can".

I'm going to read more into this, but on the surface it looks like a great idea. I'm all for anything that breaks apart censorship.

With the current administration hell bent on censoring the Internet (so their crimes can be carried out completely unchecked and under the cloak of darkness) this would be a positive and natural counterbalance.

Sorry if I was not clear enough for you. The point of this idea is to circumvent the US government's attempts to seize domains through ICANN. It seems this plan would accomplish that. When I said it can't be filtered I meant that ISPs can't simply block the .p2p TLD if people are not even using their DNS to access this TLD. Sure they could filter IPs or IP ranges of servers known to use the .p2p TLD, but has that ever been done by a US ISP? Possibly "input" is right and they can block all alternate DNS systems with a UDP filter, but odds are they could find a way around that if it does work.

Any hosts want to comment on the feasibility of this idea?

How is a decentralized system going to prevent cybersquatting?

Who decides ownership of .p2p domains?
How are disputes solved if there is no governing body?

They can filter that. They have to. If by chance they don't, it will become the child porn mecca of the world.

Doesn't the CP world already have it's "mecca" in Google Images? :Oh crap

Sure they can, ever heard of proxy DNS? 90% of every residential ISP does it.

Thanks, Ethersync.. :thumbsup

We can basically choose between US-controlled .com domains (ICANN) or pirated-controlled .p2p domains (OpenNIC).

The ownership of a .p2p domain is as safe as money deposited in a Curaçao-based bank? :upsidedow

Even if the ISPs DNS is not being used at all to access the .p2p sites and it is instead handled by an application running on the users computer?

The real threat to this system is if ICANN goes on the offensive by opening up the same extension to bury the alternative OpenNIC TLD extension(s).

Sure ICANN would look like supreme tyrannical asses if they did, but ultimately it would muddy the water just enough to cause the OpenNIC extension (what ever it was, .p2p, .free ..etc) to fail.

ISPs can block applications, in theory, ie... Newsreaders attempting to use NNTP port 119, etc.

If its on port 53 and UDP traffic they can do whatever they please with it. .p2p doesn't mean squat, it just means those applications will have a "embeded" dns root to include for their TLD. DNS request goes out on port 53 and UDP. Thats the way the DNS RFC was written.

The only way around it is utilizing a IPsec VPN to connect and tunnel all your traffic.

You no doubt know far more on the subject than me. Thanks for the feedback.

Here is a comment I found on DSL Reports:

http://www.dslreports.com/shownews/P...P2P-DNS-111605

I have no idea if the person posting this knows what he is talking about or not, but is what he describes possible?

A few other issues...

1) If an app must be running as a service to catch all .p2p requests I would not be surprised if Antivirus companies flag the app as malware.

2) Search engines probably won't spider .p2p domains.

This will just lead to the US government cracking down on encryption keys, as is they already make specific encryption keys illegal to export out of the country. Crack down on encrypted traffic, sooner or later isps will start locking down ports and protocols.

More/less this is just pro-longing the inevitable. I don't see the big stink. Other than a group of people pissed off at the world that they can't pirate anything anymore. man up and pay the company who made the software.

If you want to do P2P, then turn off all your firewalls and open up your C folder for the world to view. After all, who wants privacy right and sharing data?

Not attacking the op just making observations.

The US Gov has relaxed it's stance on encryption software a LOT since the early 90's. And anyways, if the encryption part is written outside of the US then the gov can't really do much about stopping it. They still have a couple of restrictions on exporting encryption products but none on importing AFAIK.

Correct, but it doesn't mean they wouldn't find a way to "regulate" encryption and registration of the algos/etc.

People just find ways around to do something, the US government will just make up more rules and laws. Its a never ending battle. This is why we have so many worthless laws out there that mean absolutely nothing.

Cool idea. I will register search.p2p and make it a crappy searchengine for the p2p-domains.

The worms will love it.