One document matched: draft-jabley-make-2870-historic-00.xml

<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>

<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
  <!ENTITY rfc1034 PUBLIC ''
    'http://xml.resource.org/public/rfc/bibxml/reference.RFC.1034.xml'>
  <!ENTITY rfc1035 PUBLIC ''
    'http://xml.resource.org/public/rfc/bibxml/reference.RFC.1035.xml'>
  <!ENTITY rfc2870 PUBLIC ''
    'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2870.xml'>
]>

<rfc category="std" ipr="trust200902"
  obsoletes="2870" category="bcp"
  docName="draft-jabley-make-2870-historic-00">

  <?rfc toc="yes" ?>
  <?rfc symrefs="yes" ?>
  <?rfc sortrefs="yes"?>
  <?rfc iprnotified="no" ?>
  <?rfc strict="yes" ?>

  <front>
    <title>Reclassification of RFC 2870 to Historic</title>

    <author initials="J." surname="Abley" fullname="Joe Abley" role="editor">
      <organization>ICANN</organization>
      <address>
        <postal>
          <street>12025 Waterfront Drive, Suite 300</street>
          <city>Los Angeles</city>
          <region>CA</region>
          <code>90094-2536</code>
          <country>USA</country>
        </postal>
        <phone>+1 519 670 9327</phone>
        <email>joe.abley@icann.org</email>
      </address>
    </author>

    <date day="3" month="August" year="2012"/>

    <abstract>
      <t>This document reclassifies RFC 2870, Root Name Server
	Operational Requirements, to Historic. This memo also
	obsoletes RFC 2870.</t>
    </abstract>
  </front>

  <middle>
    <section title="Introduction">
      <t>The Domain Name System (DNS) protocol (<xref target="RFC1034"/>,
        <xref target="RFC1035"/>) as implemented and deployed on the
	Internet includes thirteen so-called "Root Servers". These
	servers are authoritative-only DNS servers which answer
	authoritatively for the root zone of the DNS, often denoted
	by a single period ("."). The operators of such servers are
        known as Root Server Operators.</t>

      <t><xref target="RFC2870"/> was originally published to
        document operational requirements for Root Server Operators.</t>

      <t>This document reclassifies <xref target="RFC2870"/> to
	Historic. This memo also obsoletes <xref target="RFC2870"/>.</t>
    </section>

    <section title="Guidance for Root Server Operation">
      <t>Guidance to Root Server Operators, and information
        which might help set expectations of Root Server Operators
        by the rest of the technical community, can be found in
        <xref target="RSSAC001"/>. This document is a product of the
        ICANN Root Server System Advisory Committee (RSSAC).</t>
    </section>

    <section title="Reclassification of RFC 2870 to Historic">
      <t><xref target="RFC2870"/> presented a set of technical
	implementation and operational requirements for Root Servers.
	It included detailed requirements for service implementation
	that were useful for the time in which the document was
	published; however, that guidance has decreased in relevance
	as experience with large-scale authoritative DNS server
	deployment has increased.  Modern DNS infrastructure typically
	incorporates a variety of deployment techniques intended
	to facilitate very high query rates, and in the modern
	environment any Root Server built precisely to the specification
	presented in <xref target="RFC2870"/> would be grossly
	inadequate. Today, <xref target="RFC2870"/> provides value
	only as a part of the historical record of the ongoing
	development of the DNS.</t>

      <t>This document directs the RFC Editor to mark the document
        <xref target="RFC2870"/> as historic.</t>
    </section>

    <section title="Security Considerations">
      <t>This document presents no new security concerns for the
        Internet.</t>
    </section>

    <section title="IANA Considerations">
      <t>This document contains no actions for the IANA.</t>
    </section>
  </middle>

  <back>
    <references title="Normative References">
      &rfc2870;
    </references>

    <references title="Informative References">
      &rfc1034;
      &rfc1035;

      <reference anchor="RSSAC001">
        <front>
          <title>Service Expectations of Root Servers</title>
          <author>
            <organization abbrev="RSSAC">ICANN Root Server System
              Advisory Committee</organization>
          </author>
          <date year="2012" month="August"/>
        </front>
        <seriesInfo name="RSSAC" value="001"/>
      </reference>
    </references>

    <section title="Acknowledgements">
      <t>This document is a product of the ICANN Root Server System
        Advisory Committee (RSSAC), whose collective contributions
        are hereby acknowledged.</t>
    </section>
  </back>
</rfc>