Moving DNSSEC Lookaside Validation (DLV) to Historic Status
draft-ietf-dnsop-obsolete-dlv-01

Document Type Active Internet-Draft (dnsop WG)
Last updated 2019-10-14 (latest revision 2019-10-09)
Replaces draft-mekking-dnsop-obsolete-dlv
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Tim Wicinski
Shepherd write-up Show (last changed 2019-09-03)
IESG IESG state In Last Call (ends 2019-10-25)
Consensus Boilerplate Yes
Telechat date
Responsible AD Warren Kumari
Send notices to Tim Wicinski <tjw.ietf@gmail.com>
IANA IANA review state IANA OK - Actions Needed
IANA expert review state Expert Reviews OK
IANA expert review comments I have reviewed the document and it is fine, after the RFC is published the line should read DLV 32769 DNSSEC Lookaside Validation (OBSOLETE) [RFCXYZZ] [RFC4431]
DNS Operations                                                W. Mekking
Internet-Draft                                                D. Mahoney
Updates: 6698, 6840 (if approved)                                    ISC
Intended status: Standards Track                         October 9, 2019
Expires: April 11, 2020

      Moving DNSSEC Lookaside Validation (DLV) to Historic Status
                    draft-ietf-dnsop-obsolete-dlv-01

Abstract

   This document obsoletes DNSSEC lookaside validation (DLV) and
   reclassifies RFCs 4431 and 5074 as Historic.  Furthermore, this
   document updates RFC 6698 by excluding the DLV resource record from
   certificates, and updates RFC 6840 by excluding the DLV registries
   from the trust anchor selection.

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/.

   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 11, 2020.

Copyright Notice

   Copyright (c) 2019 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
   2.  Discussion
   3.  Moving DLV to Historic Status
     3.1.  Documents that reference the DLV RFCs
       3.1.1.  Documents that reference RFC 4431
       3.1.2.  Documents that reference RFC 5074
   4.  IANA Considerations
   5.  Security considerations
   6.  Acknowledgements
   7.  Normative References
   Authors' Addresses

1.  Introduction

   DNSSEC Lookaside Validation (DLV) was introduced to assist with the
   adoption of DNSSEC [RFC4033] [RFC4034] [RFC4035] in a time where the
   root zone and many top level domains (TLDs) were unsigned, to help
   entities with signed zones under an unsigned parent zone, or that
   have registrars that don't accept DS records.  The root zone is
   signed since July 2010 and as of May 2019, 1389 out of 1531 TLDs have
   a secure delegation from the root; thus DLV has served its purpose
   and can now retire.

2.  Discussion

   One could argue that DLV is still useful because there are still some
   unsigned TLDs and entities under those zones will not benefit from
   signing their zone.  However, keeping the DLV mechanism also has
   disadvantages:

   o  It reduces the pressure to get the parent zone signed.

   o  It reduces the pressure on registrars to accept DS records.

   o  It complicates validation code.

   In addition, not every validator actually implements DLV (only BIND 9
   and Unbound) so even if an entity can use DLV to set up an alternate
   path to its trust anchor, its effect is limited.  Furthermore, there
   was one well-known DLV registry (dlv.isc.org) and that has been
   deprecated (replaced with a signed empty zone) on September 30, 2017.
   With the absence of a well-known DLV registry service it is unlikely
   that there is a real benefit for the protocol on the Internet
   nowadays.

   One other possible reason to keep DLV is to distribute trust anchors
   for private enterprises.  The authors are not aware of any such use
   of DLV.

   All things considered it is probably not worth the effort of
   maintaining the DLV mechanism.

3.  Moving DLV to Historic Status

   There are two RFCs that specify DLV:

   1.  RFC 4431 [RFC4431] specifies the DLV resource record.

   2.  RFC 5074 [RFC5074] specifies the DLV mechanism for publishing
       trust anchors outside the DNS delegation chain and how validators
       can use them to validate DNSSEC-signed data.

   This document moves both RFC 4431 [RFC4431] and RFC 5074 [RFC5074] to
   Historic status.  This is a clear signal to implementers that the DLV
   resource record and the DLV mechanism SHOULD NOT be implemented or
   deployed.

3.1.  Documents that reference the DLV RFCs

   The RFCs that are being moved to Historic status are referenced by a
   couple of other documents.  The sections below describe what changes
Show full document text