Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of mm.st
	designates 66.111.4.26 as permitted sender)
	client-ip=66.111.4.26; envelope-from=theymos@mm.st;
	helo=out2.smtp.messagingengine.com; 
Message-Id: <1323751122.9491.140661010910705@webmail.messagingengine.com>
From: "theymos" <theymos@mm.st>
To: bitcoin-development@lists.sourceforge.net
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
References: <1323728469.78044.YahooMailNeo@web121012.mail.ne1.yahoo.com>
In-Reply-To: <1323728469.78044.YahooMailNeo@web121012.mail.ne1.yahoo.com>
Date: Mon, 12 Dec 2011 22:38:42 -0600
Subject: Re: [Bitcoin-development] [BIP 15] Aliases
Precedence: list

I like the user@server.com model. The protocol should be done entirely
in DNS, though, not using HTTP connections to the server. Then the
protocol can easily be used with Namecoin or other DNS
replacements/enhancements later. Crypto to prevent MITM attacks can be
an optional part of the protocol.

Almost all users will be unable to set up *any* always-on Internet
service to answer queries, so I'm not too concerned about how easy it is
to set up the server software.

I agree that FirstBits is bad for this. Unlike DNS, "registrations" last
forever because private keys can't be transferred safely. All short
names will be taken quickly. It will also be very expensive for clients
to query this themselves.

The CA model is broken and it should never be used by Bitcoin.