MIME-Version: 1.0
In-Reply-To: <201107260022.24961.luke@dashjr.org>
References: <CAJ1JLts5_r6hHoJR-gS-CuuvS00p=RQ6iYbCyOkBDcvgs1xtew@mail.gmail.com>
	<1311644156.29866.4.camel@Desktop666>
	<CAJ1JLts9vcF7bGo8udK9OicWhAUHvmeFDrZQDKBoGQbp-nYGrw@mail.gmail.com>
	<201107260022.24961.luke@dashjr.org>
Date: Mon, 25 Jul 2011 21:54:23 -0700
Message-ID: <CAJ1JLttnARz=f0UmzJKpCXpMeKg1X_R7Jfwv7tZq_pJqn8LbQQ@mail.gmail.com>
From: Rick Wesson <rick@support-intelligence.com>
To: Luke-Jr <luke@dashjr.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] bitcoin DNS addresses
Precedence: list

>
> 1. Right now you practically need a unique Bitcoin address per transaction.

I'd like to find ways to alievate this requirement.

> 2. DNSSEC is on the edge of becoming illegal in the US.

really, pointers please. DHS was a huge funder for DNSSEC asn .mil was
the first domain to deploy it. I think you may be miss-informed.

> 3. Emails aren't merely domains.

correct, I was speaking about an "address" that used the same/simular
formatting but did not use the SMTP protocol.

-rick

> I would propose something like resolving foo@bar.net to a SRV lookup for
> _bitcoinaddressresolution._tcp.foo.bar.net, expecting a cert for bar.net,
> making a HTTPS request for /bitcoinaddressresolution?foo@bar.net, and also
> sending an email to foo@bar.net (the usual way) signed with the keys used for
> the transaction. ;)
>