References: <1323731781.42953.YahooMailClassic@web120920.mail.ne1.yahoo.com>
	<CAGQP0AGvq603oshSGiP79A+gqDqW_hHG+qZjaZccCmo+gd3W2A@mail.gmail.com>
	<201112121841.39864.luke@dashjr.org>
	<CAGQP0AGBKKEqhaJZj-Rw400AjrVHE9_EMve=RWdqoaOaDsTgtw@mail.gmail.com>
	<CAGQP0AGY32QP=rXyGftb5NbHA7fhcCne7W=pt5+onXp1Jbm98Q@mail.gmail.com>
	<1323736946.58149.YahooMailNeo@web121001.mail.ne1.yahoo.com>
	<CANEZrP1oPaqAT+LCfrAXO9WBz+oC2uvbP=5vx2+DX2P0qFusgA@mail.gmail.com>
	<CALxbBHUgCOVMRxtnsmC2W-MaYfeDSzaftWMCCgcWsMBdZfzPQg@mail.gmail.com>
	<CAGQP0AHRaaB6UC5Y-mW=K6BqrzTOj9saKJjo50ZzvTpZKntnww@mail.gmail.com>
	<CABsx9T1wksXjLy=EC6dK1WtVFEayL-HgXWtENgSPXhU6Du2Srg@mail.gmail.com>
Message-ID: <1323791208.31194.YahooMailNeo@web121013.mail.ne1.yahoo.com>
Date: Tue, 13 Dec 2011 07:46:48 -0800 (PST)
From: Amir Taaki <zgenjix@yahoo.com>
To: "bitcoin-development@lists.sourceforge.net"
	<bitcoin-development@lists.sourceforge.net>
In-Reply-To: <CABsx9T1wksXjLy=EC6dK1WtVFEayL-HgXWtENgSPXhU6Du2Srg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Bitcoin-development] Fwd: [BIP 15] Aliases
Precedence: list
Reply-To: Amir Taaki <zgenjix@yahoo.com>

Maybe I wasn't clear enough in the document, but this is the intent with th=
e HTTPS proposal.=0A=0Agenjix@foo.org=0A=0AContacts https://foo.org/bitcoin=
-alias/?handle=3Dgenjix and the system responds with a bitcoin address. Whe=
ther the system gives you a new address from a pool of addresses, or contac=
ts the merchant behind the scenes is implementation defined.=0A=0AI'll clar=
ify it later. This is the relevant line:=0A=0Astring strRequestUrl =3D strD=
omain + "/bitcoin-alias/?handle=3D" + pszEncodedNick;=0A=0ABetween HTTPS se=
rvice and server service, I lean slightly towards HTTPS (automatic encrypte=
d connection, CAs + all benefits of DNS). But still interested in arguments=
 in favour of a server service (daemon answering queries).=0A=0A=0A----- Or=
iginal Message -----=0AFrom: Gavin Andresen <gavinandresen@gmail.com>=0ATo:=
 Jorge Tim=F3n <timon.elviejo@gmail.com>=0ACc: "bitcoin-development@lists.s=
ourceforge.net" <bitcoin-development@lists.sourceforge.net>=0ASent: Tuesday=
, December 13, 2011 1:06 PM=0ASubject: Re: [Bitcoin-development] Fwd: [BIP =
15] Aliases=0A=0AI agree with Mike Hearn and Christian Decker-- paying to=
=0A'somebody@foo.com' should become, behind the scenes, a HTTPS query to=0A=
https://foo.com/something. If you just want to (say) donate to=0Aeff.org, t=
hen paying to '@eff.org' aught to work nicely.=0A=0AAnd if namecoin ever ta=
kes off you'll pay to 'somebody@foo.bit'.=0A=0AIt seems to me that if it wa=
s DNS-based, the address should be=0Asomething like 'somebody.bitcoin.foo.c=
om'. But I think it is unlikely=0Apeople will setup and run a custom DNS se=
rver just to support bitcoin=0Apayments.=0A=0A-- =0A--=0AGavin Andresen=0A=
=0A------------------------------------------------------------------------=
------=0ASystems Optimization Self Assessment=0AImprove efficiency and util=
ization of IT resources. Drive out cost and =0Aimprove service delivery. Ta=
ke 5 minutes to use this Systems Optimization =0ASelf Assessment. http://ww=
w.accelacomm.com/jaw/sdnl/114/51450054/=0A_________________________________=
______________=0ABitcoin-development mailing list=0ABitcoin-development@lis=
ts.sourceforge.net=0Ahttps://lists.sourceforge.net/lists/listinfo/bitcoin-d=
evelopment=0A