| Internet-Draft | Extra DNSSEC EDE codes | February 2022 |
| Carpay & Toorop | Expires 29 August 2022 | [Page] |
While implementing Extended DNS Errors (RFC8914) in our DNSSEC validating resolver software Unbound, we encountered this specific situations regarding the DNSSEC bogus status where no Extended DNS Error were yet defined. This draft serves as a reference for code points requests.¶
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 29 August 2022.¶
Copyright (c) 2022 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.¶
While implementing Extended DNS Errors ([RFC8914]) in our DNSSEC validating resolver software Unbound ([UNBOUNDPR]), we encountered this specific situations regarding the DNSSEC bogus status where no Extended DNS Error were yet defined.¶
The resolver attempted to perform DNSSEC validation, but the signature is either smaller or larger than expected for the specified algorithm.¶
The resolver attempted to perform DNSSEC validation, but the Signer's Name Field in the signature contains a malformed signer (d)name.¶
The resolver attempted to perform DNSSEC validation, but the Signer's Name Field in the signature does not contain the zone name of the covered RRset.¶
The resolver attempted to perform DNSSEC validation, but the number of labels in the Signature Labels Field is incorrect.¶
The resolver attempted to perform DNSSEC validation, but the signed response does not have valid NSEC proof.¶
The resolver attempted to perform DNSSEC validation, but found a value not equal to 3 in the DNSKEY protocol number field as specified by RFC4034#section-2.1.2.¶
This draft requests the assignment of a new EDE code values for the specified EDE codes.¶
As this draft only seeks to add code points to the EDE registry, the security considerations as the same as in [RFC8914].¶