<?xml version='1.0' encoding='utf-8'?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" version="3" category="info" consensus="true" docName="draft-iab-arpa-authoritative-servers-01" indexInclude="true" ipr="trust200902" number="9120" prepTime="2021-10-29T11:28:07" scripts="Common,Latin" sortRefs="true" submissionType="IAB" symRefs="true" tocDepth="4" tocInclude="true" updates="3172" xml:lang="en">
  <link href="https://datatracker.ietf.org/doc/draft-iab-arpa-authoritative-servers-01" rel="prev"/>
  <link href="https://dx.doi.org/10.17487/rfc9120" rel="alternate"/>
  <link href="urn:issn:2070-1721" rel="alternate"/>
  <front>
    <title abbrev="Nameservers for the .arpa Domain">Nameservers for the Address and Routing Parameter Area ("arpa") Domain</title>
    <seriesInfo name="RFC" value="9120" stream="IAB"/>
    <author initials="K." surname="Davies" fullname="Kim Davies">
      <organization showOnFrontPage="false">Internet Assigned Numbers Authority</organization>
      <address>
        <postal>
          <street>PTI/ICANN</street>
          <street>12025 Waterfront Drive</street>
          <city>Los Angeles</city>
          <region>CA</region>
          <code>90094</code>
          <country>United States of America</country>
        </postal>
        <email>kim.davies@iana.org</email>
      </address>
    </author>
    <author initials="J." surname="Arkko" fullname="Jari Arkko">
      <organization showOnFrontPage="false">Ericsson Research</organization>
      <address>
        <postal>
          <street>02700 Kauniainen</street>
          <country>Finland</country>
        </postal>
        <email>jari.arkko@ericsson.com</email>
      </address>
    </author>
    <date month="10" year="2021"/>
    <keyword>root zone</keyword>
    <keyword>IANA</keyword>
    <keyword>top-level domain</keyword>
    <keyword>root nameservers</keyword>
    <keyword>DNS</keyword>
    <keyword>ARPA</keyword>
    <abstract pn="section-abstract">
      <t indent="0" pn="section-abstract-1">This document describes revisions to operational practices to separate the function of the "arpa" top-level domain in the DNS from its historical
operation alongside the DNS root zone.</t>
    </abstract>
    <boilerplate>
      <section anchor="status-of-memo" numbered="false" removeInRFC="false" toc="exclude" pn="section-boilerplate.1">
        <name slugifiedName="name-status-of-this-memo">Status of This Memo</name>
        <t indent="0" pn="section-boilerplate.1-1">
            This document is not an Internet Standards Track specification; it is
            published for informational purposes.  
        </t>
        <t indent="0" pn="section-boilerplate.1-2">
            This document is a product of the Internet Architecture Board
            (IAB) and represents information that the IAB has deemed valuable
            to provide for permanent record.  It represents the consensus of the Internet
            Architecture Board (IAB).  Documents approved for publication
            by the IAB are not candidates for any level of Internet Standard; see
            Section 2 of RFC 7841.
        </t>
        <t indent="0" pn="section-boilerplate.1-3">
            Information about the current status of this document, any
            errata, and how to provide feedback on it may be obtained at
            <eref target="https://www.rfc-editor.org/info/rfc9120" brackets="none"/>.
        </t>
      </section>
      <section anchor="copyright" numbered="false" removeInRFC="false" toc="exclude" pn="section-boilerplate.2">
        <name slugifiedName="name-copyright-notice">Copyright Notice</name>
        <t indent="0" pn="section-boilerplate.2-1">
            Copyright (c) 2021 IETF Trust and the persons identified as the
            document authors. All rights reserved.
        </t>
        <t indent="0" pn="section-boilerplate.2-2">
            This document is subject to BCP 78 and the IETF Trust's Legal
            Provisions Relating to IETF Documents
            (<eref target="https://trustee.ietf.org/license-info" brackets="none"/>) 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.
        </t>
      </section>
    </boilerplate>
    <toc>
      <section anchor="toc" numbered="false" removeInRFC="false" toc="exclude" pn="section-toc.1">
        <name slugifiedName="name-table-of-contents">Table of Contents</name>
        <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1">
          <li pn="section-toc.1-1.1">
            <t indent="0" keepWithNext="true" pn="section-toc.1-1.1.1"><xref derivedContent="1" format="counter" sectionFormat="of" target="section-1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-introduction">Introduction</xref></t>
          </li>
          <li pn="section-toc.1-1.2">
            <t indent="0" keepWithNext="true" pn="section-toc.1-1.2.1"><xref derivedContent="2" format="counter" sectionFormat="of" target="section-2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-requirements-for-the-arpa-z">Requirements for the "arpa" Zone</xref></t>
          </li>
          <li pn="section-toc.1-1.3">
            <t indent="0" pn="section-toc.1-1.3.1"><xref derivedContent="3" format="counter" sectionFormat="of" target="section-3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-transition-process">Transition Process</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.3.2">
              <li pn="section-toc.1-1.3.2.1">
                <t indent="0" keepWithNext="true" pn="section-toc.1-1.3.2.1.1"><xref derivedContent="3.1" format="counter" sectionFormat="of" target="section-3.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-dedicated-nameserver-hostna">Dedicated Nameserver Hostnames</xref></t>
              </li>
              <li pn="section-toc.1-1.3.2.2">
                <t indent="0" pn="section-toc.1-1.3.2.2.1"><xref derivedContent="3.2" format="counter" sectionFormat="of" target="section-3.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-separation-of-infrastructur">Separation of Infrastructure</xref></t>
              </li>
              <li pn="section-toc.1-1.3.2.3">
                <t indent="0" pn="section-toc.1-1.3.2.3.1"><xref derivedContent="3.3" format="counter" sectionFormat="of" target="section-3.3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-zone-administration">Zone Administration</xref></t>
              </li>
              <li pn="section-toc.1-1.3.2.4">
                <t indent="0" pn="section-toc.1-1.3.2.4.1"><xref derivedContent="3.4" format="counter" sectionFormat="of" target="section-3.4"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-conclusion-of-process">Conclusion of Process</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.4">
            <t indent="0" pn="section-toc.1-1.4.1"><xref derivedContent="4" format="counter" sectionFormat="of" target="section-4"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-iana-considerations">IANA Considerations</xref></t>
          </li>
          <li pn="section-toc.1-1.5">
            <t indent="0" pn="section-toc.1-1.5.1"><xref derivedContent="5" format="counter" sectionFormat="of" target="section-5"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-security-considerations">Security Considerations</xref></t>
          </li>
          <li pn="section-toc.1-1.6">
            <t indent="0" pn="section-toc.1-1.6.1"><xref derivedContent="6" format="counter" sectionFormat="of" target="section-6"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-references">References</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.6.2">
              <li pn="section-toc.1-1.6.2.1">
                <t indent="0" pn="section-toc.1-1.6.2.1.1"><xref derivedContent="6.1" format="counter" sectionFormat="of" target="section-6.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-normative-references">Normative References</xref></t>
              </li>
              <li pn="section-toc.1-1.6.2.2">
                <t indent="0" pn="section-toc.1-1.6.2.2.1"><xref derivedContent="6.2" format="counter" sectionFormat="of" target="section-6.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-informative-references">Informative References</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.7">
            <t indent="0" pn="section-toc.1-1.7.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.a"/><xref derivedContent="" format="title" sectionFormat="of" target="name-iab-members-at-the-time-of-">IAB Members at the Time of Approval</xref></t>
          </li>
          <li pn="section-toc.1-1.8">
            <t indent="0" pn="section-toc.1-1.8.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.b"/><xref derivedContent="" format="title" sectionFormat="of" target="name-acknowledgments">Acknowledgments</xref></t>
          </li>
          <li pn="section-toc.1-1.9">
            <t indent="0" pn="section-toc.1-1.9.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.c"/><xref derivedContent="" format="title" sectionFormat="of" target="name-authors-addresses">Authors' Addresses</xref></t>
          </li>
        </ul>
      </section>
    </toc>
  </front>
  <middle>
    <section anchor="introduction" numbered="true" toc="include" removeInRFC="false" pn="section-1">
      <name slugifiedName="name-introduction">Introduction</name>
      <t indent="0" pn="section-1-1">The "arpa" top-level domain <xref target="RFC3172" format="default" sectionFormat="of" derivedContent="RFC3172"/> is designated as an
"infrastructure domain" to support techniques defined by Internet
standards. Zones under the "arpa" domain provide various mappings, such
as IP addresses to domain names and E.164 numbers to URIs. It also
contains special-use names such as "home", which is a nonunique name
      used in residential networks.</t>
      <t indent="0" pn="section-1-2">Historically, the "arpa" zone has been hosted on almost all of the
root nameservers (NSs), and <xref target="RFC3172" format="default" sectionFormat="of" derivedContent="RFC3172"/> envisages the "arpa" domain to be
"sufficiently critical that the operational requirements for the root
servers apply to the operational requirements of the "arpa" servers". To
date, this has been implemented by serving the "arpa" domain directly on
a subset of the root server infrastructure.</t>
      <t indent="0" pn="section-1-3">This bundling of root nameserver and "arpa" nameserver operations has entwined
management of the zones' contents and their infrastructures. As a result,
some proposals under consideration by the IETF involving the "arpa" zone
have been discarded due to the risk of conflict with operations associated
with managing the content of the root zone or administering the root
nameservers.</t>
      <t indent="0" pn="section-1-4">The separation described in this document resolves the operational impacts
of synchronizing edits to the root zone and the "arpa" zone by
eliminating the current dependency and allowing more tailored operations
based on the unique requirements of each zone.</t>
    </section>
    <section anchor="requirements-for-the-arpa-zone" numbered="true" toc="include" removeInRFC="false" pn="section-2">
      <name slugifiedName="name-requirements-for-the-arpa-z">Requirements for the "arpa" Zone</name>
      <t indent="0" pn="section-2-1">The "arpa" domain continues to play a role in critical Internet
operations, and this change does not propose weakening operational
requirements described in <xref target="RFC3172" format="default" sectionFormat="of" derivedContent="RFC3172"/> for the domain. Future operational
requirements for the "arpa" domain are encouraged to follow strong
baseline requirements such as those documented in <xref target="RFC7720" format="default" sectionFormat="of" derivedContent="RFC7720"/>.</t>
      <t indent="0" pn="section-2-2">Changes to the administration of the "arpa" zone do not alter the
management practices of other zones delegated within the "arpa"
namespace. For example, "ip6.arpa" would continue to be managed in
accordance with <xref target="RFC5855" format="default" sectionFormat="of" derivedContent="RFC5855"/>.</t>
    </section>
    <section anchor="transition-process" numbered="true" toc="include" removeInRFC="false" pn="section-3">
      <name slugifiedName="name-transition-process">Transition Process</name>
      <t indent="0" pn="section-3-1">The process will dedicate new hostnames to the servers that are authoritative for
the "arpa" zone, but it will initially serve the "arpa" zone from the same
hosts.</t>
      <t indent="0" pn="section-3-2">Once completed, subsequent transitional phases could include using
new hosts to replace or augment the existing root nameserver hosts and
separating the editing and distribution of the "arpa" zone from
necessarily being connected to the root zone. Any future management
considerations regarding how such changes may be performed are beyond
the scope of this document.</t>
      <section anchor="dedicated-nameserver-hostnames" numbered="true" toc="include" removeInRFC="false" pn="section-3.1">
        <name slugifiedName="name-dedicated-nameserver-hostna">Dedicated Nameserver Hostnames</name>
        <t indent="0" pn="section-3.1-1">Consistent with the use of the "arpa" namespace itself to host nameservers for other delegations in the "arpa" zone <xref target="RFC5855" format="default" sectionFormat="of" derivedContent="RFC5855"/>, this
document specifies a new namespace of "ns.arpa", with the
nameserver set for the "arpa" zone to be initially labeled as follows:</t>
        <artwork name="" type="" align="left" alt="" pn="section-3.1-2">
   a.ns.arpa
   b.ns.arpa
   c.ns.arpa
   ...
</artwork>
        <t indent="0" pn="section-3.1-3">Dedicated hostnames eliminate a logical dependency that requires the
coordinated editing of the nameservers for the "arpa" zone and the root
zone. This component of this transition does not require that the underlying
hosts that provide "arpa" name service (that is, the root nameservers) be
altered. The "arpa" zone will initially map the new hostnames to the
same IP addresses that already provide service under the respective
hostnames within "root-servers.net".</t>
        <t indent="0" pn="section-3.1-4">Because these nameservers are completely within the "arpa" zone, they
will require glue records in the root zone. This is consistent with
current practice and requires no operational changes to the root zone.</t>
      </section>
      <section anchor="separation-of-infrastructure" numbered="true" toc="include" removeInRFC="false" pn="section-3.2">
        <name slugifiedName="name-separation-of-infrastructur">Separation of Infrastructure</name>
        <t indent="0" pn="section-3.2-1">After initially migrating the "arpa" zone to use hostnames that are not shared
with the root zone, the underlying name service is expected to evolve such that
it no longer directly aligns with a subset of root nameserver instances. With no
shared infrastructure between the root nameservers and the "arpa" nameservers, future
novel applications for the "arpa" zone may be possible.</t>
        <t indent="0" pn="section-3.2-2">Any subsequent change to the parties providing name service for the
zone is considered a normal management responsibility and would be
performed in accordance with <xref target="RFC3172" format="default" sectionFormat="of" derivedContent="RFC3172"/>.</t>
      </section>
      <section anchor="zone-administration" numbered="true" toc="include" removeInRFC="false" pn="section-3.3">
        <name slugifiedName="name-zone-administration">Zone Administration</name>
        <t indent="0" pn="section-3.3-1">Publication of the "arpa" zone file to the authoritative "arpa" nameservers is currently undertaken alongside the root zone maintenance functions.
Upon the separation of the "arpa" infrastructure from the root nameserver
infrastructure, publication of the "arpa" zone no longer necessarily needs
to be technically linked or interrelated to the root zone publication
mechanisms.</t>
      </section>
      <section anchor="conclusion-of-process" numbered="true" toc="include" removeInRFC="false" pn="section-3.4">
        <name slugifiedName="name-conclusion-of-process">Conclusion of Process</name>
        <t indent="0" pn="section-3.4-1">Full technical separation of operations of the "arpa" zone and root zone 
minimally requires the following to be satisfied:</t>
        <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-3.4-2">
          <li pn="section-3.4-2.1">The "arpa" zone no longer shares any hostnames in its nameserver set with the root
zone.</li>
          <li pn="section-3.4-2.2">The hosts that provide authoritative name service are not the same hosts
as the root nameservers, do not share any IPv4 or IPv6 addresses with the
root servers, and are sufficiently provisioned separately such
that any unique "arpa" zone requirements can be deployed without affecting
how root zone service is provided.</li>
          <li pn="section-3.4-2.3">The editorial and publication process for the "arpa" zone removes any common dependencies with the root zone process so that the "arpa" zone 
can be managed, edited, and provisioned wholly independently of the
root zone.</li>
        </ul>
        <t indent="0" pn="section-3.4-3">Such separation is ultimately sought to allow for novel uses of
the "arpa" zone without the risk of inadvertently impacting root zone and root
server operations. It is recognized that achieving this state requires a
deliberative process involving significant coordination to ensure impacts
are minimized.</t>
      </section>
    </section>
    <section anchor="iana-considerations" numbered="true" toc="include" removeInRFC="false" pn="section-4">
      <name slugifiedName="name-iana-considerations">IANA Considerations</name>
      <t indent="0" pn="section-4-1">IANA shall coordinate the creation of the "ns.arpa" namespace and
populate it with address records that reflect the IP addresses of the
contemporary root servers documented within "root-servers.net" as its
initial state. The namespace may be provisioned either directly within
the "arpa" zone (as an empty nonterminal) or through establishing
a dedicated "ns.arpa" zone, according to operational requirements.</t>
      <t indent="0" pn="section-4-2">IANA will initially migrate the 12 NS records for the "arpa" zone
      to point to their respective new entries in the "ns.arpa" domain.</t>
      <t indent="0" pn="section-4-3">When these actions are complete, the IAB and IANA will consult
and coordinate with all relevant parties on activity to reduce
or eliminate reliance upon the root zone and root server
 infrastructure serving the "arpa" zone. Such
changes will be performed in compliance with <xref target="RFC3172" format="default" sectionFormat="of" derivedContent="RFC3172"/> and shall be
conducted with all due care and deliberation to mitigate potential
impacts on critical infrastructure.</t>
    </section>
    <section anchor="security-considerations" numbered="true" toc="include" removeInRFC="false" pn="section-5">
      <name slugifiedName="name-security-considerations">Security Considerations</name>
      <t indent="0" pn="section-5-1">The security of the "arpa" zone is not necessarily impacted by any
aspects of these changes. Robust practices associated with administering
the content of the zone (including signing the zone with DNSSEC) as well
      as its distribution will continue to be necessary.</t>
    </section>
  </middle>
  <back>
    <references pn="section-6">
      <name slugifiedName="name-references">References</name>
      <references pn="section-6.1">
        <name slugifiedName="name-normative-references">Normative References</name>
        <reference anchor="RFC3172" target="https://www.rfc-editor.org/info/rfc3172" quoteTitle="true" derivedAnchor="RFC3172">
          <front>
            <title>Management Guidelines &amp; Operational Requirements for the Address and Routing Parameter Area Domain ("arpa")</title>
            <author initials="G." surname="Huston" fullname="G. Huston" role="editor">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2001" month="September"/>
            <abstract>
              <t indent="0">This memo describes the management and operational requirements for the address and routing parameter area ("arpa") domain.  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="52"/>
          <seriesInfo name="RFC" value="3172"/>
          <seriesInfo name="DOI" value="10.17487/RFC3172"/>
        </reference>
      </references>
      <references pn="section-6.2">
        <name slugifiedName="name-informative-references">Informative References</name>
        <reference anchor="RFC5855" target="https://www.rfc-editor.org/info/rfc5855" quoteTitle="true" derivedAnchor="RFC5855">
          <front>
            <title>Nameservers for IPv4 and IPv6 Reverse Zones</title>
            <author initials="J." surname="Abley" fullname="J. Abley">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="T." surname="Manderson" fullname="T. Manderson">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2010" month="May"/>
            <abstract>
              <t indent="0">This document specifies a stable naming scheme for the nameservers that serve the zones IN-ADDR.ARPA and IP6.ARPA in the DNS.  These zones contain data that facilitate reverse mapping (address to name).  This memo documents an Internet Best Current Practice.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="155"/>
          <seriesInfo name="RFC" value="5855"/>
          <seriesInfo name="DOI" value="10.17487/RFC5855"/>
        </reference>
        <reference anchor="RFC7720" target="https://www.rfc-editor.org/info/rfc7720" quoteTitle="true" derivedAnchor="RFC7720">
          <front>
            <title>DNS Root Name Service Protocol and Deployment Requirements</title>
            <author initials="M." surname="Blanchet" fullname="M. Blanchet">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="L-J." surname="Liman" fullname="L-J. Liman">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2015" month="December"/>
            <abstract>
              <t indent="0">The DNS root name service is a critical part of the Internet architecture.  The protocol and deployment requirements for the DNS root name service are defined in this document.  Operational requirements are out of scope.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="40"/>
          <seriesInfo name="RFC" value="7720"/>
          <seriesInfo name="DOI" value="10.17487/RFC7720"/>
        </reference>
      </references>
    </references>
    <section numbered="false" anchor="members" toc="include" removeInRFC="false" pn="section-appendix.a">
      <name slugifiedName="name-iab-members-at-the-time-of-">IAB Members at the Time of Approval</name>
      <t indent="0" pn="section-appendix.a-1">Internet Architecture Board members at the time this document was
approved for publication were:</t>
      <ul empty="true" indent="3" spacing="compact" bare="false" pn="section-appendix.a-2">
        <li pn="section-appendix.a-2.1">
          <t indent="0" pn="section-appendix.a-2.1.1"><contact fullname="Jari Arkko"/></t>
        </li>
        <li pn="section-appendix.a-2.2">
          <t indent="0" pn="section-appendix.a-2.2.1"><contact fullname="Deborah Brungard"/></t>
        </li>
        <li pn="section-appendix.a-2.3">
          <t indent="0" pn="section-appendix.a-2.3.1"><contact fullname="Ben Campbell"/></t>
        </li>
        <li pn="section-appendix.a-2.4">
          <t indent="0" pn="section-appendix.a-2.4.1"><contact fullname="Lars Eggert"/></t>
        </li>
        <li pn="section-appendix.a-2.5">
          <t indent="0" pn="section-appendix.a-2.5.1"><contact fullname="Wes Hardaker"/></t>
        </li>
        <li pn="section-appendix.a-2.6">
          <t indent="0" pn="section-appendix.a-2.6.1"><contact fullname="Cullen Jennings"/></t>
        </li>
        <li pn="section-appendix.a-2.7">
          <t indent="0" pn="section-appendix.a-2.7.1"><contact fullname="Mirja Kühlewind"/></t>
        </li>
        <li pn="section-appendix.a-2.8">
          <t indent="0" pn="section-appendix.a-2.8.1"><contact fullname="Zhenbin Li"/></t>
        </li>
        <li pn="section-appendix.a-2.9">
          <t indent="0" pn="section-appendix.a-2.9.1"><contact fullname="Jared Mauch"/></t>
        </li>
        <li pn="section-appendix.a-2.10">
          <t indent="0" pn="section-appendix.a-2.10.1"><contact fullname="Tommy Pauly"/></t>
        </li>
        <li pn="section-appendix.a-2.11">
          <t indent="0" pn="section-appendix.a-2.11.1"><contact fullname="David Schinazi"/></t>
        </li>
        <li pn="section-appendix.a-2.12">
          <t indent="0" pn="section-appendix.a-2.12.1"><contact fullname="Russ White"/></t>
        </li>
        <li pn="section-appendix.a-2.13">
          <t indent="0" pn="section-appendix.a-2.13.1"><contact fullname="Jiankang Yao"/></t>
        </li>
      </ul>
    </section>
    <section numbered="false" anchor="acknowledgments" toc="include" removeInRFC="false" pn="section-appendix.b">
      <name slugifiedName="name-acknowledgments">Acknowledgments</name>
      <t indent="0" pn="section-appendix.b-1">Thank you <contact fullname="Alissa Cooper"/>, <contact fullname="Michelle Cotton"/>, <contact fullname="Lars-Johan Liman"/>, <contact fullname="Wes Hardaker"/>,
<contact fullname="Ted Hardie"/>, <contact fullname="Paul Hoffman"/>, <contact fullname="Russ Housley"/>, <contact fullname="Oscar Robles-Garay"/>, <contact fullname="Duane Wessels"/>, and <contact fullname="Suzanne Woolf"/> for providing review and feedback.</t>
    </section>
    <section anchor="authors-addresses" numbered="false" removeInRFC="false" toc="include" pn="section-appendix.c">
      <name slugifiedName="name-authors-addresses">Authors' Addresses</name>
      <author initials="K." surname="Davies" fullname="Kim Davies">
        <organization showOnFrontPage="false">Internet Assigned Numbers Authority</organization>
        <address>
          <postal>
            <street>PTI/ICANN</street>
            <street>12025 Waterfront Drive</street>
            <city>Los Angeles</city>
            <region>CA</region>
            <code>90094</code>
            <country>United States of America</country>
          </postal>
          <email>kim.davies@iana.org</email>
        </address>
      </author>
      <author initials="J." surname="Arkko" fullname="Jari Arkko">
        <organization showOnFrontPage="false">Ericsson Research</organization>
        <address>
          <postal>
            <street>02700 Kauniainen</street>
            <country>Finland</country>
          </postal>
          <email>jari.arkko@ericsson.com</email>
        </address>
      </author>
    </section>
  </back>
</rfc>
