<?xml version="1.0" encoding="US-ASCII"?>
<!-- This is built from a template for a generic Internet Draft. Suggestions for
     improvement welcome - write to Brian Carpenter, brian.e.carpenter @ gmail.com 
     This can be converted using the Web service at http://xml.resource.org/ -->
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<!-- You want a table of contents -->
<!-- Use symbolic labels for references -->
<!-- This sorts the references -->
<!-- Change to "yes" if someone has disclosed IPR for the draft -->
<!-- This defines the specific filename and version number of your draft (and inserts the appropriate IETF boilerplate -->
<?rfc sortrefs="yes"?>
<?rfc toc="yes"?>
<?rfc symrefs="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<?rfc topblock="yes"?>
<?rfc comments="no"?>
<rfc category="info" docName="draft-yu-dnsops-disdm-00" ipr="trust200902">
  <front>
    <title abbrev="MDM">Multi Distribution master</title>


    <author fullname="Haisheng Yu" initials="H." surname="Yu">
      <organization>BIIGroup</organization>

      <address>
        <postal>
          <street/>

          <city>Beijing</city>

          <code/>

          <country>China</country>
        </postal>

        <email>hsyu@biigroup.cn</email>
      </address>
    </author>

   


    <!---->

    <date day="28" month="june" year="2021"/>

    <area>Networking</area>

    <workgroup>Domain Name System Operations</workgroup>

    <abstract>
       <t>DM (Distribution Master) is used to transfer zone file data between the registry and the authoritative server. The centralized DM system has the risk of a single point of failure. The distributed DM architecture allows nodes to join and exit at any time to solve the single point of failure problem.</t>
    </abstract>

    <note title="Requirements Language">
      <t>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 <xref
      target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they appear in all capitals, as shown here. </t>
    </note>
  </front>

  <middle>
    <section title="Introduction">
<t> </t>

<t>  </t>


    </section>


<section title="Distributed DM System Design Overview"></section>

<section title="Research Status"></section>

<section title="Design of Data Acquisition Subsystem"></section>

<section anchor="Security" title="Security Considerations"></section>

<section anchor="IANA" title="IANA Considerations"><t>This document does not include an IANA request.</t></section>

<section title="Acknowledgements">
 <t>The authors would like to acknowledge XXX for their valuable review and comments.</t>
</section>

 </middle>


   <back>

<references title="Normative References">
<?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml"?>
<?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.8174.xml"?>
</references>
<references title="Informative References">
	<?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.1035.xml"?>
</references>

  </back>
</rfc>
