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

    * /To/: Ben Niven-Jenkins <ben at niven-jenkins.co.uk
      <mailto:ben@DOMAIN.HIDDEN>>, Mykyta Yevstifeyev <evnikita2 at
      gmail.com <mailto:evnikita2@DOMAIN.HIDDEN>>, apps-discuss
      <apps-discuss@ietf.org>
    * /Subject/: Re: [apps-discuss] The state of 'afs' URi scheme
    * /From/: Larry Masinter <masinter at adobe.com
      <mailto:masinter@DOMAIN.HIDDEN>>
    * /Date/: Mon, 7 Feb 2011 20:46:10 -0800

----Citation starts------

I think in general the overhead in maintaining current information about 
old registered values is too high, and that it *is* worth time thinking 
about how we could lower the overhead for registry maintenance.


There are a number of related issues raised about various registered 
values, including MIME type, charset, and URI schemes.

Ideally a registry is a place where a new implementor can go to discover 
both the theory and current practice for use of registered values on the 
internet. I think the current processes cope OK with theory (although 
the overhead of updating the registry when there is a new spec is high, 
it might be acceptable) but not with practice (where implementation and 
deployment sometimes is in advance of, or divergent from, the formal specs).

The situation is more acute in areas where protocols and formats are 
undergoing rapid development.

So I agree that writing a document marking 'afs' as 'obsolete' is 
make-work and not-worth anyone's time, but how could we make it easier 
(light-weight annotation) without subjecting ourselves to DOS of 
unreliable annotation?

Larry

----Citation ends------

I'm forwarding this message from apps-discuss list here since the 
discussion is also appropriate here.

Mykyta