Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1RbbIl-00032e-5h for bitcoin-development@lists.sourceforge.net; Fri, 16 Dec 2011 17:10:31 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.53 as permitted sender) client-ip=74.125.82.53; envelope-from=andyparkins@gmail.com; helo=mail-ww0-f53.google.com; Received: from mail-ww0-f53.google.com ([74.125.82.53]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128) (Exim 4.76) id 1RbbIk-0005BC-6T for bitcoin-development@lists.sourceforge.net; Fri, 16 Dec 2011 17:10:31 +0000 Received: by wgbds1 with SMTP id ds1so5896047wgb.10 for ; Fri, 16 Dec 2011 09:10:24 -0800 (PST) Received: by 10.227.206.4 with SMTP id fs4mr6135768wbb.21.1324055424072; Fri, 16 Dec 2011 09:10:24 -0800 (PST) Received: from dvr.localnet (mail.360visiontechnology.com. [92.42.121.178]) by mx.google.com with ESMTPS id dd4sm13893664wib.1.2011.12.16.09.10.19 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 16 Dec 2011 09:10:20 -0800 (PST) From: Andy Parkins To: Rick Wesson Date: Fri, 16 Dec 2011 17:10:10 +0000 User-Agent: KMail/1.13.6 (Linux/3.0.0-1-686-pae; KDE/4.6.3; i686; ; ) References: <1323731781.42953.YahooMailClassic@web120920.mail.ne1.yahoo.com> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1963932.6d9retVk0s"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201112161710.15165.andyparkins@gmail.com> X-Spam-Score: -1.6 (-) 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 (andyparkins[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -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 0.0 AWL AWL: From: address is in the auto white-list X-Headers-End: 1RbbIk-0005BC-6T 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: Fri, 16 Dec 2011 17:10:31 -0000 --nextPart1963932.6d9retVk0s Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable On 2011 December 16 Friday, Rick Wesson wrote: > On Thu, Dec 15, 2011 at 4:07 PM, slush wrote: > > I really like this proposal with standard URLs. All other proposals like > > DNS mapping or email aliases converted to URLs with some weird logic > > looks strange to me. >=20 > wow, really. Maybe you could review some RFCs, there are thousands of > examples where some really smart engineers chose the exact opposite > path which you propose below. Could you point me at an example? Andy =2D-=20 Dr Andy Parkins andyparkins@gmail.com --nextPart1963932.6d9retVk0s Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEABECAAYFAk7re3MACgkQwQJ9gE9xL21QowCgzdxkbqGgTjAcwkL9K90TJEzM xKIAoIFjyM3HXRm+p9NZ6swvbO/eEbto =jJ7W -----END PGP SIGNATURE----- --nextPart1963932.6d9retVk0s--