<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.1 (Ruby 3.2.2) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-devforma-dn-protocol-00" category="info" submissionType="independent" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.18.1 -->
  <front>
    <title abbrev="TODO - Abbreviation">draft of dn protocol version 00</title>
    <seriesInfo name="Internet-Draft" value="draft-devforma-dn-protocol-00"/>
    <author fullname="MaBingtao">
      <organization>Yunqi Academy</organization>
      <address>
        <email>devforma@hotmail.com</email>
      </address>
    </author>
    <date year="2023" month="October" day="11"/>
    <keyword>dn</keyword>
    <abstract>
      <?line 35?>

<t>TODO Abstract</t>
    </abstract>
    <note removeInRFC="true">
      <name>About This Document</name>
      <t>
        The latest revision of this draft can be found at <eref target="https://devforma.github.io/internet-draft-template/draft-dn-protocol.html"/>.
        Status information for this document may be found at <eref target="https://datatracker.ietf.org/doc/draft-devforma-dn-protocol/"/>.
      </t>
      <t>Source for this draft and an issue tracker can be found at
        <eref target="https://github.com/devforma/internet-draft-template"/>.</t>
    </note>
  </front>
  <middle>
    <?line 40?>

<section anchor="introduction">
      <name>Introduction</name>
      <t>TODO Introduction</t>
    </section>
    <section anchor="conventions-and-definitions">
      <name>Conventions and Definitions</name>
      <t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as
described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they
appear in all capitals, as shown here.</t>
      <?line -18?>

</section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <t>TODO Security</t>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <t>This document has no IANA actions.</t>
    </section>
  </middle>
  <back>
    <references anchor="sec-normative-references">
      <name>Normative References</name>
      <reference anchor="RFC2119">
        <front>
          <title>Key words for use in RFCs to Indicate Requirement Levels</title>
          <author fullname="S. Bradner" initials="S." surname="Bradner"/>
          <date month="March" year="1997"/>
          <abstract>
            <t>In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
          </abstract>
        </front>
        <seriesInfo name="BCP" value="14"/>
        <seriesInfo name="RFC" value="2119"/>
        <seriesInfo name="DOI" value="10.17487/RFC2119"/>
      </reference>
      <reference anchor="RFC8174">
        <front>
          <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
          <author fullname="B. Leiba" initials="B." surname="Leiba"/>
          <date month="May" year="2017"/>
          <abstract>
            <t>RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.</t>
          </abstract>
        </front>
        <seriesInfo name="BCP" value="14"/>
        <seriesInfo name="RFC" value="8174"/>
        <seriesInfo name="DOI" value="10.17487/RFC8174"/>
      </reference>
    </references>
    <?line 80?>

<section numbered="false" anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>TODO acknowledge.</t>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA3VU207bQBB936+YmreqzqVCKrUoYAiXSIHQAEKo6sPaO4lX
2Lvu7jo0RfxLv6Vf1lnbCbjQl3jPmTMzO5dNGIbMSZdjBIEwfO5Az0EoKI12
OtU5LNFYqRUMBgHjSWJwScrr6WgKIcQ1ltyRIGApd7jQZhWBVHPNmNCp4gUF
ruOGApdzbQoeChWuo4eDAbNVUkjrc7hVid5ZYIn0oxzAFvDcasr4gg0+QIBC
Om0kzz0Yx4f00YZOs+uTgKmqSNBETNCFIpZqZVHZykaMrj5gFNIgjyCeHccE
HrS5XxhdlRHcnsItIakWcOoZdo8rMouIUa1CsSWqigJuAWwcPGiu3fUkuuAy
95ID/MmLMsdeqgvPc5NmEWTOlTbq918Y+xSOQkuXVYmfRtuvvlQOjULqYN1H
h+RAlQUk9l/rSLwOt3bqNWF6Uv/Pvd9O5XkYvcwVecAYr1ymjS+aMgDMqzxv
5hic80Mq0XEd1BZtFlzJX/X4yXpXqR8S4pQLLFaNApsmbGo5yLTzlC+XMinP
ObmkpjK/M8+IhWEIPLHO8NQxVu9bvIG1tZBC5MiopWPljBZV6u/RarsUaY60
ovF5aIErASOcSyVrTC4ZAs3a74KwVObN1bXfK/+Fi2l9nh1/vRnPjkf+fHUW
TyabA2sVV2fTm8no+fTseTQ9Pz++GDXOxEKHYsF5fEcWf6tgenk9nl7Ek4Ce
AbhMWqBXVBX+LdDWgtOQINQTLQ06FMAtE2hTIxMC5HN4dPnn93AbHh/fzU6O
Pg6Hn5+eWrAz/LRN4CFD1WTTKl+10GW4YrwskRsfhec5pLyUjl4faS3YTD8o
yNBgj7H333xnvkewm6TlcHuvJXzBHXLdsw5Z9+w188q5aeIb1BtpNt3s8P90
unvf+K6D131/Qe7u51IhhMOd/T1W79AVppWRbuWXyUqBhq/3x6/c2lpLx/FF
/FrWmWdGbVW6UfJ6UW2vXe2Ep/c+SpzeK/2Qo1h4D8seo+avDcWXYE6jweCp
Tc43ShrQX85kRAbUBQAA

-->

</rfc>
