From: "Luke-Jr" <luke@dashjr.org>
To: Rick Wesson <rick@support-intelligence.com>
Date: Tue, 26 Jul 2011 02:18:56 -0400
User-Agent: KMail/1.13.7 (Linux/2.6.39-gentoo; KDE/4.6.4; x86_64; ; )
References: <CAJ1JLts5_r6hHoJR-gS-CuuvS00p=RQ6iYbCyOkBDcvgs1xtew@mail.gmail.com>
	<201107260022.24961.luke@dashjr.org>
	<CAJ1JLttnARz=f0UmzJKpCXpMeKg1X_R7Jfwv7tZq_pJqn8LbQQ@mail.gmail.com>
In-Reply-To: <CAJ1JLttnARz=f0UmzJKpCXpMeKg1X_R7Jfwv7tZq_pJqn8LbQQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201107260218.59313.luke@dashjr.org>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] bitcoin DNS addresses
Precedence: list

On Tuesday, July 26, 2011 12:54:23 AM Rick Wesson wrote:
> > 1. Right now you practically need a unique Bitcoin address per
> > transaction.
> 
> I'd like to find ways to alievate this requirement.

Admittedly, my proposal to email a signed message allows one to reuse 
addresses, but there is still a privacy concern.

> > 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.

http://www.google.com/search?q=%22PROTECT+IP+act%22+DNSSEC

> > 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.

I only meant that foo.bar.net is not the same formatting.
foo@bar.net would be.