Optimal Retrieval Process for DNS Based on EDNS
draft-gong-dnsop-optimal-retrieval-edns-00

Document Type Active Internet-Draft (individual)
Last updated 2020-05-21
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
dnsop                                                            D. Gong
Internet-Draft                                                  P. Zhang
Intended status: Informational                           CFIEC-Guangzhou
Expires: November 23, 2020                                  May 22, 2020

            Optimal Retrieval Process for DNS Based on EDNS
               draft-gong-dnsop-optimal-retrieval-edns-00

Abstract

   This document specifies a mechanism for query-response protocol to
   improve DNS retrieval efficiency,which makes the resolver always look
   for the best authoritative servers to ask for the required data.Based
   on the extension mechanisms for DNS,optimal-result using OPT pseudo-
   RR can be added to the addtional data section of either a request or
   a response,which contains the information of optimal authoritative
   servers by testing.

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 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 November 23, 2020.

Copyright Notice

   Copyright (c) 2020 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 Simplified BSD License text as described in Section 4.e of

Gong & Zhang            Expires November 23, 2020               [Page 1]
Internet-Draft          Optimal Retrieval Process               May 2020

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Notation . . . . . . . . . . . . . . . . . .   2
     1.2.  Applicability . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Optimal root servers  . . . . . . . . . . . . . . . . . . . .   3
   3.  Service Quality Testing . . . . . . . . . . . . . . . . . . .   3
   4.  Optimal-result Format . . . . . . . . . . . . . . . . . . . .   4
   5.  Transport Considerations  . . . . . . . . . . . . . . . . . .   5
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   At present,the resolver undertaking the actual resolution either
   responds to queries from the local cache or sends queries to the
   authoritative server in order to get corresponding answers to the
   original queries.But how to find the best authoritative servers to
   ask without cached date is very important,that it determines the
   performance of resolution.In particular,service quality of IPv6
   servers is unstable during the transition from IPv4 to IPv6.

   As a result,this document is meant to optimize the retrieval process
   between the resolver and the authoritative servers.The authoritative
   servers with the best service quality are determined by periodically
   testing the connectivity of specific authoritative servers,that there
   are also corresponding priority orders.Hence,the resolver can receive
   the priority information embedded in the message to pursue
   queries.And the Optimal-result format with priority information is
   designed,which is a new format compatible with existing DNS message
   format.

1.1.  Requirements Notation

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
   NOT","SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
   this document are to be interpreted as described in [RFC8174].

1.2.  Applicability

   This document is applicable to the recursive resolver that pursues
   queries and the authoritative server that supports the detection of
   next-level authoritative servers.

Gong & Zhang            Expires November 23, 2020               [Page 2]
Internet-Draft          Optimal Retrieval Process               May 2020

2.  Optimal root servers

   Optimal root servers are often determined by the resolver,that the
Show full document text