Re: [apps-discuss] URI registry (was: Re: The state of 'afs' URi scheme)

"Martin J. Dürst" <duerst@it.aoyama.ac.jp> Thu, 10 February 2011 05:57 UTC

Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8D9873A68A6 for <apps-discuss@core3.amsl.com>; Wed, 9 Feb 2011 21:57:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.501
X-Spam-Level:
X-Spam-Status: No, score=-97.501 tagged_above=-999 required=5 tests=[AWL=-1.366, BAYES_00=-2.599, FRT_ADOBE2=2.455, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, J_CHICKENPOX_15=0.6, J_CHICKENPOX_23=0.6, 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 Njz+V5aSZFyC for <apps-discuss@core3.amsl.com>; Wed, 9 Feb 2011 21:57:27 -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 A69D63A6896 for <apps-discuss@ietf.org>; Wed, 9 Feb 2011 21:57:26 -0800 (PST)
Received: from scmse01.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta02.scbb.aoyama.ac.jp (secret/secret) with SMTP id p1A5vWTj030886 for <apps-discuss@ietf.org>; Thu, 10 Feb 2011 14:57:32 +0900
Received: from (unknown [133.2.206.133]) by scmse01.scbb.aoyama.ac.jp with smtp id 2324_9adf_a6cf979c_34da_11e0_81e4_001d096c566a; Thu, 10 Feb 2011 14:57:32 +0900
Received: from [IPv6:::1] ([133.2.210.1]:33353) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S14CC31A> for <apps-discuss@ietf.org> from <duerst@it.aoyama.ac.jp>; Thu, 10 Feb 2011 14:57:32 +0900
Message-ID: <4D537E48.9030403@it.aoyama.ac.jp>
Date: Thu, 10 Feb 2011 14:57:28 +0900
From: =?ISO-8859-1?Q?=22Martin_J=2E_D=FCrst=22?= <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: "t.petch" <ietfc@btconnect.com>
References: %3C4D26B005.2060909@gmail.com%3E <4D2C7755.5080908@gmail.com> <81F42F63D5BB344ABF294F8E80990C7902782BBA@MTV-EXCHANGE.microfocus.com> <4D455380.6040103@gmail.com> <3792F8F3-D01B-4B05-9E73-59228F09FE5C@gbiv.com> <4D464EA4.7090303@gmail.com> <7ED44745-7DBA-4372-BE39-22061DC26DF2@gbiv.com> <4D46CE52.6030503@vpnc.org> <4D47DD4A.7040503@gmail.com> <06BA884E-D1C7-4783-BBE6-A6B21DE013B7@niven-jenkins.co.uk> <4D482071.8050202@gmail.com> <CDAB7832-EBF9-4ECE-B8D1-09BA39BDF4B8@niven-jenkins.co.uk> <4D48267A.1030800@gmail.com> <96CC61EE-81BD-43CB-A83F-78E67B2DA7A5@niven-jenkins.co.uk> <C68CB012D9182D408CED7B884F441D4D058EEE61B9@nambxv01a.corp.adobe.com> <026901cbc781$a2724ee0$4001a8c0@gateway.2wire.net> <4D520AE6.8070502@it.aoyama.ac.jp> <000901cbc867$7a9d31a0$4001a8c0@gateway.2wire.net>
In-Reply-To: <000901cbc867$7a9d31a0$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: public-iri@w3.org, apps-discuss@ietf.org
Subject: Re: [apps-discuss] URI registry (was: Re: The state of 'afs' URi scheme)
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Feb 2011 05:57:30 -0000

[Responding one more time here because this is a metadiscussion; please 
move the discussion to public-iri@w3.org (the mailing list of the IETF 
IRI WG). Please also see 
http://trac.tools.ietf.org/wg/iri/trac/ticket/54 and 
http://trac.tools.ietf.org/wg/iri/trac/ticket/55 for the two issues this 
has resulted in]

On 2011/02/10 6:38, t.petch wrote:
>
> ----- Original Message -----
> From: "Martin J. Dürst"<duerst@it.aoyama.ac.jp>
> To: "t.petch"<ietfc@btconnect.com>
> Cc: "Larry Masinter"<masinter@adobe.com>; "Ben Niven-Jenkins"
> <ben@niven-jenkins.co.uk>;<apps-discuss@ietf.org>;<public-iri@w3.org>
> Sent: Wednesday, February 09, 2011 4:32 AM
>
>> I'm cc'ing the IRI WG list. One of the deliverables of the IRI WG is an
>> update of RFC 4395. You can see the current version at
>> http://tools.ietf.org/html/draft-ietf-iri-4395bis-irireg-00.
>>
>> Given that there is a WG chartered to work on these issues, I suggest to
>> move the discussion there.
>
> Martin
>
> Well, the IRI charter says produce a new version of RFC4395, but looking
> at the details in the charter, I see no reference to RFC4395.

Yes, the charter contains no details about RFC4395, just that the WG 
will produce an update.

> Looking at rfc4395bis, the changes I see are 'URI includes IRI'
> which is good to have, but not really on the same scale as "let's
> change the IANA categories".

I don't think anybody has proposed a change in the categories itself. 
Some people just seem to have different ideas about what exactly the 
categories mean, so it's probably a good idea to clarify that. 
Clarifications of current text is about the lowest level of actual 
change I can imagine, and so I don't think there should be any problem 
with that. But of course I'm just a participant in that WG (and one of 
the editors of the other document of the WG), so it's ultimately not for 
me to decide.

As for the move of specific 'orphaned' schemes from one category to the 
other, I also see that as a very small scale issue.


> I would expect the WG chairs
> and AD to declare such activity ultra vires (but I might get
> a pleasant surprise:-).

I'd definitely like to hear from the WG chairs or the AD(s), but maybe 
first we have to have some discussion in the WG to see where we are 
headed, and to what extent we might potentially jump out of our charter 
fence.

Regards,   Martin.

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