MIME-Version: 1.0
In-Reply-To: <201112162054.51039.andyparkins@gmail.com>
References: <1323731781.42953.YahooMailClassic@web120920.mail.ne1.yahoo.com>
	<201112161710.15165.andyparkins@gmail.com>
	<CAJ1JLts8JQ2J=DqJTD76gq2KB02ycqqeJjwaDyY2tPX8SJwvVA@mail.gmail.com>
	<201112162054.51039.andyparkins@gmail.com>
Date: Fri, 16 Dec 2011 13:50:54 -0800
Message-ID: <CAJ1JLtv+Q-+tV+jSWRzK=jH0t2Fug=89KJymc2OC=+w01iRQ6w@mail.gmail.com>
From: Rick Wesson <rick@support-intelligence.com>
To: Andy Parkins <andyparkins@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Fwd: [BIP 15] Aliases
Precedence: list

On Fri, Dec 16, 2011 at 12:54 PM, Andy Parkins <andyparkins@gmail.com> wrot=
e:

[snip]

>
> You've been unfair, the equivalent of your "user@authority.tld" is
> "https://authority.tld/user" or "https://user.authority.tld/" or
> "https://google.com/bitcoin/user" or any of an infinite number of other
> variations that _I_ as the mapper get to choose rather than whoever wrote
> the BIP; all of which are arguably no less "elegant" than that simple ema=
il.
>
> There is no equivalent in the other direction though. =A0For someone who
> want's to supply the TX to their mapping server... where does it go in
> "user@authority.tld"?

actually there are many differences. Specifying a standard using a
HTTP(s) transport for a look-up isn't something that has been done in
the PATH portion of the URI and that I was pointing out that there is
*NO* RFC that specifies such for a look-up provide the inverse of many
protocol specifications that did *not* choose that methodology.

What has happened is various schemes are specified, developed and
deployed. I am sure you are familure with many. sip:// ftp:// etc://
many are described at http://en.wikipedia.org/wiki/URI_scheme

NAPTR records (see http://en.wikipedia.org/wiki/NAPTR_record) are
another area that deserves research for those that desire URI schemes.

Understand that I am mearly advocating that as a group this work be
done in standards development process, and that IBANN is one such
effort.

-rick