Problem Statement and Requirements for an Improved DNS Delegation Mechanism abbrev: DNS DELEG Requirements
draft-wirelela-deleg-requirements-01
Document | Type |
Replaced Internet-Draft
(deleg WG)
Expired & archived
|
|
---|---|---|---|
Authors | David C Lawrence , Edward Lewis , Jim Reid , Tim Wicinski | ||
Last updated | 2024-08-30 (Latest revision 2024-08-14) | ||
Replaced by | draft-ietf-deleg-requirements | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources |
GitHub Repository
Mailing list discussion |
||
Stream | WG state | Adopted by a WG | |
Document shepherd | (None) | ||
IESG | IESG state | Replaced by draft-ietf-deleg-requirements | |
Consensus boilerplate | Unknown | ||
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
Authoritative control of parts of the Domain Name System namespace are indicated with a special record type, the NS record, that can only indicate the name of the server which a client resolver should contact for more information. Any other features of that server must then be discovered through other mechanisms. This draft considers the limitations of the current system, benefits that could be gained by changing it, and what requirements constrain an updated design.
Authors
David C Lawrence
Edward Lewis
Jim Reid
Tim Wicinski
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)