Re: [Uri-review] ssh URI

Eliot Lear <lear@cisco.com> Mon, 12 October 2009 17:50 UTC

Return-Path: <lear@cisco.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 1A5063A693D for <uri-review@core3.amsl.com>; Mon, 12 Oct 2009 10:50:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 VDosbxF-j5fr for <uri-review@core3.amsl.com>; Mon, 12 Oct 2009 10:50:14 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 4713A3A68EC for <uri-review@ietf.org>; Mon, 12 Oct 2009 10:50:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=lear@cisco.com; l=4589; q=dns/txt; s=amsiport01001; t=1255369815; x=1256579415; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20Eliot=20Lear=20<lear@cisco.com>|Subject:=20Re: =20[Uri-review]=20ssh=20URI|Date:=20Mon,=2012=20Oct=20200 9=2019:50:13=20+0200|Message-ID:=20<4AD36C55.5060903@cisc o.com>|To:=20David=20Booth=20<david@dbooth.org>|CC:=20Ste ve=20Suehring=20<suehring@braingia.org>,=20uri-review@iet f.org,=20uri@w3.org|MIME-Version:=201.0|In-Reply-To:=20<1 255366894.5481.8445.camel@dbooth-laptop>|References:=20<2 0091009160149.GB16908@braingia.org>=20<1255366894.5481.84 45.camel@dbooth-laptop>; bh=tRQ05T9jmqFaWyzTwZRd4sPKpg4sjhaZFjrz2HI3TYk=; b=BSXQpnZtiqVydeiBvjQbSXlkE/j48Y+K/qC7cGgAcDc4OUSDZYEP9UzK kg2rzv8KDsr/mkMZ80Gji7eKoYyxR885XKE16sO+8qUapj9VSXKwvB/+F 6aHOS4LWNZxmXf0TJB4lCkPEFWfxeT+cHu69EyZINxne1mrVqsbLQSCpB o=;
Authentication-Results: ams-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Al8AACcJ00qQ/uCWe2dsb2JhbACBUlMwmDgBARYkBqQtlwiELQSEOw
X-IronPort-AV: E=Sophos; i="4.44,547,1249257600"; d="scan'208,217"; a="51574187"
Received: from ams-core-1.cisco.com ([144.254.224.150]) by ams-iport-1.cisco.com with ESMTP; 12 Oct 2009 17:50:13 +0000
Received: from elear-mac.local (dhcp-10-61-100-124.cisco.com [10.61.100.124]) by ams-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n9CHoD3Y007814; Mon, 12 Oct 2009 17:50:13 GMT
Message-ID: <4AD36C55.5060903@cisco.com>
Date: Mon, 12 Oct 2009 19:50:13 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.4pre) Gecko/20091003 Shredder/3.0pre
MIME-Version: 1.0
To: David Booth <david@dbooth.org>
References: <20091009160149.GB16908@braingia.org> <1255366894.5481.8445.camel@dbooth-laptop>
In-Reply-To: <1255366894.5481.8445.camel@dbooth-laptop>
Content-Type: multipart/alternative; boundary="------------080505050608090106050903"
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:50:18 -0000

David,

I see some definite negatives to what you are suggesting:

   1. Requires some sort of consortia or legal framework.
   2. Requires an additional resolution.  SSH is commonly used for
      administration, and so I would be loathe to add that sort of step.
   3. Requires ssh applications to understand HTTP URI schema.

Or do I misread what you are suggesting?

Eliot



On 10/12/09 7:01 PM, David Booth 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.
>
> David Booth
>
>
> On Fri, 2009-10-09 at 11:01 -0500, Steve Suehring wrote:
>    
>> Hello,
>>
>> Attached is a draft to be submitted to the IETF for URI scheme related
>> to secure shell (ssh).  The draft was originally included in the secsh
>> Working Group which has since concluded.
>>
>> http://tools.ietf.org/wg/secsh/draft-ietf-secsh-scp-sftp-ssh-uri/
>>
>> I recently received a request to pick this draft back up and the
>> co-author and I will be submitting it to the IETF under the Application
>> Area.
>>
>> Please provide feedback as appropriate.
>>
>> Thank you for your time.
>>
>> Steve Suehring
>> _______________________________________________
>> Uri-review mailing list
>> Uri-review@ietf.org
>> https://www.ietf.org/mailman/listinfo/uri-review
>>