| Internet-Draft | Who does DELEG | October 2024 |
| Hoffman | Expires 17 April 2025 | [Page] |
This document describes the roles of resolvers and servers in the upcoming DELEG protocol. It might be useful to the DELEG WG in working on the protocol. This document will not become an RFC, but the words or ideas might be used in documents from the DELEG WG.¶
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 17 April 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.¶
This document describes the roles of resolvers and servers in the upcoming DELEG protocol. It might be useful to the DELEG WG in working on the protocol. This document will not become an RFC, but the words or ideas might be used in documents from the DELEG WG.¶
DNS resolvers will be the primary users of DELEG information. Other parties such as researchers and automated DNS loggers might also use DELEG information, but they do so in order to see how resolvers would act.¶
Three models have been described for who might publish DELEG information that resolvers will use. Those three are abbreviated as "direct", "indirect", and "mixed".¶
These three models are mutually exclusive. The DELEG WG must choose one of models when it chooses a protocol.¶
In this model, there are DELEG records in responses from the parent, but never in responses from the child. A DELEG-aware resolver uses the DELEG records from the parent and treats any DELEG records seen in responses from the child to be ignorable/reportable errors.¶
In this model, there are hint records in responses from the parent that point to the child. The child has DELEG records. A DELEG-aware resolver follows the hints from the parent to find the child, then uses the DELEG records from the child. A DELEG-aware resolver treats any non-hint DELEG records seen in responses from the parent to be ignorable/reportable errors.¶
In this model, the parent might contain DELEG records, hint records, or both; the child might also have DELEG records. A DELEG-aware resolver that sees hint records uses those hints to get DELEG records from the child. A DELEG-aware resolver mixes any DELEG records it has seen from the parent or the child according to the resolver's configuration.¶