Re: [Uri-review] ssh URI

Dan Brickley <danbri@danbri.org> Mon, 12 October 2009 19:59 UTC

Return-Path: <danbri@danbri.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 EFC533A6919 for <uri-review@core3.amsl.com>; Mon, 12 Oct 2009 12:59:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.185
X-Spam-Level:
X-Spam-Status: No, score=-0.185 tagged_above=-999 required=5 tests=[BAYES_40=-0.185]
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 5RU+UEapeILO for <uri-review@core3.amsl.com>; Mon, 12 Oct 2009 12:59:41 -0700 (PDT)
Received: from mail-ew0-f208.google.com (mail-ew0-f208.google.com [209.85.219.208]) by core3.amsl.com (Postfix) with ESMTP id 806EE3A690F for <uri-review@ietf.org>; Mon, 12 Oct 2009 12:59:38 -0700 (PDT)
Received: by ewy4 with SMTP id 4so2755717ewy.37 for <uri-review@ietf.org>; Mon, 12 Oct 2009 12:59:35 -0700 (PDT)
Received: by 10.211.172.8 with SMTP id z8mr7507949ebo.92.1255377575712; Mon, 12 Oct 2009 12:59:35 -0700 (PDT)
Received: from ?192.168.1.12? (s5590d015.adsl.wanadoo.nl [85.144.208.21]) by mx.google.com with ESMTPS id 10sm1193324eyz.4.2009.10.12.12.59.34 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 12 Oct 2009 12:59:35 -0700 (PDT)
References: <20091009160149.GB16908@braingia.org> <1255366894.5481.8445.camel@dbooth-laptop> <5EAB4D387A4A4B7C854FBD1869729771@POCZTOWIEC>
Message-Id: <5591CDCF-4AB3-4C49-9AA0-1EAA4CB7DAA1@danbri.org>
From: Dan Brickley <danbri@danbri.org>
To: Kristof Zelechovski <giecrilj@stegny.2a.pl>
In-Reply-To: <5EAB4D387A4A4B7C854FBD1869729771@POCZTOWIEC>
Content-Type: text/plain; charset="us-ascii"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
X-Mailer: iPhone Mail (7D11)
Mime-Version: 1.0 (iPhone Mail 7D11)
Date: Mon, 12 Oct 2009 21:59:48 +0200
X-Mailman-Approved-At: Tue, 13 Oct 2009 08:08:37 -0700
Cc: "<uri-review@ietf.org>" <uri-review@ietf.org>, "<uri@w3.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 19:59:42 -0000

On 12 Oct 2009, at 21:35, Kristof Zelechovski <giecrilj@stegny.2a.pl>  
wrote:

> David, you do not see a need to define a new URI scheme for  
> anything, do
> you?.  If I you do, please enumerate the requirements for a protocol  
> that
> would save it from the http black hole.
> SSH is not a new protocol, and the "adoption rate" does not depend  
> on the
> URI; it is an agreement between the owner and the user that counts.   
> This
> agreement already provides all technical information the user needs,  
> and
> explaining it over HTTP would not be useful.
> And how would you persuade the Web browser to send an HTTP SSH URI  
> to an
> external handler instead of navigating to it?  (Think Internet  
> Explorer, for
> clarity.)

...which in turn would have rather awkward privacy characteristics.

A custom scheme makes sense to me.

Dan