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 1RaUZH-0006bW-38 for bitcoin-development@lists.sourceforge.net; Tue, 13 Dec 2011 15:46:59 +0000 X-ACL-Warn: Received: from nm29-vm3.bullet.mail.ne1.yahoo.com ([98.138.91.159]) by sog-mx-3.v43.ch3.sourceforge.com with smtp (Exim 4.76) id 1RaUZB-0002xu-Ih for bitcoin-development@lists.sourceforge.net; Tue, 13 Dec 2011 15:46:59 +0000 Received: from [98.138.90.48] by nm29.bullet.mail.ne1.yahoo.com with NNFMP; 13 Dec 2011 15:46:48 -0000 Received: from [98.138.87.9] by tm1.bullet.mail.ne1.yahoo.com with NNFMP; 13 Dec 2011 15:46:48 -0000 Received: from [127.0.0.1] by omp1009.mail.ne1.yahoo.com with NNFMP; 13 Dec 2011 15:46:48 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 416386.50371.bm@omp1009.mail.ne1.yahoo.com Received: (qmail 32966 invoked by uid 60001); 13 Dec 2011 15:46:48 -0000 X-YMail-OSG: GHlKJ4kVM1lM3NK8Wnp8yAo0CJelZ9Hx2oGAm2jEBB25ws_ dqBKmbDWyRdlbxzI4qMoZ9bltmrm1aNR.VloLQWAisuR6krTbvYLHiy9kMZR .DVtClC.sdIyqM9L7jUeZNqinvK1pnfG90hs1xTk9XpLEZ.4e9c7nQtdAKVE PRrb0zbQrIWnOpHYbpwfh2pnCneLB5NqKpKwlbLpCJXbvSvKJUshg3.rZjrS 6Uvhcmfyq4AMYEdlwrCkSDySDf_f9XorjXt2QzSNcZuN.iz_S0J8PDz8ygup QkQ1dSdbkFLBPdb2J_fME3MugGz4g.iBCATISaKg1cRrztWXO25YsAyrjsLS j90qKcH.Un6fkJiN5J9b0dcPwmlBK0WFoECiRy1WjXRKt.AFSjKqKkjUlrEb f7sbJPFXHU9vzBbAwM4CHdt4rsSraHEHrd8naNHaA4vzIFe_vTe35sTfG7fK mFYwD0jDsMak3O1ockHuZC829ciwK3E.DZBJm9CoD39RAzrAkeGlzerd13s_ gnd1UdiIahhvLuiLl Received: from [92.20.180.200] by web121013.mail.ne1.yahoo.com via HTTP; Tue, 13 Dec 2011 07:46:48 PST X-Mailer: YahooMailWebService/0.8.115.331698 References: <1323731781.42953.YahooMailClassic@web120920.mail.ne1.yahoo.com> <201112121841.39864.luke@dashjr.org> <1323736946.58149.YahooMailNeo@web121001.mail.ne1.yahoo.com> Message-ID: <1323791208.31194.YahooMailNeo@web121013.mail.ne1.yahoo.com> Date: Tue, 13 Dec 2011 07:46:48 -0800 (PST) From: Amir Taaki To: "bitcoin-development@lists.sourceforge.net" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -2.4 (--) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [98.138.91.159 listed in list.dnswl.org] 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (zgenjix[at]yahoo.com) -2.3 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1RaUZB-0002xu-Ih Subject: Re: [Bitcoin-development] Fwd: [BIP 15] Aliases X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list Reply-To: Amir Taaki List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2011 15:46:59 -0000 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 =0ATo:= Jorge Tim=F3n =0ACc: "bitcoin-development@lists.s= ourceforge.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