Extended DNS Errors
draft-ietf-dnsop-extended-error-00

Document Type Active Internet-Draft (dnsop WG)
Last updated 2017-10-18 (latest revision 2017-10-16)
Replaces draft-wkumari-dnsop-extended-error
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                          W. Kumari
Internet-Draft                                                    Google
Intended status: Standards Track                                 E. Hunt
Expires: April 19, 2018                                              ISC
                                                               R. Arends
                                                                 Nominet
                                                             W. Hardaker
                                                                 USC/ISI
                                                             D. Lawrence
                                                     Akamai Technologies
                                                        October 16, 2017

                          Extended DNS Errors
                   draft-ietf-dnsop-extended-error-00

Abstract

   This document defines an extensible method to return additional
   information about the cause of DNS errors.  The primary use case is
   to extend SERVFAIL to provide additional information about the cause
   of DNS and DNSSEC failures.

   [ Open question: The document currently defines a registry for
   errors.  It has also been suggested that the option also carry human
   readable (text) messages, to allow the server admin to provide
   additional debugging information (e.g: "example.com pointed their NS
   at us.  No idea why...", "We don't provide recursive DNS to
   192.0.2.0.  Please stop asking...", "Have you tried Acme Anvil and
   DNS?  We do DNS right..." (!).  Please let us know if you think text
   is needed, or if a 16bit FCFS registry is expressive enough. ]

   [ Open question: This document discusses extended *errors*, but it
   has been suggested that this could be used to also annotate *non-
   error* messages.  The authors do not think that this is a good idea,
   but could be persuaded otherwise. ]

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 http://datatracker.ietf.org/drafts/current/.

Kumari, et al.           Expires April 19, 2018                 [Page 1]
Internet-Draft       draft-ietf-dnsop-extended-error        October 2017

   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 April 19, 2018.

Copyright Notice

   Copyright (c) 2017 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
   (http://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 Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction and background . . . . . . . . . . . . . . . . .   3
     1.1.  Requirements notation . . . . . . . . . . . . . . . . . .   3
   2.  Extended Error EDNS0 option format  . . . . . . . . . . . . .   3
   3.  Use of the Extended DNS Error option  . . . . . . . . . . . .   4
   4.  Defined Extended DNS Errors . . . . . . . . . . . . . . . . .   5
     4.1.  Extended DNS Error Code 100 - DNSSEC Bogus  . . . . . . .   5
     4.2.  Extended DNS Error Code 2 - DNSSEC Indeterminate  . . . .   5
     4.3.  Extended DNS Error Code 3 - Lame  . . . . . . . . . . . .   5
     4.4.  Extended DNS Error Code 4 - Prohibited  . . . . . . . . .   5
     4.5.  Extended DNS Error Code 5 - TooBusy . . . . . . . . . . .   6
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   6.  Open questions  . . . . . . . . . . . . . . . . . . . . . . .   7
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Appendix A.  Changes / Author Notes.  . . . . . . . . . . . . . .   8
Show full document text