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

Mykyta Yevstifeyev <> Tue, 01 February 2011 10:12 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id EBB033A6C39 for <>; Tue, 1 Feb 2011 02:12:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.208
X-Spam-Status: No, score=-3.208 tagged_above=-999 required=5 tests=[AWL=0.390, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id U+Kxwz1faQ8C for <>; Tue, 1 Feb 2011 02:12:01 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 57A863A6BBA for <>; Tue, 1 Feb 2011 02:12:01 -0800 (PST)
Received: by fxm9 with SMTP id 9so7222101fxm.31 for <>; Tue, 01 Feb 2011 02:15:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type; bh=689Muc6arhI4oGkrF2R+Ui2uuXdpQ10EPTzxfdmiJuU=; b=S5MSAREEL1FDtWWmwZuxCXZpiA+zv2gTx25UsMsyQClH9p4UiYU5bjjGtDaApLdnpV x92u4zUZl6Amj5kH7x0zTYIPUA3l6Ip8CEdZS6q+PFX8nHSzC0z/5DYhvbStuOdOpct0 3sEM00q23zQV+6EFgJyANgFF+R5dKkfj8pFrc=
DomainKey-Signature: a=rsa-sha1; c=nofws;; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type; b=bEJ0/2toGKMQjOmrBxlEae3H+agSvSGrqtBSIeX5f+rqIDkCyUqf0Gq00ZGQql1HZn T4UZd4zJMFMq6403ysfoIjVWBf5ydopUp8vuckVyrP4bhyybfOcg3GGRqy8NZMhqZZqt EzSRkI7ZvV+/A0ivXPmY3lFzWOxvjvmxC+kTE=
Received: by with SMTP id k10mr7254286faj.31.1296555317366; Tue, 01 Feb 2011 02:15:17 -0800 (PST)
Received: from [] ([]) by with ESMTPS id e17sm7756753fak.34.2011. (version=SSLv3 cipher=RC4-MD5); Tue, 01 Feb 2011 02:15:15 -0800 (PST)
Message-ID: <>
Date: Tue, 01 Feb 2011 12:15:38 +0200
From: Mykyta Yevstifeyev <>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv: Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Paul Hoffman <>
References: <> <> <> <> <> <> <>
In-Reply-To: <>
Content-Type: multipart/alternative; boundary="------------080402040107000700020406"
Subject: Re: [apps-discuss] The state of 'afs' URi scheme
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 01 Feb 2011 10:12:03 -0000

31.01.2011 16:59, Paul Hoffman wrote:
> On 1/31/11 12:28 AM, Roy T. Fielding wrote:
>> No, there is no reason to have that document either.  We don't need
>> these useless exercises in bit pushing -- there are plenty of other
>> drafts that need writing about actual protocols that were (and are)
>> used on the Web as identifiers.  afs, nfs, tn3270, and mailserver are
>> all examples of schemes that someone once thought might be a good idea,
>> but were in fact never used on the Internet.  They are obsolete.
> +1
> On 1/31/11 3:20 AM, Mykyta Yevstifeyev wrote:
> > Since these schemes are in Provisional category, it means that they are
> > 'waiting for specification'. If no-one specifies them, they should be
> > moved to Historical. That's clear, IMO.
> -1
> Mykyta, you are approximately the only person who seems to have a 
> problem understanding that standards organizations like the IETF 
> sometimes don't follow through on what they thought were good ideas 
> and sometimes don't document that. Your response is to generate many 
> useless efforts to clean up the IETF specs instead of just doing what 
> everyone else does, which is to ask a question, find the answer, and 
> move on. It feels like you are wasting lots of people's time for the 
> benefit of no one other than maybe yourself. (If there are others who 
> feel that Mykyta's efforts are worth our time, by all means speak up 
> and I'm happy to back down here.)
Paul, Roy, and all,

What RFC 4395 says is that all URI schemes ever registered fall into 
three categories: Permanent, Provisional and Historical.  There are no 
other cases the URI scheme may be classified as.

RFC 1738, in its Section 4 mentioned the 'afs' URI scheme as reserved 
for further specifying.  Following the creation of URI schemes registry 
the scheme was added to Provisional category, since it does not appear 
to appropriate for registration as Permanent or Historical.

RFC 4395 sets clear criteria for all the categories.  The 'afs' URI 
scheme may not be classified as Permanent, because of the lack of what 
mentioned in Section 2.1, 2.3, 2.4, 2.6 and 2.7 of RFC 4395.  This 
scheme is not appropriate for Provisional because of the points 
described in Section 3 of this document, especially the cited below:

>    o  If no permanent, citable specification for the URI scheme
>        definition is included, credible reasons for not providing it
>        should be given.
>     o  A valid Security Considerations section, as required by Section 6
>        of [3  <>].
>     o  If the scheme definition does not meet the guidelines laid out in
>        Section 2  <>, the differences and reasons SHOULD be noted.
Therefore, there are no other possibility either to remain it as 
Provisional or re-register it as Permanent.  Moreover, Section 4 mentions:

> once in use or registered but for whatever reason is no longer in
>     common use
and the 'afs' scheme meets these criteria.  So the conclusion is obvious.

As for the proposal to de-assign the scheme registration, the procedures 
for such action are not defined anywhere.

All the best,
Mykyta Yevstifeyev
> _______________________________________________
> apps-discuss mailing list