Addition of Extended DNS Errors codes
draft-bortzmeyer-more-edes-01

Internet Engineering Task Force                            S. Bortzmeyer
Internet-Draft                                                     Afnic
Intended status: Informational                           2 December 2024
Expires: 5 June 2025

                 Addition of Extended DNS Errors codes
                     draft-bortzmeyer-more-edes-01

Abstract

   This document is the specification of three new EDE (Extended DNS
   Errors) codes, for minimal answers, local roots and tailoring based
   on the client IP address.

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 5 June 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.

Bortzmeyer                 Expires 5 June 2025                  [Page 1]
Internet-Draft                  More EDEs                  December 2024

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   2
   2.  Tailoring . . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Minimal response  . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Local root  . . . . . . . . . . . . . . . . . . . . . . . . .   3
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   3
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   3
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   3
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   3
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   4
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .   4
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   4

1.  Introduction

   [RFC8914] created the EDE (Extended DNS Errors).  Each error is
   identified by a code, and there is an IANA registry of these codes.
   This specification adds three codes:

   *  One to say that the response has been tailored from the IP address
      of the end-client, for instance through ECS (EDNS Client Subnet),

   *  One to say that the response was deliberately minimal,

   *  One to say that the response comes from a local root.

1.1.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

2.  Tailoring

   This response code, TBD, means that the response has been tailored on
   the basis of the IP address of the client.  It can be from its actual
   IP address in the query (DNS-based load balancing), or because of ECS
   (EDNS Client Subnet, [RFC7871]).  It MAY be sent by authoritative
   servers or resolvers, for instance when they implement ECS.  Note
   that the fact that the server accepts ECS can also be seen in the
   EDNS part of the response, but it does not mean that ECS was actually
   used to tailor the answer.  Also, this response code is more general
   than just ECS.

Bortzmeyer                 Expires 5 June 2025                  [Page 2]
Internet-Draft                  More EDEs                  December 2024

   If a resolver receives this EDE from an authoritative server, it
   SHOULD copy it in the response sent to its client.

3.  Minimal response

   This response code, TBD, means that the response was deliberately
   minimal.  It can be because the request was using the QTYPE ANY, as
   documented by [RFC8482].  Or it can be also for cases like "glue
   records not sent since I wanted to save bits".  It MAY be sent by
   authoritative servers or resolvers.

4.  Local root

   This response code, TBD, means that the response comes from a local
   root, as documented in [RFC8806].  It MAY be sent by resolvers using
   a local root.

5.  IANA Considerations

   IANA is requested to allocate codes to these three EDE and to add
   them to the "Extended DNS Error Codes", with a reference to this
   document.

   Note that the policy for the registry "Extended DNS Error Codes" is
   just "First come, first served" so this document is not strictly
   necessary.

6.  Security Considerations

   The EDE are sent with EDNS and are not signed.  They should be used
   with care (see [RFC8914], section 6).

7.  References

7.1.  Normative References

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119,
              DOI 10.17487/RFC2119, March 1997,
              <https://www.rfc-editor.org/info/rfc2119>.

   [RFC7871]  Contavalli, C., van der Gaast, W., Lawrence, D., and W.
              Kumari, "Client Subnet in DNS Queries", RFC 7871,
              DOI 10.17487/RFC7871, May 2016,
              <https://www.rfc-editor.org/info/rfc7871>.

Bortzmeyer                 Expires 5 June 2025                  [Page 3]
Internet-Draft                  More EDEs                  December 2024

   [RFC8174]  Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
              2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
              May 2017, <https://www.rfc-editor.org/info/rfc8174>.

   [RFC8482]  Abley, J., Gudmundsson, O., Majkowski, M., and E. Hunt,
              "Providing Minimal-Sized Responses to DNS Queries That
              Have QTYPE=ANY", RFC 8482, DOI 10.17487/RFC8482, January
              2019, <https://www.rfc-editor.org/info/rfc8482>.

   [RFC8806]  Kumari, W. and P. Hoffman, "Running a Root Server Local to
              a Resolver", RFC 8806, DOI 10.17487/RFC8806, June 2020,
              <https://www.rfc-editor.org/info/rfc8806>.

   [RFC8914]  Kumari, W., Hunt, E., Arends, R., Hardaker, W., and D.
              Lawrence, "Extended DNS Errors", RFC 8914,
              DOI 10.17487/RFC8914, October 2020,
              <https://www.rfc-editor.org/info/rfc8914>.

7.2.  Informative References

Acknowledgements

   Original idea by Marco Davids.

Author's Address

   Stéphane Bortzmeyer
   Afnic
   7 avenue du 8 mai 1945
   78280 Guyancourt
   France
   Email: bortzmeyer+ietf@nic.fr
   URI:   https://www.afnic.fr/

Bortzmeyer                 Expires 5 June 2025                  [Page 4]