An Architecture for Open Human Friendly Naming of Internet Resource Addresses ('URLs')
draft-moseley-ohfn-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Shep Bostin | ||
| Last updated | 1999-02-22 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
As use of the Internet has become widespread, it's become increasingly clear that the URL -- the mechanism most users employ to designate resources -- is inherently confusing to non-technical users, and to a great extent, is unusable by them. For that reason, an easier naming scheme that employs human-friendly names ('HFNs') is desirable and necessary. Such schemes have been discussed at length in RFCs 1737[1], 2276[2] and 2168[3]. As use of the Internet has become widespread, it's become increasingly clear that the URL -- the mechanism most users employ to designate resources -- is inherently confusing to non-technical users, and to a great extent, is unusable by them. For that reason, an easier naming scheme that employs human-friendly names ('HFNs') is desirable and necessary. Such schemes have been discussed at length in RFCs 1737[1], 2276[2] and 2168[3].
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)