Re: [Uri-review] ssh URI

Ted Hardie <ted.ietf@gmail.com> Tue, 13 October 2009 19:19 UTC

Return-Path: <ted.ietf@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 0B2A728C312 for <uri-review@core3.amsl.com>; Tue, 13 Oct 2009 12:19:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_38=0.6]
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 tPqM7mh2AJng for <uri-review@core3.amsl.com>; Tue, 13 Oct 2009 12:19:56 -0700 (PDT)
Received: from mail-px0-f176.google.com (mail-px0-f176.google.com [209.85.216.176]) by core3.amsl.com (Postfix) with ESMTP id 4D4DA28C2F3 for <uri-review@ietf.org>; Tue, 13 Oct 2009 12:19:56 -0700 (PDT)
Received: by pxi6 with SMTP id 6so428177pxi.31 for <uri-review@ietf.org>; Tue, 13 Oct 2009 12:19:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=xb33rsPRRAPd6/srttxr1fjT004Qav+l3yNtzsE5DG4=; b=mehUEIiEfEjiaMli4P+8JmUW5Cjhyxh27IA/Kkh4joh0s5NHiWixpYgC2lcCYFJYvD +RFSjR8CWFPx/DKZUw8mPKulNOXLuVRm+MMhRC2IPuAtMXRNaFtyyqXifa+S+koW5G/v Y4cjo6IGd4GwLaav9pmcSpbhA7nqOeDzurb3s=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=WT4ty1oboumzgul/c9Wpraazd2GZYWYEwpjXF/j2h3YsBKePMQvCv0kNqrApex0Gl/ CTeT1PXWoUACKk5bvhU+ZMz0qdyN79W/lcQDrsvuRmVtgqmWr3TEAqlsCp6Bhw8vtc5i uDF9tCzI6ZZTwlbJmF8EEkBMUOyW61wQXm4Kw=
MIME-Version: 1.0
Received: by 10.142.150.41 with SMTP id x41mr578004wfd.243.1255461594246; Tue, 13 Oct 2009 12:19:54 -0700 (PDT)
In-Reply-To: <eb19f3360910130044q59145662m5d683b0589119cea@mail.gmail.com>
References: <20091009160149.GB16908@braingia.org> <1255366894.5481.8445.camel@dbooth-laptop> <5EAB4D387A4A4B7C854FBD1869729771@POCZTOWIEC> <1255395156.5481.10083.camel@dbooth-laptop> <eb19f3360910130044q59145662m5d683b0589119cea@mail.gmail.com>
Date: Tue, 13 Oct 2009 12:19:54 -0700
Message-ID: <6e04e83a0910131219h457e720cx641ab494f69259a7@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
To: Dan Brickley <danbri@danbri.org>
Content-Type: text/plain; charset="ISO-8859-1"
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: Tue, 13 Oct 2009 19:19:57 -0000

While I applaud the basic sentiment of not having this discussion
every time a new URI scheme comes up, I think you'd have to persuade
the IETF rather than the TAG.  The IETF is responsible for URI
registration, and the documents are pretty clear on that point.  The
IESG and IAB take the TAG's input very seriously, of course, but the
question of URI registration is one where there has been divergence
for some time.  As the discussion above notes, having HTTP always in
the URI loop may make sense for the web; it doesn't work for other
deployments and other protocols.

I personally agree with those saying ssh ought to be an independent
scheme.  It has a widely installed user base and I have seen
individuals use ssh:hostname as a pseudo-URI for some time.  Pushing
out a real spec for the URI scheme would avoid interoperability
problems there, and that in itself is goodness.

2 cents from:

Ted Hardie

On Tue, Oct 13, 2009 at 12:44 AM, Dan Brickley <danbri@danbri.org> wrote:
> [snip]
>
> David,
>
> Can I suggest a new workflow for these ideas?
>
> Instead of intervening when every new URI scheme proposal comes
> through these lists, perhaps you could work to persuade the W3C TAG of
> them instead? I think I understand where you're coming from, but the
> approach is pretty alien to URIs as currently deployed, particularly
> with regard to browser infrastructure, which at the moment is
> universally keyed off of the scheme prefix and unlikely to change
> rapidly due to the huge security implications.
>
> There might be something in these ideas (though I remain generally
> skeptical when it comes to protocols - such as ssh - rather than
> content/object identifiers eg. doi, xri, ...). At the moment they're
> being discussed in an ad hoc way whenever someone proposes a new
> scheme. Could it be more efficient to propose and refine them through
> the TAG, perhaps?
>
> cheers,
>
> Dan
> _______________________________________________
> Uri-review mailing list
> Uri-review@ietf.org
> https://www.ietf.org/mailman/listinfo/uri-review
>