W3C home > Mailing lists > Public > uri@w3.org > January 2010

Status of RFC 1738

From: Charles Lindsey <chl@clerew.man.ac.uk>
Date: Thu, 07 Jan 2010 10:46:28 -0000
To: uri@w3.org
Cc: "Paul Hoffman" <phoffman@imc.org>
Message-ID: <op.u55r7q156hl8nm@clerew.man.ac.uk>
The question has arisen of whether, with the publication of the nntp/news  
schemes, RFC 1738 can finally be delcared obsolete.

Looking at the list of schemes defined therein, it appears that most of  
them have been dealt with by new RFCs, or have been declared historic.  
According to IANA, there would still remain just two schemes not yet  
disposed of, namely 'file' and 'ftp'.

It has been suggested that 'file' is so ambiguous, with no consensus on  
how the clean it up, that it may as well be abandoned. OTOH, most browsers  
support it, at least for accessing resources on the localhost, and I  
personally find it quite useful.

It seems that 'ftp' really needs a new RFC, even if it merely copies the  
text out of 1738.

What are the views of this list as to whether these schemes should now be  
properly codified (and volunteers to do it)? And should the final  
obsoleting of 1738 be held back until that has been done?

When it is finally ready to go, declaring it as 'historic' might well be  
in order.

Charles H. Lindsey ---------At Home, doing my own thing------------------------
Tel: +44 161 436 6131                       
   Web: http://www.cs.man.ac.uk/~chl
Email: chl@clerew.man.ac.uk      Snail: 5 Clerewood Ave, CHEADLE, SK8 3JU, U.K.
PGP: 2C15F1A9      Fingerprint: 73 6D C2 51 93 A0 01 E7 65 E8 64 7E 14 A4 AB A5
Received on Thursday, 7 January 2010 10:47:13 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:25:13 UTC