Updating Resolver Algorithm
draft-fujiwara-dnsop-resolver-update-00

Document Type Active Internet-Draft (dnsop WG)
Last updated 2016-11-11 (latest revision 2016-10-31)
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state Candidate for WG Adoption
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                                        K. Fujiwara
Internet-Draft                                                      JPRS
Updates: 1034, 2181 (if approved)                      November 01, 2016
Intended status: Standards Track
Expires: May 5, 2017

                      Updating Resolver Algorithm
                draft-fujiwara-dnsop-resolver-update-00

Abstract

   Parent side NS RRSet and glue records are all information to access
   servers for child zone.  However, they may be overwritten by child
   zone data (zone apex NS RRSet and other A/AAAA RRSets).  The
   overwrite makes name resolution unstable and induces vulnerabilities.
   RFC 2181 section 5.4.1 specifies trustworthiness of DNS data.  And it
   is deemed that that all cached data (authoritative data, non-
   authoritative data, referrals and glue records) are merged into one.
   Resolvers may answer non-authoritative data, referrals and glue
   records that should not be returned.  This document proposes updating
   resolver algorithm that separates the cache to "authoritative data
   cache" and "delegation cache".  The former is used to answer stub
   resolvers, and the latter is used to iterate zones.

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 May 5, 2017.

Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Fujiwara                   Expires May 5, 2017                  [Page 1]
Internet-Draft           resolver-clarification            November 2016

   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
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Traditional resolver algorithm  . . . . . . . . . . . . . . .   3
     3.1.  Importance of parent side NS RRSet  . . . . . . . . . . .   3
     3.2.  Recommendation of resolver's answer . . . . . . . . . . .   4
     3.3.  Traditional resolver algorithm  . . . . . . . . . . . . .   5
   4.  Problem Statement . . . . . . . . . . . . . . . . . . . . . .   5
   5.  Updating of Resolver Algorithm  . . . . . . . . . . . . . . .   6
     5.1.  Recommendations to resolvers  . . . . . . . . . . . . . .   6
     5.2.  Update to resolver algorithm  . . . . . . . . . . . . . .   6
     5.3.  Characteristics of the update . . . . . . . . . . . . . .   7
     5.4.  Issues of the update  . . . . . . . . . . . . . . . . . .   8
   6.  Implementation Ideas  . . . . . . . . . . . . . . . . . . . .   8
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   9.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   8
   10. Change History  . . . . . . . . . . . . . . . . . . . . . . .   8
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     11.1.  Normative References . . . . . . . . . . . . . . . . . .   8
     11.2.  Informative References . . . . . . . . . . . . . . . . .   9
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   Resolver algorithm is defined in [RFC1034] and updated by [RFC2181].
   The resolver algorithm seems to assume single cache that holds all
   RRSets from received responses.  [RFC2181] Section 5.4.1 Ranking data
   specifies the trustworthiness order of RRSets.  When a resolver
   receives higher trustworthy data, the cached data is replaced by the
   received data.

   Parent side NS RRSet is very important because it creates new zone
Show full document text