Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Rb509-0004K4-Bf for bitcoin-development@lists.sourceforge.net; Thu, 15 Dec 2011 06:41:09 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.210.175 as permitted sender) client-ip=209.85.210.175; envelope-from=walter.stanish@gmail.com; helo=mail-iy0-f175.google.com; Received: from mail-iy0-f175.google.com ([209.85.210.175]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Rb508-0005Ml-9s for bitcoin-development@lists.sourceforge.net; Thu, 15 Dec 2011 06:41:09 +0000 Received: by iadj38 with SMTP id j38so3115267iad.34 for ; Wed, 14 Dec 2011 22:41:03 -0800 (PST) MIME-Version: 1.0 Received: by 10.43.51.69 with SMTP id vh5mr1680690icb.32.1323931262894; Wed, 14 Dec 2011 22:41:02 -0800 (PST) Sender: walter.stanish@gmail.com Received: by 10.42.151.69 with HTTP; Wed, 14 Dec 2011 22:41:02 -0800 (PST) In-Reply-To: <1323929094.37881.YahooMailClassic@web120902.mail.ne1.yahoo.com> References: <1323929094.37881.YahooMailClassic@web120902.mail.ne1.yahoo.com> Date: Thu, 15 Dec 2011 14:41:02 +0800 X-Google-Sender-Auth: zV1WgudXX1NR0cIwXeULHYUQK60 Message-ID: From: Walter Stanish To: Zell Faze Content-Type: text/plain; charset=ISO-8859-1 X-Spam-Score: -1.1 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (walter.stanish[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 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 0.4 AWL AWL: From: address is in the auto white-list X-Headers-End: 1Rb508-0005Ml-9s Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] Fwd: [BIP 15] Aliases 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: Thu, 15 Dec 2011 06:41:09 -0000 >> Just so we're clear, what is the need for HTTP at all? >> A query for a string and an answer can all be handled via DNS. > It is a lot easier to set up an HTTP server to dynamically respond > with addresses than a DNS record. Interesting that you bring up the effort factor. The notion that every individual will want to run their own DNS or HTTP based alias system to dispense transaction-specific bitcoin addresses seems - on this basis - alone a little far fetched. Such a system would provide very little added value at significant hassle to the small subset of users who could be bothered setting up such a scheme. Also, remember that most people in the world don't even know what DNS is, nor do they have the capacity or motivation to set up a program on a web server for what amounts to minor ongoing time savings and some vanity thrills. To my mind, it is far more likely that third party hosted services (such as providers of hosted wallet, conventional currency holding and exchange services) will provide aliasing resolution, and that these alias resolution services will operate on an alias@provider mechanism (for example, IIBAN and its 'institution' codes @ ). In addition, during the 'pre-transaction exchange' that the alias resolution process essentially represents, additional value could be added by these types of service providers by providing functionality presently excluded from Bitcoin but relevant to real world financial systems. For example this 'pre-transaction exchange' process might include, in addition to alias resolution, transaction metadata exchange (transaction description, invoice/order number, taxation information, schedules of fees and charges, pre-arranged currency exchange rates if filling an payment for an amount quoted in another (eg: conventional) currency, shipping terms, transaction reversal (cancellation) terms, escrow terms, etc.) Regards, Walter Stanish Payward Inc.