URI Localization Using NAPTR RR
draft-singh-uri-localization-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Jasdip Singh | ||
| Last updated | 2001-10-23 | ||
| 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
This memo specifies the structure of a Naming Authority Pointer (NAPTR) DNS Resource Record (RR) for localizing a Uniform Resource Identifier (URI) in more popular protocols like HTTP, SMTP, and FTP. URI localization means transforming by locale (geography and language) a URI into another URI that identifies a local resource. This URI transformation, where feasible, can help distribute content more efficiently and appropriately.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)