Re: [Uri-review] ssh URI

David Booth <david@dbooth.org> Wed, 14 October 2009 04:19 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 88B9C3A6819 for <uri-review@core3.amsl.com>; Tue, 13 Oct 2009 21:19:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.321
X-Spam-Level:
X-Spam-Status: No, score=-3.321 tagged_above=-999 required=5 tests=[AWL=-0.037, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_MILLIONSOF=0.315]
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 6FTaPv6hHG-1 for <uri-review@core3.amsl.com>; Tue, 13 Oct 2009 21:19:42 -0700 (PDT)
Received: from relay01.pair.com (relay01.pair.com [209.68.5.15]) by core3.amsl.com (Postfix) with SMTP id 6D6953A687A for <uri-review@ietf.org>; Tue, 13 Oct 2009 21:19:42 -0700 (PDT)
Received: (qmail 6638 invoked from network); 14 Oct 2009 04:19:42 -0000
Received: from 209.6.102.232 (HELO ?192.168.7.2?) (209.6.102.232) by relay01.pair.com with SMTP; 14 Oct 2009 04:19:42 -0000
X-pair-Authenticated: 209.197.102.232
From: David Booth <david@dbooth.org>
To: John Cowan <cowan@ccil.org>
In-Reply-To: <20091013042705.GG13660@mercury.ccil.org>
References: <20091009160149.GB16908@braingia.org> <1255366894.5481.8445.camel@dbooth-laptop> <5EAB4D387A4A4B7C854FBD1869729771@POCZTOWIEC> <1255395156.5481.10083.camel@dbooth-laptop> <81c242240910121816y4becb1aevae5008b23537df2c@mail.gmail.com> <1255398140.5481.10279.camel@dbooth-laptop> <81c242240910121855q52319dbatafb6ee46c3364ed@mail.gmail.com> <1255406578.5481.10704.camel@dbooth-laptop> <20091013042705.GG13660@mercury.ccil.org>
Content-Type: text/plain
Date: Wed, 14 Oct 2009 00:19:39 -0400
Message-Id: <1255493979.25337.3056.camel@dbooth-laptop>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.1
Content-Transfer-Encoding: 7bit
Cc: uri-review@ietf.org, uri@w3.org
Subject: Re: [Uri-review] ssh URI
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, 14 Oct 2009 04:19:43 -0000

On Tue, 2009-10-13 at 00:27 -0400, John Cowan wrote:
> David Booth scripsit:
> 
> > Getting a scheme registered is the *easy* part.  The hard part is
> > getting millions of installed clients to implement the special
> > recognition of that scheme.
> 
> No harder than getting them to recognize a load-ssh-protocol-driver
> meta-scheme.

I disagree.  If a client doesn't recognize a new scheme, the user has
little choice but to search around for an implementation or hope that
the client vendor adds support for it in the future.  But if an http URI
is used, the URI (as a fallback) could dereference directly to a page
providing information about those new URIs, where to download client
software that supports them, and -- potentially -- even attempt to
auto-download a client extension for them.  This certainly seems like it
would encourage faster adoption.


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

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