| Internet-Draft | Resinfo DNSSEC | October 2024 |
| Bortzmeyer | Expires 10 April 2025 | [Page] |
This document specifies a DNS Resolver Information Key (RFC 9606) for DNSSEC validation capability, "dnssecval".¶
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 10 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.¶
RFC 9606 specifies a DNS resource record (RR) type RESINFO to allow resolvers to publish information about their capabilities and policies. This information is encoded as {key, value} pairs, with each information is unambiguously identified with a key. Keys are maintained in an IANA registry. This specification adds a new key, to indicate that the resolver validates with DNSSEC [RFC4033][RFC4034][RFC4035].¶
Such key may be used, for example, by a DNS client to prefer resolvers that enable DNSSEC validation.¶
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.¶
The name of the key is "dnssecval", for "DNSSEC validating [resolver]". The presence of this key indicates that the DNS resolver validates all answers with DNSSEC [RFC4033] [RFC4034] [RFC4035]. Note that, per the rules for the keys defined in Section 6.4 of [RFC6763] if there is no '=' in a key, then it is a boolean attribute, simply identified as being present, with no value.¶
A resolver that announces this capability in a RESINFO record MAY add DNSSEC-specific EDE (Extended DNS Error Codes, [RFC8914]) to the value of the "exterr" key, e.g., "Unsupported DNSKEY Algorithm", "Unsupported DS Digest Type", and "DNSSEC Bogus". Refer to the "Extended DNS Error Codes" registry for a definitive list of these EDEs.¶
This document requests IANA to add the key "dnssecval", with the explanation text "The presence of the key name indicates that DNSSEC validation is enabled", and a reference to this document to the registry "DNS Resolver Information Keys" under the "Domain Name System (DNS) Parameters" registry group.¶
| Name | Description | Reference |
|---|---|---|
| dnssecval | The presence of the key name indicates that DNSSEC validation is enabled. | RFC EDITOR: replace : This_Document |
DNSSEC is a very important tool for the security of the DNS. Therefore it is important for users to know in advance whether the resolver they consider supports DNSSEC. It would be better to assume that every resolver validates (thus rendering this document useless) but it is not the case today.¶
As with any information published in the DNS, the keys in the RESINFO may be wrong or outdated. They should be regarded with care. The security considerations discussed in Section 7 of [RFC9606] apply.¶
Original idea by Marco Davids.¶