Re: [Uri-review] ssh URI

David Booth <david@dbooth.org> Mon, 12 October 2009 17:42 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 DCC453A68F3 for <uri-review@core3.amsl.com>; Mon, 12 Oct 2009 10:42:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.134
X-Spam-Level:
X-Spam-Status: No, score=-3.134 tagged_above=-999 required=5 tests=[AWL=0.465, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 ZqV6ffX7ySng for <uri-review@core3.amsl.com>; Mon, 12 Oct 2009 10:42:33 -0700 (PDT)
Received: from relay02.pair.com (relay02.pair.com [209.68.5.16]) by core3.amsl.com (Postfix) with SMTP id D7EA33A68EC for <uri-review@ietf.org>; Mon, 12 Oct 2009 10:42:31 -0700 (PDT)
Received: (qmail 74811 invoked from network); 12 Oct 2009 17:42:31 -0000
Received: from 209.6.102.232 (HELO ?192.168.7.2?) (209.6.102.232) by relay02.pair.com with SMTP; 12 Oct 2009 17:42:31 -0000
X-pair-Authenticated: 209.197.102.232
From: David Booth <david@dbooth.org>
To: Dan Brickley <danbri@danbri.org>
In-Reply-To: <eb19f3360910121007i7f533958ycae1ffbfbeac4307@mail.gmail.com>
References: <20091009160149.GB16908@braingia.org> <1255366894.5481.8445.camel@dbooth-laptop> <eb19f3360910121007i7f533958ycae1ffbfbeac4307@mail.gmail.com>
Content-Type: text/plain
Date: Mon, 12 Oct 2009 13:42:30 -0400
Message-Id: <1255369350.5481.8560.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: Mon, 12 Oct 2009 17:42:35 -0000

On Mon, 2009-10-12 at 19:07 +0200, Dan Brickley wrote:
> On Mon, Oct 12, 2009 at 7:01 PM, David Booth <david@dbooth.org> wrote:
> > I don't see a need to define a new URI scheme for this.  You can just
> > define an http URI prefix for this purpose, as described in
> > http://dbooth.org/2006/urn2http/
> >
> > Furthermore, as Graham Klyne suggested during a similar discussion
> > earlier, "an HTTP URI can also retrieve a protocol [handler]
> > implementation"
> > http://lists.w3.org/Archives/Public/uri/2009Sep/0029.html
> > This could dramatically improve the adoption rate of a new protocol.
> 
> You'd really be advocating retrieval of SSH protocol handlers over
> untrusted HTTP connections? That's brave or something!

Good point.  For this application one would presumably choose an HTTP
URI prefix that starts with "https:" rather than "http:".  :)



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

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