Connected: An Internet Encyclopedia
RFC 1630 - 4.2. Specific Schemes

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1630
Up: 4. Recommendations
Prev: 4.1.5. Fragment-id
Next: 4.2.1. HTTP

### 4.2. Specific Schemes

The mapping for URIs onto some existing standard and experimental protocols is outlined in the BNF syntax definition. Notes on particular protocols follow. These URIs are frequently referred to as URLs, though the exact definition of the term URL is still under discussion (March 1993). The schemes covered are:

http
  Hypertext Transfer Protocol (examples)

ftp
  File Transfer protocol

gopher
  Gopher protocol

mailto
  Electronic mail address

news
  Usenet news

telnet, rlogin and tn3270
  Reference to interactive sessions

wais
  Wide Area Information Servers

file
  Local file access

The following schemes are proposed as essential to the unification of the web with electronic mail, but not currently (to the author's knowledge) implemented:

mid
  Message identifiers for electronic mail

cid
  Content identifiers for MIME body part

The schemes for X.500, network management database, and Whois++ have not been specified and may be the subject of further study. Schemes for Prospero, and restricted NNTP use are not currently implemented as far as the author is aware.

The "urn" prefix is reserved for use in encoding a Uniform Resource Name when that has been developed by the IETF working group.

New schemes may be registered at a later time.

4.2.1. HTTP
4.2.2. FTP
4.2.3. Gopher
4.2.4. Mailto
4.2.5. News
4.2.6. Telnet, rlogin, tn3270
4.2.7. URN
4.2.8. WAIS
4.2.9. file
4.2.10. Message-Id
4.2.11. Content-Id
4.2.12. Schemes for Further Study
4.2.13. Prospero

Next: 4.2.1. HTTP

Connected: An Internet Encyclopedia
RFC 1630 - 4.2. Specific Schemes