Re: [Uri-review] [Fwd: I-D Action:draft-melnikov-mailserver-uri-to-historic-00.txt]

Alfred Hönes <ah@TR-Sys.de> Wed, 17 November 2010 20:49 UTC

Return-Path: <A.Hoenes@TR-Sys.de>
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 597483A699E; Wed, 17 Nov 2010 12:49:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.094
X-Spam-Level:
X-Spam-Status: No, score=-98.094 tagged_above=-999 required=5 tests=[AWL=0.655, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, HELO_EQ_DE=0.35, 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 WVGDi1aNIO-U; Wed, 17 Nov 2010 12:49:09 -0800 (PST)
Received: from TR-Sys.de (gateway.tr-sys.de [213.178.172.147]) by core3.amsl.com (Postfix) with ESMTP id DE5A63A6998; Wed, 17 Nov 2010 12:49:07 -0800 (PST)
Received: from ZEUS.TR-Sys.de by w. with ESMTP ($Revision: 1.37.109.26 $/16.3.2) id AA242476977; Wed, 17 Nov 2010 21:49:37 +0100
Received: (from ah@localhost) by z.TR-Sys.de (8.9.3 (PHNE_25183)/8.7.3) id VAA14181; Wed, 17 Nov 2010 21:49:36 +0100 (MEZ)
From: Alfred Hönes <ah@TR-Sys.de>
Message-Id: <201011172049.VAA14181@TR-Sys.de>
To: uri-review@ietf.org
Date: Wed, 17 Nov 2010 21:49:36 +0100
X-Mailer: ELM [$Revision: 1.17.214.3 $]
Mime-Version: 1.0
Content-Type: text/plain; charset="hp-roman8"
Content-Transfer-Encoding: 7bit
Cc: apps-discuss@ietf.org
Subject: Re: [Uri-review] [Fwd: I-D Action:draft-melnikov-mailserver-uri-to-historic-00.txt]
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: Wed, 17 Nov 2010 20:49:10 -0000

My apologies for cross-posting, but this should perhaps reach a
broader audience.   I suggest to send feedback to the uri-review
at ietf.org mailing list, because Alexey sent his I-D announcement
there as well.


At Wed, 17 Nov 2010 17:26:32 +0000 , Alexey Melnikov wrote:

> FYI. I've asked on Apps-discuss about deprecating the mailserver:
> URIs and I've heard several voices in favor of doing that.
>
> I will be asking Peter Saint-Andre to sponsor this document.
>
> ...
>
>    Filename        : draft-melnikov-mailserver-uri-to-historic-00.txt
> ...


There are two more, apparently natively orphaned URI schemes listed
as 'provisional' in the IANA registry, both mentioned in RFC 1630
for the first time, and later again in RFC 1738, but never formally
registered and, AFAICS, still lacking any publicly available
specification:

   a)  tn3270

   b)  afs


A quick Google search does not reveal any hints on definitions and/or
actual use.  Some W3C web pages consider these as "reserved" names.

Apparently none of the various RFCs on Telnet extensions for TN3270
and the somehow related MIB module specifications mention the 'tn3270'
URI scheme.
Even stronger, for 'afs', archived mail (from 1993) seems to confirm
that 'afs' as a URI scheme was a very poor idea from its beginning
(see "afs: considered harmful",
<http://wwwwbs.cs.tu-berlin.de/html/urls/0148.html> ).

I suggest to consider deprecating these reserved URI scheme names
as well, in a single draft together with the 'mailserver' scheme
(to save work in the process).

Thereby, the registrations would be moved to "Historic", which,
according to the definition of that RFC status, does not immediately
invalidate existing use cases (if any), but serves to clarify that
new implementations should not try to support the subject.
The scheme names would remain in the registry, thus keeping the names
"reserved", i.e. out of availability for incompatible new use.

So there are a few questions, for both cases:

1)  Is anybody aware of a specification for the above provisional
    URI schemes ?

2)  If "yes" for 1), are there interoperable implementations?

3)  Are these URI schemes in actual use anywhere
    (even if only intended for interpretation by brainware) ?

4)  Do the answers to the above questions support deprecation?



Kind regards,
  Alfred.

-- 

+------------------------+--------------------------------------------+
| TR-Sys Alfred Hoenes   |  Alfred Hoenes   Dipl.-Math., Dipl.-Phys.  |
| Gerlinger Strasse 12   |  Phone: (+49)7156/9635-0, Fax: -18         |
| D-71254  Ditzingen     |  E-Mail:  ah@TR-Sys.de                     |
+------------------------+--------------------------------------------+