| Internet-Draft | More EDEs | September 2024 |
| Bortzmeyer | Expires 22 March 2025 | [Page] |
- Workgroup:
- Internet Engineering Task Force
- Internet-Draft:
- draft-bortzmeyer-more-edes-00
- Published:
- Intended Status:
- Informational
- Expires:
Addition of Extended DNS Errors codes
Abstract
This document is the specification of three new EDE (Extended DNS Errors) codes, for minimal answers, local roots and ECS (EDNS Client Subnet).¶
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 22 March 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.¶
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 because of ECS,¶
- 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. ECS
This response code, TBD, means that the response has been tailored because of ECS (EDNS CLient Subnet, [RFC7871]). It MAY be sent by authoritative servers or resolvers when they implement ECS.¶
TODO if a resolver receives this EDE from an authoritative, should it copy it in the response sent to its client?¶
TODO Could it also include tailoring for other reasons (like DNS load balancing)?¶
3. Minimal response
This response code, TBD, means that the response to an ANY request was deliberately minimal, as documented by [RFC8482]. It MAY be sent by authoritative servers or resolvers.¶
TODO should we extend it also for cases like "glue not sent since I wanted to save bits"?¶
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, , <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, , <https://www.rfc-editor.org/info/rfc7871>.
- [RFC8174]
- Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, , <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, , <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, , <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, , <https://www.rfc-editor.org/info/rfc8914>.
7.2. Informative References
Acknowledgements
Original idea by Marco Davids.¶