Re: [apps-discuss] The state of 'afs' URi scheme

Ben Niven-Jenkins <ben@niven-jenkins.co.uk> Tue, 01 February 2011 15:47 UTC

Return-Path: <ben@niven-jenkins.co.uk>
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 AE3DC3A6E0F for <apps-discuss@core3.amsl.com>; Tue, 1 Feb 2011 07:47:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.539
X-Spam-Level:
X-Spam-Status: No, score=-103.539 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 I7vZsVjPUm3y for <apps-discuss@core3.amsl.com>; Tue, 1 Feb 2011 07:47:16 -0800 (PST)
Received: from mailex.mailcore.me (mailex.mailcore.me [94.136.40.61]) by core3.amsl.com (Postfix) with ESMTP id 182183A6E86 for <apps-discuss@ietf.org>; Tue, 1 Feb 2011 07:46:40 -0800 (PST)
Received: from host1.cachelogic.com ([212.44.43.80] helo=dhcp-113-devlan.cachelogic.com) by mail11.atlas.pipex.net with esmtpa (Exim 4.71) (envelope-from <ben@niven-jenkins.co.uk>) id 1PkIUO-0006Yd-Bu; Tue, 01 Feb 2011 15:49:56 +0000
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
In-Reply-To: <4D48267A.1030800@gmail.com>
Date: Tue, 1 Feb 2011 15:49:54 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <96CC61EE-81BD-43CB-A83F-78E67B2DA7A5@niven-jenkins.co.uk>
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>
To: Mykyta Yevstifeyev <evnikita2@gmail.com>
X-Mailer: Apple Mail (2.1082)
X-Mailcore-Auth: 9600544
X-Mailcore-Domain: 172912
Cc: apps-discuss@ietf.org
Subject: Re: [apps-discuss] 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: Tue, 01 Feb 2011 15:47:17 -0000

Mykyta,

This will be my last mail on this topic as I've spent too long on it already.

On 1 Feb 2011, at 15:27, Mykyta Yevstifeyev wrote:
> 01.02.2011 17:23, Ben Niven-Jenkins wrote:
>> 
>> So you've saved an I-D being written but still used IESG time which could be much better spent on other things that actually provide value to the community.
> I really do not consider the action I propose as that 'requires great amount of time'.  Moreover, there is a strong consensus it is not used and will not be used so no problems will appear, IMO.

Let me be more explicit. IMO spending any amount of time >0 on this is pointless.
 
>> Also, you failed to answer the question I asked though, namely:
>>>> What is the real value and benefit in doing all the work to move them to historic? No one uses them so no one benefits from tweaking the category they are placed in IMO.
>> Unless there is a good answer to that question to justify changing their classification, I don't see any point in spending time discussing how one might go about reclassifying them.
> You should better ask the authors of RFC 4395 this, but not me.  If this wasn't needed, it wouldn't appear here.

RFC4395 states "Any scheme that is no longer in common use MAY be designated as historical". You're the one pushing for that optional action to be taken, not the authors of RFC4395 so you're the one that should justify why it is worthwhile taking that action.

Ben