DNS Authoritative server Management Based on Blockchain
draft-song-dnsop-dns-blockchain-00

Document Type Active Internet-Draft (individual)
Authors Yang Song  , louie long 
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                                                            Y. Song
Internet-Draft                                                   Y. Long
Intended status: Informational                           CFIEC-Guangzhou
Expires: November 23, 2020                                  May 22, 2020

        DNS Authoritative server Management Based on Blockchain
                   draft-song-dnsop-dns-blockchain-00

Abstract

   This document specifies a mechanism for managing authoritative server
   such as root server,thereby implement decentralized management of the
   authoritative server.Through distributed decision and distributed
   storage,encrypted inforamtion and records are stored adding the block
   to the blockchain.And the distributed authoritative servers share
   common blockchain which has detailed retrieval data for answering
   queries from the resolvers.

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

Song & Long             Expires November 23, 2020               [Page 1]
Internet-Draft           Blockchain Oriented DNS                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 . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Authoritative server  . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Root server . . . . . . . . . . . . . . . . . . . . . . .   3
     2.2.  Top-Level Domain Server . . . . . . . . . . . . . . . . .   3
     2.3.  Others  . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Deployment of authoritative server  . . . . . . . . . . . . .   3
   4.  Distributed Management  . . . . . . . . . . . . . . . . . . .   4
     4.1.  Country Code Top-level Domains  . . . . . . . . . . . . .   5
     4.2.  Generic Top-level Domains . . . . . . . . . . . . . . . .   5
   5.  Features  . . . . . . . . . . . . . . . . . . . . . . . . . .   5
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   The Domain Name System(DNS) is a simple query-response protocol,At
   present,DNS adopts centralized resolution system,that authoritative
   server is deployed by the independent entity and any modification
   requires the approval of the independent entity also.But there exists
   many risks for above-mentioned architecture,such as risk of
   disappearance, risk of blindness, risk of
   isolation,etc..Therefore,decentralized architecture for DNS is
   developing as a alternative option.

   This document describes a new architecture for DNS,multiple
   authoritative servers in the same layer(e.g. root servers)as server
   nodes make up a node group.All server nodes in the same node group
   are peers,by which corresponding operations are governed together.And
   information and records stored in the server nodes can only be
   changed by reaching a consensus within the node group.Update from any
   server node can be automatically distributed to the other server
   nodes which provide redundant service for the data.Hence,there is no
   affect even though some server nodes are corrupted.

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].
Show full document text