Resolvers and Servers for DELEG
draft-hoffman-deleg-roles-00

Network Working Group                                         P. Hoffman
Internet-Draft                                                     ICANN
Intended status: Informational                           14 October 2024
Expires: 17 April 2025

                    Resolvers and Servers for DELEG
                      draft-hoffman-deleg-roles-00

Abstract

   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.

Status of This Memo

   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 Notice

   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.

Hoffman                   Expires 17 April 2025                 [Page 1]
Internet-Draft               Who does DELEG                 October 2024

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Targets for DELEG Information . . . . . . . . . . . . . . . .   2
   3.  Who Will Publish DELEG Information  . . . . . . . . . . . . .   2
     3.1.  Direct: Parent delegates  . . . . . . . . . . . . . . . .   2
     3.2.  Indirect: Parent hints to child's delegation  . . . . . .   3
     3.3.  Mixed: Delegation information is found at both the parent
           and child . . . . . . . . . . . . . . . . . . . . . . . .   3
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   3

1.  Introduction

   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.

2.  Targets for DELEG Information

   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.

3.  Who Will Publish DELEG Information

   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.

3.1.  Direct: Parent delegates

   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.

Hoffman                   Expires 17 April 2025                 [Page 2]
Internet-Draft               Who does DELEG                 October 2024

3.2.  Indirect: Parent hints to child's delegation

   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.

3.3.  Mixed: Delegation information is found at both the parent and
      child

   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.

Author's Address

   Paul Hoffman
   ICANN
   Email: paul.hoffman@icann.org

Hoffman                   Expires 17 April 2025                 [Page 3]