W3C home > Mailing lists > Public > uri@w3.org > May 2005

RE: Status of ftp:///?

From: McDonald, Ira <imcdonald@sharplabs.com>
Date: Sat, 14 May 2005 15:28:34 -0700
Message-ID: <CFEE79A465B35C4385389BA5866BEDF00C7BBB@mailsrvnt02.enet.sharplabs.com>
To: uri@w3.org

Hi folks,

Umm...RFC 2396 is _obsolete_.

You might want to be looking at the successor RFC 3986 / STD 66, which 
does _not_ preserve all the ABNF elements that were in RFC 2396, so it
takes a bit of care to do comparisons.

Cheers,
- Ira

Ira McDonald (Musician / Software Architect)
Blue Roof Music / High North Inc
PO Box 221  Grand Marais, MI  49839
phone: +1-906-494-2434
email: imcdonald@sharplabs.com

> -----Original Message-----
> From: uri-request@w3.org [mailto:uri-request@w3.org]On Behalf Of Frank
> Ellermann
> Sent: Saturday, May 14, 2005 5:19 AM
> To: uri@w3.org
> Subject: Re: Status of ftp:///?
> 
> 
> 
> Graham Klyne wrote:
> 
> > implicitly, by omission of any contrary qualification,
> > permits ftp:///.
> 
> It's clear that you don't like my "let's see what happens"
> approach, but with two browsers I got ftp:/// => bad, not
> the same as ftp://localhost/
> 
> BTW, the same effect as for http:/// vs. http://localhost/
> 
> RfC 1738 says that file:/// is a special case, so I guess
> that ftp:/// and http:/// should be plain wrong.
> 
> RfC 2396 has server = [ [ userinnfo "@" ] hostport ] for
> one case of authority, but the text says "<userinfo>@" and
> ":port" might be omitted, not the "host".
> 
> In STD 66 that's:
> 
> |      authority   = [ userinfo "@" ] host [ ":" port ]
> |      host        = IP-literal / IPv4address / reg-name
> |      reg-name    = *( unreserved / pct-encoded / sub-delims )
> 
> | If the URI scheme defines a default for host, then that default
> | applies when the host subcomponent is undefined or when the
> | registered name is empty (zero length).  For example, the "file"
> | URI scheme is defined so that no authority, an empty host, and
> | "localhost" all mean the end-user's machine, whereas the "http"
> | scheme considers a missing authority or empty host invalid.
> 
> You found a bug in the ftp-uri-04 draft.
> 
> Adding  'As for the "http" scheme the <host> component of the
> <authority> cannot be empty'  could fix it.  Bye, Frank
> 
> 
> 
Received on Saturday, 14 May 2005 22:28:43 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 13 January 2011 12:15:35 GMT