Re: [Uri-review] ssh URI

Bob Aman <bob@sporkmonger.com> Tue, 13 October 2009 01:16 UTC

Return-Path: <sporkmonger@gmail.com>
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 46EFA3A69B9 for <uri-review@core3.amsl.com>; Mon, 12 Oct 2009 18:16:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.793
X-Spam-Level:
X-Spam-Status: No, score=-1.793 tagged_above=-999 required=5 tests=[AWL=0.184, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 hCxpRStGAq10 for <uri-review@core3.amsl.com>; Mon, 12 Oct 2009 18:16:36 -0700 (PDT)
Received: from mail-yx0-f199.google.com (mail-yx0-f199.google.com [209.85.210.199]) by core3.amsl.com (Postfix) with ESMTP id 71D593A68AC for <uri-review@ietf.org>; Mon, 12 Oct 2009 18:16:36 -0700 (PDT)
Received: by yxe37 with SMTP id 37so3267308yxe.31 for <uri-review@ietf.org>; Mon, 12 Oct 2009 18:16:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:reply-to:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=QCnIFuCAG52P9prNnlWOPtbAPGKQ0hNL2kBzvf7T+Go=; b=BBSJekOgXZ5LKv/AV8Ax+G+do/3cdduXzRZIhgXVMiR0p33RW4sCuRSihb+L5lMP6q OzNAsfXruuWacGldOA5GHHK+GsDOJVedrTBDS2spS0+xqSy1H8hPefww2pVxDT3/iwhv Is8QNj+bkvXIgJ3GsYT7WEB40p5EpJ4c/pICA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:reply-to:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=b/BeF+TK00Z9ZhUzOe9W4tSEw/S7I4znYLYnJ/e0zIWzAuhE2gTf4MencHjBsI3+j6 gkpbWfHmUptM4M9DZAARAXkwMK2IMBZSZWCGVdV4al+Eq/Q0ZR9tRnJF0pUe77xhceej UX14D7FF6z1RUx5EyXM6P7PQonp+FJa2bqAL4=
MIME-Version: 1.0
Sender: sporkmonger@gmail.com
Received: by 10.150.61.15 with SMTP id j15mr11337775yba.154.1255396593126; Mon, 12 Oct 2009 18:16:33 -0700 (PDT)
In-Reply-To: <1255395156.5481.10083.camel@dbooth-laptop>
References: <20091009160149.GB16908@braingia.org> <1255366894.5481.8445.camel@dbooth-laptop> <5EAB4D387A4A4B7C854FBD1869729771@POCZTOWIEC> <1255395156.5481.10083.camel@dbooth-laptop>
Date: Mon, 12 Oct 2009 21:16:33 -0400
X-Google-Sender-Auth: cfc047dcb6543188
Message-ID: <81c242240910121816y4becb1aevae5008b23537df2c@mail.gmail.com>
From: Bob Aman <bob@sporkmonger.com>
To: David Booth <david@dbooth.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
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
Reply-To: bob@sporkmonger.com
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: Tue, 13 Oct 2009 01:16:37 -0000

>  - Downloadable software that would cause the browser to recognize such
> URIs in the future, and handle them appropriately (i.e., by opening a
> secure shell, rather than by fetching a page from sshuri.org).
> Furthermore, such software might even be programmed to recognize and
> handle the "ssh:" URI scheme as well.

I have a problem with this in the general case because I don't think
there's currently a way for such a URI to be registered to a specific
application in any major browser.  And for the specific case, I can
think of at least one use case where you might want to link to an ssh
URI in a browser:  HTTP-based admin interfaces to machines.

And I'll also repeat my previous comment for emphasis:  This concept
is just confusing.

-1 to the concept of using anything under the http/https scheme to
formally represent an ssh identifier.

-Bob Aman