| Internet-Draft | DNS DELEG Requirements | July 2024 |
| Lawrence, et al. | Expires 9 January 2025 | [Page] |
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.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 9 January 2025.¶
Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
In the Domain Name System [STD13], subtrees within the domain name hierarchy are indicated by delegations to servers which are authoritative for their portion of the namespace. The DNS records that do this, called NS records, can only represent the name of a nameserver. In practice, clients can expect nothing out of this delegated server other than that it will answer DNS requests on UDP port 53.¶
As the DNS has evolved over the past four decades, this has proven to be a barrier for the efficient introduction of new DNS technology, particularly for interacting with servers other than via UDP or TCP on port 53. Many features that have been conceived come with additional overhead as they are limited by this least common denominator of nameserver functionality.¶
Various mechanisms have been proposed for communicating additional information about authoritative nameservers. This document investigates problems that could be addressed with a new delegation mechanism and the factors that need to be considered in the design of a solution.¶
This document assumes familiarity with DNS terms as defined in [BCP219]. Additionally, the following new terms are introduced:¶
A new method of DNS delegation, matching the requirements in this document but not presuming any particular mechanism, including previous specific proposals that used this name¶
The person or organization responsible for the nameserver which serves the zone¶
The network address tuple at which a zone is served¶
The requirements constraining any proposed changes to DNS delegations fall broadly into two categories.¶
"Hard requirements" are those that must be followed by a successful protocol [RFC5218], because violating them would present too much of an obstacle for broad adoption. These will primarily be related to the way the existing Domain Name System functions at all levels.¶
"Soft requirements" are those that are desirable, but the absence of which does not intrinsically eliminate a design. These will largely be descriptive of the problems that are trying to be addressed with a new method, or features that would ease adoption.¶
The context used here will be for the Domain Name System as it exists under the ICANN root and the Registry/Registrar/Registrant model (reference), and some conditions will only be relevant there. While it is expected that any design which satisfies the requirements of put forth here would be broadly applicable for any uses of the DNS outside of this environment, such uses are not in scope.¶
The following strictures are necessary in a new delegation design.¶
DELEG must not disrupt the existing registration model of domains. Reservation of a name at a registry will still use the relevant registrar system to indicate the authorized registrant.¶
DELEG must not change current namespace semantics. The nameserver (NS) record type will continue to define the delegation of authority between a parent zone and a child zone exactly as it has for decades.¶
DELEG must not negatively impact most DNS software. This is intentionally a bit vague with regard to "most", because it can't be absolutely guaranteed for all possible DNS software on the network. However, the working group should strive to test any proposed mechanism against a wide range of legacy software and come to a consensus as to what constitutes adherence to this requirement.¶
DELEG must be able to secure delegations with DNSSEC. Ideally it should be able to convey an even stronger security model for delegations than currently exists.¶
DELEG must support updates to delegation information with the same relative ease as currently exists with NS records. Changes should take the same amount of time (eg, controlled by a DNS TTL) and allow a smooth transition between different operational platforms.¶
The following items are the aspirational goals for this work, describing the features that are desired beyond what current NS-based delegations provide.¶
DELEG should facilitate the use of new DNS transport mechanisms, including those already defined by DNS-over-TLS (DoT [RFC7858]), DNS-over-HTTPS (DoH [RFC8484]), and DNS-over-Quic (DoQ [RFC9520]). It should easily allow the adoption of new transport mechanisms.¶
DELEG should make clear all of the necessary details for contacting a Service Access Point -- its protocol, port, and any other data that would be required to initiate a DNS query.¶
DELEG should minimize transaction cost in its usage. This includes, but is not limited to, packet count, packet volume, and the amount of time it takes to resolve a query.¶
DELEG should enable a DNS operator to manage DNS service more completely on behalf of registrants. For example, DELEG could address long-standing issues of DNSSEC record maintenance that now often depend on registrant/registrar interaction. Similarly, DELEG could allow new transports to be deployed by an operator without necessitating that delegation information be modified by the registrant.¶
DELEG should allow for backward compatibility to the conventional NS-based delegation mechanism. That is, a Zone Operator who wants to maintain a single source of truth of delegation information using DELEG should be able to easily have Do53 delegations derived from it.¶
DELEG should be easily extensible, much like the Extension Mechanisms for DNS [RFC6891]. allowing for the incremental addition of new parameters without needing all of the heavy lifting that is expected for the initial deployment.¶
DELEG should support an in-band means for the child to signal to the parent that parent-side records related to the child should be updated, akin to CDS/CDNSKEY [RFC8078].¶
This memo includes no request to IANA.¶
Updating the means by which DNS delegation information is communicated has tremendous implications for the security of the Internet. This section will be made more robust in future drafts. Contributions welcome.¶