Domain Names, A Case for Clarifying
draft-lewis-domain-names-10
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Author | Edward Lewis | ||
| Last updated | 2018-07-30 (Latest revision 2018-01-26) | ||
| RFC stream | Independent Submission | ||
| Formats | |||
| IETF conflict review | conflict-review-lewis-domain-names, conflict-review-lewis-domain-names, conflict-review-lewis-domain-names, conflict-review-lewis-domain-names, conflict-review-lewis-domain-names | ||
| Stream | ISE state | In ISE Review | |
| Consensus boilerplate | Unknown | ||
| Document shepherd | (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
Is the concept of Domain Names owned by the DNS protocol or does the DNS protocol exist to support the Domain Names concept? This question has become pertinent in light of proposals to use Domain Names in protocols in ways incompatible with the DNS protocol and the operational environment built to runthe protocol. This document looks first at the early record in the RFC series and then expands to survey how Domain Names are used in protocols and reaches the conclusion that Domain Names are independent of the DNS, and further, that there might be a need to clarify the definition of Domain Names to reinforce that notion.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)