Re: [Uri-review] ws: and wss: schemes

David Booth <david@dbooth.org> Wed, 09 September 2009 14:17 UTC

Return-Path: <david@dbooth.org>
X-Original-To: uri-review@core3.amsl.com
Delivered-To: uri-review@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 178DF3A6C0E for <uri-review@core3.amsl.com>; Wed, 9 Sep 2009 07:17:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.98
X-Spam-Level:
X-Spam-Status: No, score=-2.98 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9O+F5Y0NZDpv for <uri-review@core3.amsl.com>; Wed, 9 Sep 2009 07:17:40 -0700 (PDT)
Received: from relay00.pair.com (relay00.pair.com [209.68.5.9]) by core3.amsl.com (Postfix) with SMTP id 07DFE3A697B for <uri-review@ietf.org>; Wed, 9 Sep 2009 07:17:39 -0700 (PDT)
Received: (qmail 91868 invoked from network); 9 Sep 2009 14:18:11 -0000
Received: from 192.35.79.70 (HELO ?10.78.165.46?) (192.35.79.70) by relay00.pair.com with SMTP; 9 Sep 2009 14:18:11 -0000
X-pair-Authenticated: 192.35.79.70
From: David Booth <david@dbooth.org>
To: "Daniel R. Tobias" <dan@tobias.name>
In-Reply-To: <4AA70134.28006.1928A41F@dan.tobias.name>
References: <OF22CD1320.96C55266-ON85257610.004AB599-85257610.004BC9CA@lotus.com> , <4AA2A630.32731.824DABF@dan.tobias.name> , <1252444455.16404.646.camel@dbooth-laptop> <4AA70134.28006.1928A41F@dan.tobias.name>
Content-Type: text/plain
Date: Wed, 09 Sep 2009 10:18:11 -0400
Message-Id: <1252505891.16404.743.camel@dbooth-laptop>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.1
Content-Transfer-Encoding: 7bit
Cc: URI <uri@w3.org>, hybi@ietf.org, uri-review@ietf.org
Subject: Re: [Uri-review] ws: and wss: schemes
X-BeenThere: uri-review@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Proposed URI Schemes <uri-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/uri-review>, <mailto:uri-review-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/uri-review>
List-Post: <mailto:uri-review@ietf.org>
List-Help: <mailto:uri-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/uri-review>, <mailto:uri-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Sep 2009 14:17:41 -0000

On Tue, 2009-09-08 at 21:13 -0400, Daniel R. Tobias wrote:
> I wonder if the "HTTP Uber Alles" crowd, if they were active 20 years 
> ago, would be insisting that everything, including that newfangled 
> HTTP protocol, be expressed in the form of a Gopher address, or 
> perhaps FTP or Telnet, or maybe an e-mail address with the standard, 
> adopted by the owner of the address, that the subject line contain 
> the actual protocol intended to be used?
> 
> I also wonder if, should their side win all its battles, 1000 years 
> from now all URIs in use will be at least 1000 characters long, of 
> which at least 800 of these characters will be fossilized deadwood of 
> obsolete protocols that are preserved as magic incantations to begin 
> a URI.  So they'll be something like:
> 
> http://ipp.solarsystem.net/earth/galacticgateway.net/andromeda/tachyon
> .protocol.net/ ...[snip]... /actualsite.actualgalaxy/path-in-site
> 
> where "ipp.solarsystem.net", under "http", is the magic indicator of 
> the InterPlanetaryProtocol that became dominant in 2067, and was 
> followed by the actual address being reached by that protocol, 
> starting with its home planet, but then "galacticgateway.net" within 
> "earth" became the magic string to indicate that you are actually 
> using the InterGalacticProtocol which became dominant in 2152, and 
> similarly the "tachyon.protocol.net" signifies the Tachyon Protocol 
> that caught on around 2272.
> 
> User agent identifiers for the browsers people use with their 31st 
> century protocols are similarly long and convoluted, beginning with 
> "Mozilla/5.0" and containing references to MSIE, Gecko, and various 
> other browser names and codenames that were trendy at some point or 
> other over the millennium.

History is riddled with discarded protocols, the proponents of which
naively thought that *their* protocol was so important that they needed
to invent a whole new naming scheme for it.  

If the Tachyon Protocol does become dominant in 2272 it will be a simple
matter to define a new URI scheme, so that Tachyon URIs can be shortened
henceforth.  (That's the *easy* part.  The hard part was convincing the
186,000 makers of nearly 4.2 trillion devices to *implement* the Tachyon
Protocol.)  But until that point, there is greater value in layering the
Tachyon Protocol on top of the dominant protocol, whether that happens
to be HTTP or the InterPlanetaryProtocol.

There is nothing intrinsically special about HTTP.  What matters is just
that it is so widely implemented.  That's what the network effect is all
about.


-- 
David Booth, Ph.D.
Cleveland Clinic (contractor)

Opinions expressed herein are those of the author and do not necessarily
reflect those of Cleveland Clinic.