Signaling Trust Anchor Knowledge in DNS Security Extensions (DNSSEC)
draft-ietf-dnsop-edns-key-tag-05

Document Type Active Internet-Draft (dnsop WG)
Last updated 2017-03-17 (latest revision 2017-02-16)
Replaces draft-wessels-edns-key-tag
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Tim Wicinski
Shepherd write-up Show (last changed 2016-12-14)
IESG IESG state RFC Ed Queue
Consensus Boilerplate Yes
Telechat date
Responsible AD Joel Jaeggli
Send notices to "Tim Wicinski" <tjw.ietf@gmail.com>
IANA IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack
RFC Editor RFC Editor state RFC-EDITOR
Internet Engineering Task Force                               D. Wessels
Internet-Draft                                                  Verisign
Intended status: Standards Track                               W. Kumari
Expires: August 20, 2017                                          Google
                                                              P. Hoffman
                                                                   ICANN
                                                       February 16, 2017

  Signaling Trust Anchor Knowledge in DNS Security Extensions (DNSSEC)
                    draft-ietf-dnsop-edns-key-tag-05

Abstract

   The DNS Security Extensions (DNSSEC) were developed to provide origin
   authentication and integrity protection for DNS data by using digital
   signatures.  These digital signatures can be verified by building a
   chain-of-trust starting from a trust anchor and proceeding down to a
   particular node in the DNS.  This document specifies two different
   ways for validating resolvers to signal to a server which keys are
   referenced in their chain-of-trust.  The data from such signaling
   allow zone administrators to monitor the progress of rollovers in a
   DNSSEC-signed zone.

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 August 20, 2017.

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

Wessels, et al.          Expires August 20, 2017                [Page 1]
Internet-Draft          DNSSEC Key Tag Signaling           February 2017

   (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
     1.1.  Design Evolution  . . . . . . . . . . . . . . . . . . . .   3
   2.  Requirements Terminology  . . . . . . . . . . . . . . . . . .   4
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Using the edns-key-tag Option . . . . . . . . . . . . . . . .   5
     4.1.  Option Format . . . . . . . . . . . . . . . . . . . . . .   5
     4.2.  Use By Queriers . . . . . . . . . . . . . . . . . . . . .   5
       4.2.1.  Stub Resolvers  . . . . . . . . . . . . . . . . . . .   6
         4.2.1.1.  Validating Stub Resolvers . . . . . . . . . . . .   6
         4.2.1.2.  Non-validating Stub Resolvers . . . . . . . . . .   6
       4.2.2.  Recursive Resolvers . . . . . . . . . . . . . . . . .   6
         4.2.2.1.  Validating Recursive Resolvers  . . . . . . . . .   6
         4.2.2.2.  Non-validating Recursive Resolvers  . . . . . . .   7
     4.3.  Use By Responders . . . . . . . . . . . . . . . . . . . .   7
   5.  Using the Key Tag Query . . . . . . . . . . . . . . . . . . .   7
     5.1.  Query Format  . . . . . . . . . . . . . . . . . . . . . .   8
     5.2.  Use By Queriers . . . . . . . . . . . . . . . . . . . . .   8
     5.3.  Use By Responders . . . . . . . . . . . . . . . . . . . .   8
       5.3.1.  Interaction With Aggressive Negative Caching  . . . .   9
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   8.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .  10
   9.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  11
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  11
     10.2.  Informative References . . . . . . . . . . . . . . . . .  11
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  12

1.  Introduction
Show full document text