From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1QlazH-0000KK-6h for bitcoin-development@lists.sourceforge.net; Tue, 26 Jul 2011 06:19:27 +0000 X-ACL-Warn: Received: from zinan.dashjr.org ([173.242.112.54]) by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1QlazC-0005RD-43 for bitcoin-development@lists.sourceforge.net; Tue, 26 Jul 2011 06:19:27 +0000 Received: from ishibashi.localnet (fl-67-77-87-241.dhcp.embarqhsd.net [67.77.87.241]) (Authenticated sender: luke-jr) by zinan.dashjr.org (Postfix) with ESMTPSA id EAE07D707D8; Tue, 26 Jul 2011 06:19:13 +0000 (UTC) From: "Luke-Jr" To: Rick Wesson 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: <201107260022.24961.luke@dashjr.org> In-Reply-To: X-PGP-Key-Fingerprint: CE5A D56A 36CC 69FA E7D2 3558 665F C11D D53E 9583 X-PGP-Key-ID: 665FC11DD53E9583 X-PGP-Keyserver: x-hkp://subkeys.pgp.net MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201107260218.59313.luke@dashjr.org> X-Spam-Score: -0.7 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.2 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 0.5 AWL AWL: From: address is in the auto white-list X-Headers-End: 1QlazC-0005RD-43 Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] bitcoin DNS addresses X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jul 2011 06:19:27 -0000 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.