Re: [Uri-review] ssh URI

Steve Suehring <suehring@braingia.org> Wed, 14 October 2009 12:49 UTC

Return-Path: <suehring@braingia.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 9695D28C160 for <uri-review@core3.amsl.com>; Wed, 14 Oct 2009 05:49:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.265
X-Spam-Level:
X-Spam-Status: No, score=-2.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
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 bczoPT9nb2ti for <uri-review@core3.amsl.com>; Wed, 14 Oct 2009 05:49:33 -0700 (PDT)
Received: from dfw0.icgmedia.com (dfw0.icgmedia.com [69.93.3.2]) by core3.amsl.com (Postfix) with ESMTP id E359A28C149 for <uri-review@ietf.org>; Wed, 14 Oct 2009 05:49:32 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by dfw0.icgmedia.com (Postfix) with ESMTP id 3C9B31722A; Wed, 14 Oct 2009 07:49:36 -0500 (CDT)
X-Virus-Scanned: Debian amavisd-new at icgmedia.com
Received: from dfw0.icgmedia.com ([127.0.0.1]) by localhost (dfw0.icgmedia.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aDHgUvrUqawd; Wed, 14 Oct 2009 07:49:31 -0500 (CDT)
Received: from titania.braingia.org (66-190-11-170.dhcp.stpt.wi.charter.com [66.190.11.170]) by dfw0.icgmedia.com (Postfix) with ESMTP id 4661617228; Wed, 14 Oct 2009 07:49:31 -0500 (CDT)
Received: by titania.braingia.org (Postfix, from userid 1000) id 489C5A2008; Wed, 14 Oct 2009 07:49:28 -0500 (CDT)
Date: Wed, 14 Oct 2009 07:49:28 -0500
From: Steve Suehring <suehring@braingia.org>
To: David Booth <david@dbooth.org>
Message-ID: <20091014124928.GA16922@braingia.org>
References: <20091009160149.GB16908@braingia.org> <1255366894.5481.8445.camel@dbooth-laptop> <5EAB4D387A4A4B7C854FBD1869729771@POCZTOWIEC> <1255395156.5481.10083.camel@dbooth-laptop> <eb19f3360910130044q59145662m5d683b0589119cea@mail.gmail.com> <6e04e83a0910131219h457e720cx641ab494f69259a7@mail.gmail.com> <eb19f3360910131235oa2be24bs7a0d436345452008@mail.gmail.com> <1255494116.25337.3067.camel@dbooth-laptop>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <1255494116.25337.3067.camel@dbooth-laptop>
User-Agent: Mutt/1.5.18 (2008-05-17)
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 12:49:33 -0000

On Wed, Oct 14, 2009 at 12:21:56AM -0400, David Booth wrote:
>  - I actually think an ssh: scheme is one of the most justifiable
> proposals for a new scheme that I have seen lately, because ssh already
> has widespread adoption, and I would not be at all upset to see it go
> through.  In the long run it would be convenient.  But the ability to
> serve useful information and software as a fallback for clients that do
> not recognize SSH URIs is an undeniable benefit of http URIs, and I do
> not think any proposal for a new scheme should be considered complete
> without serious consideration of these potential benefits. 

David,

Thank you for your input on the http prefix for the ssh uri.  I think 
the general consensus and what I'm reading from your message indicates 
that we'll continue to move forward with the ssh draft as-is, opting for 
a new uri scheme as you indicate.  

We have some revisions to make to the draft itself based on feedback 
here about the location of the fingerprint and feedback from from the 
ssh working group mailing list.  When we get that revisions settled 
we'll submit it back to these mailing lists for a final walkthrough.

Thanks everyone for their input.

Steve