ROOT ZONE PROTOCOL
draft-glassey-dns-rzp-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Todd S. Glassey | ||
| Last updated | 2002-06-12 | ||
| 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
The changing structure and size of today's Internet has taxed the existing name services and their architecture to the breaking point. The DNS system of today was unfortunately architected to have a single root zone and limited set of Top Level Domains. This is defined usually in the set of root servers any resolving request uses to lookup an address. This proposal then is an attempt to lessen the impact on end-users and registrars and to allow IP owners a greater freedom in representing namespace to their customers. The elevator description is that this I-D proposes the restructuring of domain names more fully along the lines of a telephone number by creating a ROOT ZONE PROTOCOL as an addition to multiply the existing DNS services times the number of ROOT ZONES.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)