Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from <rick.wesson@iidf.org>) id 1RbDUg-0006OI-Nk for bitcoin-development@lists.sourceforge.net; Thu, 15 Dec 2011 15:45:14 +0000 X-ACL-Warn: Received: from mail-vw0-f47.google.com ([209.85.212.47]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1RbDUV-0003Ep-NK for bitcoin-development@lists.sourceforge.net; Thu, 15 Dec 2011 15:45:14 +0000 Received: by vbbfc21 with SMTP id fc21so2257178vbb.34 for <bitcoin-development@lists.sourceforge.net>; Thu, 15 Dec 2011 07:44:58 -0800 (PST) MIME-Version: 1.0 Received: by 10.52.21.211 with SMTP id x19mr3554819vde.58.1323963898101; Thu, 15 Dec 2011 07:44:58 -0800 (PST) Received: by 10.52.37.80 with HTTP; Thu, 15 Dec 2011 07:44:58 -0800 (PST) In-Reply-To: <CAGQP0AFD9q+=vZPod_n_LJjCjzVnVy5w3hq4N07JZRM6=Ly-FQ@mail.gmail.com> References: <CA+QPp0rAJz9wPcrf926q=_c45mCL_67JCyacvM79CWcic9AL2w@mail.gmail.com> <1323929094.37881.YahooMailClassic@web120902.mail.ne1.yahoo.com> <CACwuEiPbLdpgYCcTHH_GCHcwGcGj5HnOMFKkQf860D4Xn0mLsQ@mail.gmail.com> <CAGQP0AFD9q+=vZPod_n_LJjCjzVnVy5w3hq4N07JZRM6=Ly-FQ@mail.gmail.com> Date: Thu, 15 Dec 2011 07:44:58 -0800 Message-ID: <CAJ1JLtsdPDfTyX6zVbu0wmiKY6+rWZcnnRaCcBukvJrLg0-_3w@mail.gmail.com> From: Rick Wesson <rick@support-intelligence.com> To: =?ISO-8859-1?Q?Jorge_Tim=F3n?= <timon.elviejo@gmail.com> Content-Type: text/plain; charset=ISO-8859-1 X-Spam-Score: 0.4 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 0.4 AWL AWL: From: address is in the auto white-list X-Headers-End: 1RbDUV-0003Ep-NK 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: <bitcoin-development.lists.sourceforge.net> List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> List-Post: <mailto:bitcoin-development@lists.sourceforge.net> List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> X-List-Received-Date: Thu, 15 Dec 2011 15:45:14 -0000 > Why don't just... > > bitcoin://url.without.explicitly.specifying.provider > bitcoin://alias@provider > bitcoin://IIBAN@authorizedBitcoinInstitution ?? > > By the way, I don't like the fact that a single authorized institution > needs to map the IIBANs to bitcoin addresses. The IANA is a good institution to rely on for mapping things, much history and wise execution there. -rick