Re: [Uri-review] URI scheme registration request - dchub

Graham Klyne <GK@ninebynine.org> Fri, 22 February 2013 15:30 UTC

Return-Path: <GK@ninebynine.org>
X-Original-To: uri-review@ietfa.amsl.com
Delivered-To: uri-review@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A97B121F8E53; Fri, 22 Feb 2013 07:30:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level:
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.149, BAYES_00=-2.599, WEIRD_PORT=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DpK1k4QnlPHj; Fri, 22 Feb 2013 07:30:43 -0800 (PST)
Received: from relay16.mail.ox.ac.uk (relay16.mail.ox.ac.uk [163.1.2.166]) by ietfa.amsl.com (Postfix) with ESMTP id BC1E921F8E2E; Fri, 22 Feb 2013 07:30:43 -0800 (PST)
Received: from smtp2.mail.ox.ac.uk ([163.1.2.205]) by relay16.mail.ox.ac.uk with esmtp (Exim 4.80) (envelope-from <GK@ninebynine.org>) id 1U8ua7-0005Hc-pr; Fri, 22 Feb 2013 15:30:39 +0000
Received: from gklyne.plus.com ([80.229.154.156] helo=conina.local) by smtp2.mail.ox.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <GK@ninebynine.org>) id 1U8ua6-0008Lp-9C; Fri, 22 Feb 2013 15:30:39 +0000
Message-ID: <51278B10.10200@ninebynine.org>
Date: Fri, 22 Feb 2013 15:13:20 +0000
From: Graham Klyne <GK@ninebynine.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: Fredrik Ullner <ullner@gmail.com>
References: <CAOd=0fOPCgEwPWxOm3QDn=QKe8Rb8RmShn5sEL3iBS_z6aOUXg@mail.gmail.com> <512663B2.20809@tibco.com> <CAOd=0fPuFsoTCh0mcYt_vVi-=Y5Or4oNQT+BYpKZv1zop0vdHA@mail.gmail.com>
In-Reply-To: <CAOd=0fPuFsoTCh0mcYt_vVi-=Y5Or4oNQT+BYpKZv1zop0vdHA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Oxford-Username: zool0635
Cc: uri-review@ietf.org, Bjoern Hoehrmann <derhoermi@gmx.net>, "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: Re: [Uri-review] URI scheme registration request - dchub
X-BeenThere: uri-review@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Proposed URI Schemes <uri-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Fri, 22 Feb 2013 15:30:44 -0000

On 21/02/2013 21:07, Fredrik Ullner wrote:
> On Thu, Feb 21, 2013 at 7:13 PM, Eric Johnson<eric@tibco.com>;  wrote:
>> >
>> >The protocol itself ought to be filed as an RFC. That would pretty much
>> >guarantee permanence of the reference.

> It has actually been discussed previously. I have a semi-complete document
> written, but it's far from complete. I am also unsure of how one would
> manage messages that are now not used by any implementation. If people
> would feel that that would be the best approach, then I'm all for it.

"Ought to be" maybe too strong, but if dchub is widely used and supported that's 
an option to consider.  But if you go down that route, be aware that in can be a 
lot of work preparing and herding a spec through full IETF review.  As Eric 
says, that would almost certainly justify making the URI scheme registration 
permanent.

> I would like to invite people for discussion to the DC community. There is
> a development forum athttp://dcbase.org  as well as the development talk
> hub at adcs://hub.dcbase.org:16591 (note that this is another URI scheme
> that is intended to be registered in the future). (Download the application
> DC++, press Ctrl+Q and enter the adcs:// address to join.) Is there perhaps
> an IRC channel otherwise where one can discuss these things?

I took a quick look.  It appears to be a vibrant developer community there, but 
I got a bit lost looking, e.g., for possible clues about interoperability of 
different implementations.

The adcs: reference wasn't useful to me, as my browser doesn't know what to do 
with it - this is a perennial problem with new URI schemes, and is one reason 
why there is some reluctance to allow new permanent schemes - it's extremely 
difficult and expensive to get new schemes widely deployed.

#g
--