Locating Services through the DNS
draft-bazyar-dns-locating-services-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Jawaid Bazyar | ||
| Last updated | 1996-01-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
Internet users continue to find new ways to apply existing Internet standards and technology. In particular, it has become common usage to use the DNS to locate services on a particular network, by use of names like gopher.tc.umn.edu or www.hypermall.com. This was a natural use of DNS. However, the continued commercialization of the Internet and the current trend towards service providers who maintain services and 'pseudo-domains' for numerous customers, and the difficulties of using multiple IP's requires that not only an IP address, but a port number as well, be available to client software looking for a particular service. This draft describes a simple way to support 'multi-home' servers through the DNS, with no changes to existing protocols, and only minimal additions to client software.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)