Re: [Uri-review] [apps-discuss] Provisional URI registrations

"Martin J. Dürst" <duerst@it.aoyama.ac.jp> Mon, 22 November 2010 06:51 UTC

Return-Path: <duerst@it.aoyama.ac.jp>
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 2582B3A6A0E for <uri-review@core3.amsl.com>; Sun, 21 Nov 2010 22:51:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.421
X-Spam-Level:
X-Spam-Status: No, score=-100.421 tagged_above=-999 required=5 tests=[AWL=-0.631, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
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 iPO-2FK6BRfH for <uri-review@core3.amsl.com>; Sun, 21 Nov 2010 22:51:01 -0800 (PST)
Received: from scintmta02.scbb.aoyama.ac.jp (scintmta02.scbb.aoyama.ac.jp [133.2.253.34]) by core3.amsl.com (Postfix) with ESMTP id B218A3A6A39 for <uri-review@ietf.org>; Sun, 21 Nov 2010 22:50:51 -0800 (PST)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta02.scbb.aoyama.ac.jp (secret/secret) with SMTP id oAM6pfed004873 for <uri-review@ietf.org>; Mon, 22 Nov 2010 15:51:41 +0900
Received: from (unknown [133.2.206.133]) by scmse02.scbb.aoyama.ac.jp with smtp id 649f_5406_f658f0fc_f604_11df_a0ab_001d096c5782; Mon, 22 Nov 2010 15:51:41 +0900
Received: from [IPv6:::1] ([133.2.210.1]:51715) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S148C926> for <uri-review@ietf.org> from <duerst@it.aoyama.ac.jp>; Mon, 22 Nov 2010 15:51:41 +0900
Message-ID: <4CEA12F9.2090106@it.aoyama.ac.jp>
Date: Mon, 22 Nov 2010 15:51:37 +0900
From: "\"Martin J. Dürst\"" <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
References: <A232FF7C06EE5B1C0F886130@PST.JCK.COM> <4CE99C5D.9040601@ninebynine.org> <4CE9BDCA.4010202@it.aoyama.ac.jp> <D8FA9230788A44981E86132F@PST.JCK.COM>
In-Reply-To: <D8FA9230788A44981E86132F@PST.JCK.COM>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Cc: "public-iri@w3.org" <public-iri@w3.org>, uri-review@ietf.org, Graham Klyne <GK@ninebynine.org>, apps-discuss@ietf.org
Subject: Re: [Uri-review] [apps-discuss] Provisional URI registrations
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, 22 Nov 2010 06:51:02 -0000

Hello John, others,

(cc'ing the IRI WG mailing list, because it is chartered to work on an 
update of RFC 4395 (Guidelines and Registration Procedures for New URI 
Schemes); please reduce cc list in replies whenever possible)

On 2010/11/22 12:41, John C Klensin wrote:
>
>
> --On Monday, November 22, 2010 09:48 +0900 "\"Martin J.
> Dürst\""<duerst@it.aoyama.ac.jp>  wrote:
>
>> On 2010/11/22 7:25, Graham Klyne wrote:
>>
>>> We have "permanent", "provisional" and "historical"
>>> registration classes for URI schemes. For practical purposes,
>>> I think the "provisional" registry serves the same role as
>>> the "reserved" one you suggest [1]. I think the additional
>>> bureaucracy incurred to create a new registry class is not
>>> justified by practical benefit.
>>
>> +1.
>
> I would agree, except that:
>
> (1) We now have proposals to remove things from Provisional that
> have well-defined protocol specs and evidence of use because
> they have been Provisional too long.  Fighting battles of that
> sort is lots more painful than setting up a new registry
> category, especially since...

I don't think fighting such battles should be painful. If A says a 
scheme (or protocol) is no longer in use, and B say it's in use, then B 
just wins. Having to say "the scheme (or protocol) is still in use" 
every two years or so may indeed some pain, but not too much.

> (2) Not having a Reserved category from the beginning appears to
> be an error on IANA's part, not something the IETF specified in
> any way.

In what way is it IANA's error? RFC 4395 
(http://tools.ietf.org/html/rfc4395) is pretty clear (as Graham has 
already explained) that there are three categories: Permanent, 
Provisional, and Historical.

> If that is correct, it should be possible to deal
> with it as correcting an error, which is (or should be) an
> extremely lightweight procedure.

I don't understand how it could be correct, but maybe I'm missing 
something. Anyway, I encourage everybody who thinks an additional 
Reserved category is needed, or some other clarifications could help, to 
submit their proposal as an issue on draft-ietf-iri-4395bis-irireg 
(http://tools.ietf.org/html/draft-ietf-iri-4395bis-irireg (Guidelines 
and Registration Procedures for New URI/IRI Schemes)) to the IRI WG 
(mailing list address: public-iri@w3.org). The current list of active 
issues of the WG can be found at 
http://trac.tools.ietf.org/wg/iri/trac/report/1.

Regards,   Martin.

-- 
#-# Martin J. Dürst, Professor, Aoyama Gakuin University
#-# http://www.sw.it.aoyama.ac.jp   mailto:duerst@it.aoyama.ac.jp