<?xml version='1.0' encoding='utf-8'?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" version="3" category="std" docName="draft-ietf-regext-epp-ttl-18" number="9803" ipr="trust200902" submissionType="IETF" consensus="true" tocInclude="true" tocDepth="4" symRefs="true" sortRefs="true" updates="" obsoletes="" xml:lang="en" prepTime="2025-06-13T15:43:34" indexInclude="true" scripts="Common,Latin">
  <link href="https://datatracker.ietf.org/doc/draft-ietf-regext-epp-ttl-18" rel="prev"/>
  <link href="https://dx.doi.org/10.17487/rfc9803" rel="alternate"/>
  <link href="urn:issn:2070-1721" rel="alternate"/>
  <front>
    <title abbrev="TTL Mapping for EPP">Extensible Provisioning Protocol (EPP) Mapping for DNS Time-to-Live (TTL) Values</title>
    <seriesInfo name="RFC" value="9803" stream="IETF"/>
    <author fullname="Gavin Brown">
      <organization showOnFrontPage="true">ICANN</organization>
      <address>
        <postal>
          <street>12025 Waterfront Drive, Suite 300</street>
          <city>Los Angeles</city>
          <region>CA</region>
          <code>90292</code>
          <country>United States of America</country>
        </postal>
        <email>gavin.brown@icann.org</email>
        <uri>https://www.icann.org/</uri>
      </address>
    </author>
    <date month="06" year="2025"/>
    <area>ART</area>
    <workgroup>regext</workgroup>
    <keyword>EPP</keyword>
    <keyword>DNS</keyword>
    <keyword>TTL</keyword>
    <keyword>time-to-live</keyword>
    <abstract pn="section-abstract">
      <t indent="0" pn="section-abstract-1">This document describes an extension to the Extensible Provisioning
      Protocol (EPP) that allows EPP clients to manage the Time-to-Live (TTL)
      value for domain name delegation records.
      </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 is an Internet Standards Track document.
        </t>
        <t indent="0" pn="section-boilerplate.1-2">
            This document is a product of the Internet Engineering Task Force
            (IETF).  It represents the consensus of the IETF community.  It has
            received public review and has been approved for publication by
            the Internet Engineering Steering Group (IESG).  Further
            information on Internet Standards is available in 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/rfc9803" 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) 2025 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. Code Components extracted from this
            document must include Revised BSD License text as described in
            Section 4.e of the Trust Legal Provisions and are provided without
            warranty as described in the Revised BSD License.
        </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" 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>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.1.2">
              <li pn="section-toc.1-1.1.2.1">
                <t indent="0" keepWithNext="true" pn="section-toc.1-1.1.2.1.1"><xref derivedContent="1.1" format="counter" sectionFormat="of" target="section-1.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-conventions-used-in-this-do">Conventions Used in This Document</xref></t>
              </li>
              <li pn="section-toc.1-1.1.2.2">
                <t indent="0" pn="section-toc.1-1.1.2.2.1"><xref derivedContent="1.2" format="counter" sectionFormat="of" target="section-1.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-extension-elements">Extension Elements</xref></t>
                <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.1.2.2.2">
                  <li pn="section-toc.1-1.1.2.2.2.1">
                    <t indent="0" pn="section-toc.1-1.1.2.2.2.1.1"><xref derivedContent="1.2.1" format="counter" sectionFormat="of" target="section-1.2.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-the-ttlttl-element">The &lt;ttl:ttl&gt; Element</xref></t>
                    <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.1.2.2.2.1.2">
                      <li pn="section-toc.1-1.1.2.2.2.1.2.1">
                        <t indent="0" keepWithNext="true" pn="section-toc.1-1.1.2.2.2.1.2.1.1"><xref derivedContent="1.2.1.1" format="counter" sectionFormat="of" target="section-1.2.1.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-element-content">Element Content</xref></t>
                      </li>
                      <li pn="section-toc.1-1.1.2.2.2.1.2.2">
                        <t indent="0" keepWithNext="true" pn="section-toc.1-1.1.2.2.2.1.2.2.1"><xref derivedContent="1.2.1.2" format="counter" sectionFormat="of" target="section-1.2.1.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-supported-dns-record-types">Supported DNS Record Types</xref></t>
                      </li>
                      <li pn="section-toc.1-1.1.2.2.2.1.2.3">
                        <t indent="0" pn="section-toc.1-1.1.2.2.2.1.2.3.1"><xref derivedContent="1.2.1.3" format="counter" sectionFormat="of" target="section-1.2.1.3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-the-ttlinfo-element">The &lt;ttl:info&gt; Element</xref></t>
                      </li>
                    </ul>
                  </li>
                  <li pn="section-toc.1-1.1.2.2.2.2">
                    <t indent="0" pn="section-toc.1-1.1.2.2.2.2.1"><xref derivedContent="1.2.2" format="counter" sectionFormat="of" target="section-1.2.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-examples">Examples</xref></t>
                    <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.1.2.2.2.2.2">
                      <li pn="section-toc.1-1.1.2.2.2.2.2.1">
                        <t indent="0" pn="section-toc.1-1.1.2.2.2.2.2.1.1"><xref derivedContent="1.2.2.1" format="counter" sectionFormat="of" target="section-1.2.2.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-explicit-ttl-value-create-o">Explicit TTL Value (&lt;create&gt; or &lt;update&gt; Command)</xref></t>
                      </li>
                      <li pn="section-toc.1-1.1.2.2.2.2.2.2">
                        <t indent="0" pn="section-toc.1-1.1.2.2.2.2.2.2.1"><xref derivedContent="1.2.2.2" format="counter" sectionFormat="of" target="section-1.2.2.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-explicit-ttl-value-info-pol">Explicit TTL Value (&lt;info&gt; Policy Mode)</xref></t>
                      </li>
                      <li pn="section-toc.1-1.1.2.2.2.2.2.3">
                        <t indent="0" pn="section-toc.1-1.1.2.2.2.2.2.3.1"><xref derivedContent="1.2.2.3" format="counter" sectionFormat="of" target="section-1.2.2.3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-empty-value-indicating-defa">Empty Value Indicating Default TTL (&lt;create&gt; or &lt;update&gt; Command, &lt;info&gt; Default Mode)</xref></t>
                      </li>
                      <li pn="section-toc.1-1.1.2.2.2.2.2.4">
                        <t indent="0" pn="section-toc.1-1.1.2.2.2.2.2.4.1"><xref derivedContent="1.2.2.4" format="counter" sectionFormat="of" target="section-1.2.2.4"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-custom-record-type-create-o">Custom Record Type (&lt;create&gt; or &lt;update&gt; Command, &lt;info&gt; Default Mode)</xref></t>
                      </li>
                    </ul>
                  </li>
                </ul>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.2">
            <t indent="0" 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-epp-command-mapping">EPP Command Mapping</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.2.2">
              <li pn="section-toc.1-1.2.2.1">
                <t indent="0" pn="section-toc.1-1.2.2.1.1"><xref derivedContent="2.1" format="counter" sectionFormat="of" target="section-2.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-epp-query-commands">EPP Query Commands</xref></t>
                <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.2.2.1.2">
                  <li pn="section-toc.1-1.2.2.1.2.1">
                    <t indent="0" pn="section-toc.1-1.2.2.1.2.1.1"><xref derivedContent="2.1.1" format="counter" sectionFormat="of" target="section-2.1.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-epp-info-command">EPP &lt;info&gt; Command</xref></t>
                    <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.2.2.1.2.1.2">
                      <li pn="section-toc.1-1.2.2.1.2.1.2.1">
                        <t indent="0" pn="section-toc.1-1.2.2.1.2.1.2.1.1"><xref derivedContent="2.1.1.1" format="counter" sectionFormat="of" target="section-2.1.1.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-default-mode">Default Mode</xref></t>
                      </li>
                      <li pn="section-toc.1-1.2.2.1.2.1.2.2">
                        <t indent="0" pn="section-toc.1-1.2.2.1.2.1.2.2.1"><xref derivedContent="2.1.1.2" format="counter" sectionFormat="of" target="section-2.1.1.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-policy-mode">Policy Mode</xref></t>
                      </li>
                    </ul>
                  </li>
                </ul>
              </li>
              <li pn="section-toc.1-1.2.2.2">
                <t indent="0" pn="section-toc.1-1.2.2.2.1"><xref derivedContent="2.2" format="counter" sectionFormat="of" target="section-2.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-epp-transform-commands">EPP Transform Commands</xref></t>
                <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.2.2.2.2">
                  <li pn="section-toc.1-1.2.2.2.2.1">
                    <t indent="0" pn="section-toc.1-1.2.2.2.2.1.1"><xref derivedContent="2.2.1" format="counter" sectionFormat="of" target="section-2.2.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-epp-create-command">EPP &lt;create&gt; Command</xref></t>
                  </li>
                  <li pn="section-toc.1-1.2.2.2.2.2">
                    <t indent="0" pn="section-toc.1-1.2.2.2.2.2.1"><xref derivedContent="2.2.2" format="counter" sectionFormat="of" target="section-2.2.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-epp-update-command">EPP &lt;update&gt; Command</xref></t>
                  </li>
                </ul>
              </li>
            </ul>
          </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-server-processing-of-ttl-va">Server Processing of TTL Values</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" 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-permitted-record-types">Permitted Record Types</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-use-of-ttl-values-in-delega">Use of TTL Values in Delegation Records</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-out-of-band-changes-to-ttl-">Out-of-Band Changes to TTL Values</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-operational-considerations">Operational Considerations</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.5.2">
              <li pn="section-toc.1-1.5.2.1">
                <t indent="0" pn="section-toc.1-1.5.2.1.1"><xref derivedContent="5.1" format="counter" sectionFormat="of" target="section-5.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-operational-impact-of-ttl-v">Operational Impact of TTL Values</xref></t>
              </li>
              <li pn="section-toc.1-1.5.2.2">
                <t indent="0" pn="section-toc.1-1.5.2.2.1"><xref derivedContent="5.2" format="counter" sectionFormat="of" target="section-5.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-when-ttl-values-should-be-c">When TTL Values Should Be Changed</xref></t>
              </li>
              <li pn="section-toc.1-1.5.2.3">
                <t indent="0" pn="section-toc.1-1.5.2.3.1"><xref derivedContent="5.3" format="counter" sectionFormat="of" target="section-5.3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-changes-to-server-policy">Changes to Server Policy</xref></t>
              </li>
            </ul>
          </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-security-considerations">Security Considerations</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-fast-flux-dns">Fast Flux DNS</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-compromised-user-accounts">Compromised User Accounts</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.7">
            <t indent="0" pn="section-toc.1-1.7.1"><xref derivedContent="7" format="counter" sectionFormat="of" target="section-7"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-iana-considerations">IANA Considerations</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.7.2">
              <li pn="section-toc.1-1.7.2.1">
                <t indent="0" pn="section-toc.1-1.7.2.1.1"><xref derivedContent="7.1" format="counter" sectionFormat="of" target="section-7.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-xml-namespace">XML Namespace</xref></t>
              </li>
              <li pn="section-toc.1-1.7.2.2">
                <t indent="0" pn="section-toc.1-1.7.2.2.1"><xref derivedContent="7.2" format="counter" sectionFormat="of" target="section-7.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-epp-extension-registry">EPP Extension Registry</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.8">
            <t indent="0" pn="section-toc.1-1.8.1"><xref derivedContent="8" format="counter" sectionFormat="of" target="section-8"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-formal-syntax">Formal Syntax</xref></t>
          </li>
          <li pn="section-toc.1-1.9">
            <t indent="0" pn="section-toc.1-1.9.1"><xref derivedContent="9" format="counter" sectionFormat="of" target="section-9"/>.  <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.9.2">
              <li pn="section-toc.1-1.9.2.1">
                <t indent="0" pn="section-toc.1-1.9.2.1.1"><xref derivedContent="9.1" format="counter" sectionFormat="of" target="section-9.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-normative-references">Normative References</xref></t>
              </li>
              <li pn="section-toc.1-1.9.2.2">
                <t indent="0" pn="section-toc.1-1.9.2.2.1"><xref derivedContent="9.2" format="counter" sectionFormat="of" target="section-9.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-informative-references">Informative References</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.10">
            <t indent="0" pn="section-toc.1-1.10.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.a"/><xref derivedContent="" format="title" sectionFormat="of" target="name-acknowledgments">Acknowledgments</xref></t>
          </li>
          <li pn="section-toc.1-1.11">
            <t indent="0" pn="section-toc.1-1.11.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.b"/><xref derivedContent="" format="title" sectionFormat="of" target="name-authors-address">Author's Address</xref></t>
          </li>
        </ul>
      </section>
    </toc>
  </front>
  <middle>
    <section numbered="true" removeInRFC="false" toc="include" pn="section-1">
      <name slugifiedName="name-introduction">Introduction</name>
      <t indent="0" pn="section-1-1">
	The principal output of any domain name registry system is a DNS zone
	file, which contains the delegation record(s) for names registered
	within a zone (such as a top-level domain).  These records typically
	include one or more <tt>NS</tt> records, but may also include
	<tt>DS</tt> records for domains secured with DNSSEC <xref target="RFC9364" format="default" sectionFormat="of" derivedContent="RFC9364"/>, and <tt>DNAME</tt> records for Internationalized Domain Name (IDN) variants <xref target="RFC6927" format="default" sectionFormat="of" derivedContent="RFC6927"/>.  <tt>A</tt> and/or <tt>AAAA</tt> records may also
	be published for nameservers where they are required by DNS resolvers
	to avoid an infinite loop.</t>
      <t indent="0" pn="section-1-2">
	Typically, the Time-to-Live (TTL) value (see <xref section="5" sectionFormat="of" target="RFC9499" format="default" derivedLink="https://rfc-editor.org/rfc/rfc9499#section-5" derivedContent="RFC9499"/>) of these records is determined
	by the registry operator.  However, in some circumstances it may be
	desirable to allow the sponsoring client of a domain name to change
	the TTL values used for that domain's delegation: for example, to
	reduce the amount of time required to complete a change of DNS
	servers, DNSSEC deployment or key rollover, or to allow for fast
	rollback of such changes.</t>
      <t indent="0" pn="section-1-3">
	This document describes an EPP extension to the domain name and host
	object mappings (described in <xref target="RFC5731" format="default" sectionFormat="of" derivedContent="RFC5731"/> and <xref target="RFC5732" format="default" sectionFormat="of" derivedContent="RFC5732"/>, respectively) that allows the sponsor of a domain
	name or host object to change the TTL values of the resource record(s)
	associated with that object.  It also describes how EPP servers should
	handle TTLs specified by EPP clients and how both parties coordinate
	to manage TTL values in response to changes in operational or security
	requirements.</t>
      <section numbered="true" removeInRFC="false" toc="include" pn="section-1.1">
        <name slugifiedName="name-conventions-used-in-this-do">Conventions Used in This Document</name>
        <t indent="0" pn="section-1.1-1">
    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" format="default" sectionFormat="of" derivedContent="RFC2119"/> <xref target="RFC8174" format="default" sectionFormat="of" derivedContent="RFC8174"/> when, and only when, they appear in all capitals, as
    shown here.
        </t>
        <t indent="0" pn="section-1.1-2">
	  In this document's examples, "C:" represents lines sent by a protocol client and
	  "S:" represents lines returned by a protocol server.  Indentation
	  and white space in these examples are provided only to illustrate element
	  relationships and are not required features of this protocol.</t>
        <t indent="0" pn="section-1.1-3">
	  A protocol client that is authorized to manage an existing object is
	  described as a "sponsoring" client throughout this document.</t>
        <t indent="0" pn="section-1.1-4">
	  XML is case sensitive.  Unless stated otherwise, the XML specifications
	  and examples provided in this document <bcp14>MUST</bcp14> be
	  interpreted in the character case presented in order to develop a
	  conforming implementation.</t>
        <t indent="0" pn="section-1.1-5">
	  EPP uses XML namespaces to provide an extensible object management
	  framework and to identify schemas required for XML instance parsing
	  and validation.  These namespaces and schema definitions are used to
	  identify both the base protocol schema and the schemas for managed
	  objects.</t>
        <t indent="0" pn="section-1.1-6">
	  The XML namespace prefixes used in these examples (such as the string
	  <tt>ttl</tt> in <tt>ttl:create</tt>) are solely for illustrative
	  purposes.  A conforming implementation <bcp14>MUST NOT</bcp14>
	  require the use of these or any other specific namespace prefixes.</t>
        <t indent="0" pn="section-1.1-7">
	  In accordance with Section 3.2.2.1 of XML Schema Part 2: Datatypes
	  <xref target="XSD-DATATYPES" format="default" sectionFormat="of" derivedContent="XSD-DATATYPES"/>, the allowable lexical
	  representations for the <tt>xs:boolean</tt> datatype are the strings
	  "<tt>0</tt>" and "<tt>false</tt>" for the concept 'false' and the
	  strings "<tt>1</tt>" and "<tt>true</tt>" for the concept 'true'.
	  Implementations <bcp14>MUST</bcp14> support both styles of lexical
	  representation.</t>
      </section>
      <section anchor="extension-elements" numbered="true" removeInRFC="false" toc="include" pn="section-1.2">
        <name slugifiedName="name-extension-elements">Extension Elements</name>
        <t indent="0" pn="section-1.2-1">This extension adds additional elements to the EPP domain and host mappings.</t>
        <section anchor="ttl_element" numbered="true" removeInRFC="false" toc="include" pn="section-1.2.1">
          <name slugifiedName="name-the-ttlttl-element">The &lt;ttl:ttl&gt; Element</name>
          <t indent="0" pn="section-1.2.1-1">
	    The <tt>&lt;ttl:ttl&gt;</tt> element is used to define TTL values
	    for the DNS resource records associated with domain and host
	    objects.
          </t>
          <t indent="0" pn="section-1.2.1-2">
	    <tt>&lt;ttl:ttl&gt;</tt> elements have the optional following
	    attributes, depending on whether they appear in an EPP command or
	    response:
          </t>
          <dl newline="true" indent="3" spacing="normal" pn="section-1.2.1-3">
            <dt pn="section-1.2.1-3.1">"<tt>for</tt>"</dt>
            <dd pn="section-1.2.1-3.2">
              <bcp14>REQUIRED</bcp14> in both commands and responses, and
	      specifies the DNS record type to which the TTL value pertains.
	      This attribute <bcp14>MUST</bcp14> have one of the following
	      values: "<tt>NS</tt>", "<tt>DS</tt>", "<tt>DNAME</tt>",
	      "<tt>A</tt>", "<tt>AAAA</tt>" or "<tt>custom</tt>".
	    </dd>
            <dt pn="section-1.2.1-3.3">"<tt>custom</tt>"</dt>
            <dd pn="section-1.2.1-3.4">If the value of the "<tt>for</tt>" attribute is
	      "<tt>custom</tt>", then the <tt>&lt;ttl:ttl&gt;</tt> element
	      <bcp14>MUST</bcp14> also have a "<tt>custom</tt>" attribute
	      containing a DNS record type conforming with the regular
	      expression in <xref sectionFormat="of" section="3.1" target="RFC6895" format="default" derivedLink="https://rfc-editor.org/rfc/rfc6895#section-3.1" derivedContent="RFC6895"/>.  Additionally, the record type
	      <bcp14>MUST</bcp14> be registered with IANA in <xref target="IANA-RRTYPES" format="default" sectionFormat="of" derivedContent="IANA-RRTYPES"/>.
	      </dd>
            <dt pn="section-1.2.1-3.5">"<tt>min</tt>"</dt>
            <dd pn="section-1.2.1-3.6">
              <bcp14>MUST NOT</bcp14> be present in EPP commands but
	      <bcp14>MAY</bcp14> be present in EPP responses (see <xref target="info-command" format="default" sectionFormat="of" derivedContent="Section 2.1.1"/>). It is used by the server to
	      indicate the lowest value that may be set.
	    </dd>
            <dt pn="section-1.2.1-3.7">"<tt>default</tt>"</dt>
            <dd pn="section-1.2.1-3.8">
              <bcp14>MUST NOT</bcp14> be present in EPP commands but
	      <bcp14>MAY</bcp14> be present in EPP responses (see <xref target="info-command" format="default" sectionFormat="of" derivedContent="Section 2.1.1"/>). It is used by the server to
	      indicate the default value.
	    </dd>
            <dt pn="section-1.2.1-3.9">"<tt>max</tt>"</dt>
            <dd pn="section-1.2.1-3.10">
              <bcp14>MUST NOT</bcp14> be present in EPP commands but
	      <bcp14>MAY</bcp14> be present in EPP responses (see <xref target="info-command" format="default" sectionFormat="of" derivedContent="Section 2.1.1"/>). It is used by the server to
	      indicate the highest value that may be set.
	    </dd>
          </dl>
          <t indent="0" pn="section-1.2.1-4">
	    When present, the value of the "<tt>min</tt>" attribute
	    <bcp14>MUST</bcp14> be lower than the value of the "<tt>max</tt>"
	    attribute. The "<tt>default</tt>" attribute <bcp14>MUST</bcp14> be
	    between the "<tt>min</tt>" and "<tt>max</tt>" values, inclusively.</t>
          <section anchor="element-content" numbered="true" removeInRFC="false" toc="include" pn="section-1.2.1.1">
            <name slugifiedName="name-element-content">Element Content</name>
            <t indent="0" pn="section-1.2.1.1-1">
	      The XML schema found in <xref target="formal-syntax" format="default" sectionFormat="of" derivedContent="Section 8"/> of this
	      document restricts the content of <tt>&lt;ttl:ttl&gt;</tt>
	      elements to be either:</t>
            <ol indent="adaptive" spacing="normal" start="1" type="1" pn="section-1.2.1.1-2">
              <li pn="section-1.2.1.1-2.1" derivedCounter="1.">a non-negative integer, indicating the value of the TTL in seconds, or</li>
              <li pn="section-1.2.1.1-2.2" derivedCounter="2.">empty, in which case the server's default TTL for the given record type is to be applied.</li>
            </ol>
          </section>
          <section anchor="supported-dns-record-types" numbered="true" removeInRFC="false" toc="include" pn="section-1.2.1.2">
            <name slugifiedName="name-supported-dns-record-types">Supported DNS Record Types</name>
            <t indent="0" pn="section-1.2.1.2-1">
	      To facilitate forward compatibility with future changes to the
	      DNS protocol, this document does not enumerate or restrict the
	      DNS record types that can be included in the "<tt>custom</tt>"
	      attribute of the <tt>&lt;ttl:ttl&gt;</tt> element.</t>
            <t indent="0" pn="section-1.2.1.2-2">
	      The regular expression that is used to validate the values of
	      the "<tt>custom</tt>" attribute is based on the expression found
	      in <xref sectionFormat="of" section="3.1" target="RFC6895" format="default" derivedLink="https://rfc-editor.org/rfc/rfc6895#section-3.1" derivedContent="RFC6895"/>,
	      and it is intended to match both existing and future RRTYPE
	      mnemonics.  This eliminates the need to update this document in
	      the event that new DNS records that exist above a zone cut
	      (<xref sectionFormat="of" section="7" target="RFC9499" format="default" derivedLink="https://rfc-editor.org/rfc/rfc9499#section-7" derivedContent="RFC9499"/>) are
	      specified.</t>
            <t indent="0" pn="section-1.2.1.2-3">
	      Nevertheless, EPP servers that implement this extension
	      <bcp14>MUST</bcp14> restrict the DNS record types that are
	      accepted in <tt>&lt;create&gt;</tt> and <tt>&lt;update&gt;</tt>
	      commands, and included in <tt>&lt;info&gt;</tt> responses,
	      allowing only those types that are (a) registered in <xref target="IANA-RRTYPES" format="default" sectionFormat="of" derivedContent="IANA-RRTYPES"/> and (b) appropriate for use above a zone
	      cut.</t>
            <t indent="0" pn="section-1.2.1.2-4">
	      A server that receives a <tt>&lt;create&gt;</tt> or
	      <tt>&lt;update&gt;</tt> command that attempts to set TTL values
	      for inapplicable DNS record types <bcp14>MUST</bcp14> respond
	      with a 2306 "Parameter value policy" error.</t>
            <t indent="0" pn="section-1.2.1.2-5">
	      As an illustrative example, a server <bcp14>MAY</bcp14> allow
	      clients to specify TTL values for the following record types for
	      domain objects:
            </t>
            <ol indent="adaptive" spacing="normal" start="1" type="1" pn="section-1.2.1.2-6">
              <li pn="section-1.2.1.2-6.1" derivedCounter="1.">
                <tt>NS</tt>;
	      </li>
              <li pn="section-1.2.1.2-6.2" derivedCounter="2.">
                <tt>DS</tt> (if the server also implements <xref target="RFC5910" format="default" sectionFormat="of" derivedContent="RFC5910"/>);
	      </li>
              <li pn="section-1.2.1.2-6.3" derivedCounter="3.">
                <tt>DNAME</tt> (if the server implements IDN variants using
                <tt>DNAME</tt> records).
	      </li>
            </ol>
            <section numbered="true" removeInRFC="false" toc="exclude" pn="section-1.2.1.2.1">
              <name slugifiedName="name-glue-records">Glue Records</name>
              <t indent="0" pn="section-1.2.1.2.1-1">
		Glue records are described in <xref section="7" sectionFormat="of" target="RFC9499" format="default" derivedLink="https://rfc-editor.org/rfc/rfc9499#section-7" derivedContent="RFC9499"/>.</t>
              <t indent="0" pn="section-1.2.1.2.1-2">
		Servers that implement host objects <xref target="RFC5732" format="default" sectionFormat="of" derivedContent="RFC5732"/>
                <bcp14>MAY</bcp14> allow clients to specify TTL values for
		<tt>A</tt> and <tt>AAAA</tt> records for host objects.</t>
              <t indent="0" pn="section-1.2.1.2.1-3">
		A server supporting host objects that receives a command that
		attempts to set TTL values for <tt>A</tt> and <tt>AAAA</tt>
		records on a domain object <bcp14>MUST</bcp14> respond with a
		2306 "Parameter value policy" error.</t>
              <t indent="0" pn="section-1.2.1.2.1-4">
		EPP servers that use the host attribute model (described in
		<xref sectionFormat="of" section="1.1" target="RFC5731" format="default" derivedLink="https://rfc-editor.org/rfc/rfc5731#section-1.1" derivedContent="RFC5731"/>)
		<bcp14>MAY</bcp14> allow clients to specify TTL values for
		<tt>A</tt> and <tt>AAAA</tt> records for domain objects.</t>
            </section>
          </section>
          <section anchor="info-element" numbered="true" removeInRFC="false" toc="include" pn="section-1.2.1.3">
            <name slugifiedName="name-the-ttlinfo-element">The &lt;ttl:info&gt; Element</name>
            <t indent="0" pn="section-1.2.1.3-1">
	      The <tt>&lt;ttl:info&gt;</tt> element is used by clients to
	      request that the server include additional information in
	      <tt>&lt;info&gt;</tt> responses for domain and host objects.</t>
            <t indent="0" pn="section-1.2.1.3-2">
	      It has a single <bcp14>OPTIONAL</bcp14> "<tt>policy</tt>"
	      attribute, which takes a boolean value with a default value of
	      "<tt>false</tt>".</t>
            <t indent="0" pn="section-1.2.1.3-3">
	      The semantics of this element are described in <xref target="info-command" format="default" sectionFormat="of" derivedContent="Section 2.1.1"/>.</t>
            <t indent="0" pn="section-1.2.1.3-4">Below is an example of a <tt>&lt;ttl:info&gt;</tt>
        element with an explicit "<tt>policy</tt>" attribute:</t>
            <sourcecode type="xml" markers="false" pn="section-1.2.1.3-5">
&lt;ttl:info policy="true"/&gt;
</sourcecode>
          </section>
        </section>
        <section numbered="true" removeInRFC="false" toc="include" pn="section-1.2.2">
          <name slugifiedName="name-examples">Examples</name>
          <section numbered="true" removeInRFC="false" toc="include" pn="section-1.2.2.1">
            <name slugifiedName="name-explicit-ttl-value-create-o">Explicit TTL Value (&lt;create&gt; or &lt;update&gt; Command)</name>
            <sourcecode type="xml" markers="false" pn="section-1.2.2.1-1">
&lt;ttl:ttl for="NS"&gt;3600&lt;/ttl:ttl&gt;
</sourcecode>
          </section>
          <section numbered="true" removeInRFC="false" toc="include" pn="section-1.2.2.2">
            <name slugifiedName="name-explicit-ttl-value-info-pol">Explicit TTL Value (&lt;info&gt; Policy Mode)</name>
            <sourcecode type="xml" markers="false" pn="section-1.2.2.2-1">
&lt;ttl:ttl
  for="NS"
  min="60"
  default="86400"
  max="172800"&gt;3600&lt;/ttl:ttl&gt;
</sourcecode>
          </section>
          <section numbered="true" removeInRFC="false" toc="include" pn="section-1.2.2.3">
            <name slugifiedName="name-empty-value-indicating-defa">Empty Value Indicating Default TTL (&lt;create&gt; or &lt;update&gt; Command, &lt;info&gt; Default Mode)</name>
            <sourcecode type="xml" markers="false" pn="section-1.2.2.3-1">
&lt;ttl:ttl for="NS"/&gt;
</sourcecode>
          </section>
          <section numbered="true" removeInRFC="false" toc="include" pn="section-1.2.2.4">
            <name slugifiedName="name-custom-record-type-create-o">Custom Record Type (&lt;create&gt; or &lt;update&gt; Command, &lt;info&gt; Default Mode)</name>
            <sourcecode type="xml" markers="false" pn="section-1.2.2.4-1">
&lt;ttl:ttl
  for="custom"
  custom="NEWRRTYPE"&gt;3600&lt;/ttl:ttl&gt;
</sourcecode>
          </section>
        </section>
      </section>
    </section>
    <section numbered="true" removeInRFC="false" toc="include" pn="section-2">
      <name slugifiedName="name-epp-command-mapping">EPP Command Mapping</name>
      <section numbered="true" removeInRFC="false" toc="include" pn="section-2.1">
        <name slugifiedName="name-epp-query-commands">EPP Query Commands</name>
        <section anchor="info-command" numbered="true" removeInRFC="false" toc="include" pn="section-2.1.1">
          <name slugifiedName="name-epp-info-command">EPP &lt;info&gt; Command</name>
          <t indent="0" pn="section-2.1.1-1">
	    This extension defines an additional element for EPP
	    <tt>&lt;info&gt;</tt> commands and responses for domain and host
	    objects.</t>
          <t indent="0" pn="section-2.1.1-2">
	    The EPP <tt>&lt;info&gt;</tt> command is extended to support two
	    different modes:</t>
          <ol indent="adaptive" spacing="normal" start="1" type="1" pn="section-2.1.1-3">
            <li pn="section-2.1.1-3.1" derivedCounter="1.">The Default Mode (<xref target="default-mode" format="default" sectionFormat="of" derivedContent="Section 2.1.1.1"/>), which
            requests the inclusion of all non-default TTL values in the
            response; and</li>
            <li pn="section-2.1.1-3.2" derivedCounter="2.">The Policy Mode (<xref target="policy-mode" format="default" sectionFormat="of" derivedContent="Section 2.1.1.2"/>), which requests
            the inclusion of TTL information for all supported DNS record
            types in the response, along with the minimum, default, and maximum
            values for those records.</li>
          </ol>
          <section anchor="default-mode" numbered="true" removeInRFC="false" toc="include" pn="section-2.1.1.1">
            <name slugifiedName="name-default-mode">Default Mode</name>
            <t indent="0" pn="section-2.1.1.1-1">
	      If a server receives an <tt>&lt;info&gt;</tt> command for a
	      domain or host object that includes a <tt>&lt;ttl:info&gt;</tt>
	      element with a "<tt>policy</tt>" attribute that is "<tt>0</tt>"
	      or "<tt>false</tt>", then the EPP response <bcp14>MUST</bcp14>
	      contain <tt>&lt;ttl:ttl&gt;</tt> records for all DNS record
	      types that have non-default TTL values.  These elements
	      <bcp14>MUST NOT</bcp14> have the "<tt>min</tt>",
	      "<tt>default</tt>", and "<tt>max</tt>" attributes.</t>
            <t indent="0" pn="section-2.1.1.1-2">
	      Below is an example domain <tt>&lt;info&gt;</tt> command with a
	      <tt>&lt;ttl:info&gt;</tt> element with a "<tt>policy</tt>"
	      attribute that is "<tt>false</tt>":</t>
            <sourcecode type="xml" markers="false" pn="section-2.1.1.1-3">
C: &lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt;
C: &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt;
C:   &lt;command&gt;
C:     &lt;info&gt;
C:       &lt;domain:info
C:        xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"&gt;
C:         &lt;domain:name&gt;example.com&lt;/domain:name&gt;
C:       &lt;/domain:info&gt;
C:     &lt;/info&gt;
C:     &lt;extension&gt;
C:       &lt;ttl:info
C:         xmlns:ttl="urn:ietf:params:xml:ns:epp:ttl-1.0"
C:         policy="false"/&gt;
C:     &lt;/extension&gt;
C:   &lt;/command&gt;
C: &lt;/epp&gt;
</sourcecode>
            <t indent="0" pn="section-2.1.1.1-4">
	      Below is an example domain <tt>&lt;info&gt;</tt> response to a command with
	      a <tt>&lt;ttl:info&gt;</tt> element with a "<tt>policy</tt>"
	      attribute that is "<tt>false</tt>":</t>
            <sourcecode type="xml" markers="false" pn="section-2.1.1.1-5">
S: &lt;?xml version="1.0" encoding="utf-8" standalone="no"?&gt;
S: &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt;
S:   &lt;response&gt;
S:     &lt;result code="1000"&gt;
S:       &lt;msg&gt;Command completed successfully&lt;/msg&gt;
S:     &lt;/result&gt;
S:     &lt;resData&gt;
S:       &lt;domain:infData
S:         xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"&gt;
S:         &lt;domain:name&gt;example.com&lt;/domain:name&gt;
S:         &lt;domain:roid&gt;EXAMPLE1-REP&lt;/domain:roid&gt;
S:         &lt;domain:status s="ok"/&gt;
S:         &lt;domain:ns&gt;
S:           &lt;domain:hostObj&gt;ns1.example.com&lt;/domain:hostObj&gt;
S:           &lt;domain:hostObj&gt;ns1.example.net&lt;/domain:hostObj&gt;
S:         &lt;/domain:ns&gt;
S:         &lt;domain:clID&gt;ClientX&lt;/domain:clID&gt;
S:         &lt;domain:crID&gt;ClientX&lt;/domain:crID&gt;
S:         &lt;domain:crDate&gt;2023-11-08T10:14:55.0Z&lt;/domain:crDate&gt;
S:         &lt;domain:exDate&gt;2024-11-08T10:14:55.0Z&lt;/domain:exDate&gt;
S:       &lt;/domain:infData&gt;
S:     &lt;/resData&gt;
S:     &lt;extension&gt;
S:       &lt;ttl:infData
S:         xmlns:ttl="urn:ietf:params:xml:ns:epp:ttl-1.0"&gt;
S:         &lt;ttl:ttl for="NS"&gt;172800&lt;/ttl:ttl&gt;
S:         &lt;ttl:ttl for="DS"&gt;300&lt;/ttl:ttl&gt;
S:       &lt;/ttl:infData&gt;
S:       &lt;secDNS:infData
S:         xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1"&gt;
S:         &lt;secDNS:dsData&gt;
S:           &lt;secDNS:keyTag&gt;12345&lt;/secDNS:keyTag&gt;
S:           &lt;secDNS:alg&gt;13&lt;/secDNS:alg&gt;
S:           &lt;secDNS:digestType&gt;2&lt;/secDNS:digestType&gt;
S:           &lt;secDNS:digest&gt;49FD46E6C4B45C55D4AC&lt;/secDNS:digest&gt;
S:         &lt;/secDNS:dsData&gt;
S:       &lt;/secDNS:infData&gt;
S:     &lt;/extension&gt;
S:     &lt;trID&gt;
S:       &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt;
S:       &lt;svTRID&gt;54322-XYZ&lt;/svTRID&gt;
S:     &lt;/trID&gt;
S:   &lt;/response&gt;
S: &lt;/epp&gt;
</sourcecode>
            <t indent="0" pn="section-2.1.1.1-6">
	      Below is an example host <tt>&lt;info&gt;</tt> command with a
	      &lt;ttl:info&gt; element with a "<tt>policy</tt>" attribute that
	      is "<tt>false</tt>":</t>
            <sourcecode type="xml" markers="false" pn="section-2.1.1.1-7">
C: &lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt;
C: &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt;
C:   &lt;command&gt;
C:     &lt;info&gt;
C:       &lt;host:info
C:        xmlns:host="urn:ietf:params:xml:ns:host-1.0"&gt;
C:         &lt;host:name&gt;ns1.example.com&lt;/host:name&gt;
C:       &lt;/host:info&gt;
C:     &lt;/info&gt;
C:     &lt;extension&gt;
C:       &lt;ttl:info
C:         xmlns:ttl="urn:ietf:params:xml:ns:epp:ttl-1.0"
C:         policy="false"/&gt;
C:     &lt;/extension&gt;
C:   &lt;/command&gt;
C: &lt;/epp&gt;
</sourcecode>
            <t indent="0" pn="section-2.1.1.1-8">Below is an example host <tt>&lt;info&gt;</tt> response to a command with a
            &lt;ttl:info&gt; element with a "<tt>policy</tt>" attribute that is
            "<tt>false</tt>":</t>
            <sourcecode type="xml" markers="false" pn="section-2.1.1.1-9">
S: &lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt;
S: &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt;
S:   &lt;response&gt;
S:     &lt;result code="1000"&gt;
S:       &lt;msg&gt;Command completed successfully&lt;/msg&gt;
S:     &lt;/result&gt;
S:     &lt;resData&gt;
S:       &lt;host:infData
S:         xmlns:host="urn:ietf:params:xml:ns:host-1.0"&gt;
S:         &lt;host:name&gt;ns1.example.com&lt;/host:name&gt;
S:         &lt;host:roid&gt;NS1_EXAMPLE1-REP&lt;/host:roid&gt;
S:         &lt;host:status s="ok"/&gt;
S:         &lt;host:addr ip="v4"&gt;192.0.2.2&lt;/host:addr&gt;
S:         &lt;host:addr ip="v6"&gt;2001:db8::8:800:200c:417a&lt;/host:addr&gt;
S:         &lt;host:clID&gt;ClientX&lt;/host:clID&gt;
S:         &lt;host:crID&gt;ClientX&lt;/host:crID&gt;
S:         &lt;host:crDate&gt;2023-11-08T10:14:55.0Z&lt;/host:crDate&gt;
S:       &lt;/host:infData&gt;
S:     &lt;/resData&gt;
S:     &lt;extension&gt;
S:       &lt;ttl:infData
S:         xmlns:ttl="urn:ietf:params:xml:ns:epp:ttl-1.0"&gt;
S:         &lt;ttl:ttl for="A"&gt;172800&lt;/ttl:ttl&gt;
S:         &lt;ttl:ttl for="AAAA"&gt;86400&lt;/ttl:ttl&gt;
S:       &lt;/ttl:infData&gt;
S:     &lt;/extension&gt;
S:     &lt;trID&gt;
S:       &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt;
S:       &lt;svTRID&gt;54322-XYZ&lt;/svTRID&gt;
S:     &lt;/trID&gt;
S:   &lt;/response&gt;
S: &lt;/epp&gt;
</sourcecode>
          </section>
          <section anchor="policy-mode" numbered="true" removeInRFC="false" toc="include" pn="section-2.1.1.2">
            <name slugifiedName="name-policy-mode">Policy Mode</name>
            <t indent="0" pn="section-2.1.1.2-1">
	      If a server receives an <tt>&lt;info&gt;</tt> command for a
	      domain or host object that includes a <tt>&lt;ttl:info&gt;</tt>
	      element with a "<tt>policy</tt>" attribute that is "<tt>1</tt>" or
	      "<tt>true</tt>", then the EPP response <bcp14>MUST</bcp14>
	      contain <tt>&lt;ttl:ttl&gt;</tt> records for all supported DNS
	      record types, irrespective of whether those record types are
	      actually in use by the object in question.  These elements
	      <bcp14>MUST</bcp14> have the "<tt>min</tt>", "<tt>default</tt>",
	      and "<tt>max</tt>" attributes.</t>
            <t indent="0" pn="section-2.1.1.2-2">
	      Below is an example domain <tt>&lt;info&gt;</tt> command requesting the
	      server policies:</t>
            <sourcecode type="xml" markers="false" pn="section-2.1.1.2-3">
C: &lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt;
C: &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt;
C:   &lt;command&gt;
C:     &lt;info&gt;
C:       &lt;domain:info
C:        xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"&gt;
C:         &lt;domain:name&gt;example.com&lt;/domain:name&gt;
C:       &lt;/domain:info&gt;
C:     &lt;/info&gt;
C:     &lt;extension&gt;
C:       &lt;ttl:info
C:         xmlns:ttl="urn:ietf:params:xml:ns:epp:ttl-1.0"
C:         policy="true"/&gt;
C:     &lt;/extension&gt;
C:   &lt;/command&gt;
C: &lt;/epp&gt;
</sourcecode>
            <t indent="0" pn="section-2.1.1.2-4">Below is an example domain <tt>&lt;info&gt;</tt> response providing the server policies:</t>
            <sourcecode type="xml" markers="false" pn="section-2.1.1.2-5">
S: &lt;?xml version="1.0" encoding="utf-8" standalone="no"?&gt;
S: &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt;
S:   &lt;response&gt;
S:     &lt;result code="1000"&gt;
S:       &lt;msg&gt;Command completed successfully&lt;/msg&gt;
S:     &lt;/result&gt;
S:     &lt;resData&gt;
S:       &lt;domain:infData
S:         xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"&gt;
S:         &lt;domain:name&gt;example.com&lt;/domain:name&gt;
S:         &lt;domain:roid&gt;EXAMPLE1-REP&lt;/domain:roid&gt;
S:         &lt;domain:status s="ok"/&gt;
S:         &lt;domain:ns&gt;
S:           &lt;domain:hostObj&gt;ns1.example.com&lt;/domain:hostObj&gt;
S:           &lt;domain:hostObj&gt;ns1.example.net&lt;/domain:hostObj&gt;
S:         &lt;/domain:ns&gt;
S:         &lt;domain:clID&gt;ClientX&lt;/domain:clID&gt;
S:         &lt;domain:crID&gt;ClientX&lt;/domain:crID&gt;
S:         &lt;domain:crDate&gt;2023-11-08T10:14:55.0Z&lt;/domain:crDate&gt;
S:         &lt;domain:exDate&gt;2024-11-08T10:14:55.0Z&lt;/domain:exDate&gt;
S:       &lt;/domain:infData&gt;
S:     &lt;/resData&gt;
S:     &lt;extension&gt;
S:       &lt;ttl:infData
S:         xmlns:ttl="urn:ietf:params:xml:ns:epp:ttl-1.0"&gt;
S:         &lt;ttl:ttl for="NS"
S:           min="3600"
S:           default="86400"
S:           max="172800"&gt;172800&lt;/ttl:ttl&gt;
S:         &lt;ttl:ttl for="DS"
S:           min="60"
S:           default="86400"
S:           max="172800"&gt;300&lt;/ttl:ttl&gt;
S:       &lt;/ttl:infData&gt;
S:       &lt;secDNS:infData
S:         xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1"&gt;
S:         &lt;secDNS:dsData&gt;
S:           &lt;secDNS:keyTag&gt;12345&lt;/secDNS:keyTag&gt;
S:           &lt;secDNS:alg&gt;13&lt;/secDNS:alg&gt;
S:           &lt;secDNS:digestType&gt;2&lt;/secDNS:digestType&gt;
S:           &lt;secDNS:digest&gt;49FD46E6C4B45C55D4AC&lt;/secDNS:digest&gt;
S:         &lt;/secDNS:dsData&gt;
S:       &lt;/secDNS:infData&gt;
S:     &lt;/extension&gt;
S:     &lt;trID&gt;
S:       &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt;
S:       &lt;svTRID&gt;54322-XYZ&lt;/svTRID&gt;
S:     &lt;/trID&gt;
S:   &lt;/response&gt;
S: &lt;/epp&gt;
</sourcecode>
            <t indent="0" pn="section-2.1.1.2-6">Below is an example host <tt>&lt;info&gt;</tt> command requesting the server policies:</t>
            <sourcecode type="xml" markers="false" pn="section-2.1.1.2-7">
C: &lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt;
C: &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt;
C:   &lt;command&gt;
C:     &lt;info&gt;
C:       &lt;host:info
C:        xmlns:host="urn:ietf:params:xml:ns:host-1.0"&gt;
C:         &lt;host:name&gt;ns1.example.com&lt;/host:name&gt;
C:       &lt;/host:info&gt;
C:     &lt;/info&gt;
C:     &lt;extension&gt;
C:       &lt;ttl:info
C:         xmlns:ttl="urn:ietf:params:xml:ns:epp:ttl-1.0"
C:         policy="true"/&gt;
C:     &lt;/extension&gt;
C:   &lt;/command&gt;
C: &lt;/epp&gt;
</sourcecode>
            <t indent="0" pn="section-2.1.1.2-8">Below is an example host <tt>&lt;info&gt;</tt> response providing the server policies:</t>
            <sourcecode type="xml" markers="false" pn="section-2.1.1.2-9">
S: &lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt;
S: &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt;
S:   &lt;response&gt;
S:     &lt;result code="1000"&gt;
S:       &lt;msg&gt;Command completed successfully&lt;/msg&gt;
S:     &lt;/result&gt;
S:     &lt;resData&gt;
S:       &lt;host:infData
S:         xmlns:host="urn:ietf:params:xml:ns:host-1.0"&gt;
S:         &lt;host:name&gt;ns1.example.com&lt;/host:name&gt;
S:         &lt;host:roid&gt;NS1_EXAMPLE1-REP&lt;/host:roid&gt;
S:         &lt;host:status s="ok"/&gt;
S:         &lt;host:addr ip="v4"&gt;192.0.2.2&lt;/host:addr&gt;
S:         &lt;host:addr ip="v6"&gt;2001:db8::8:800:200c:417a&lt;/host:addr&gt;
S:         &lt;host:clID&gt;ClientX&lt;/host:clID&gt;
S:         &lt;host:crID&gt;ClientX&lt;/host:crID&gt;
S:         &lt;host:crDate&gt;2023-11-08T10:14:55.0Z&lt;/host:crDate&gt;
S:       &lt;/host:infData&gt;
S:     &lt;/resData&gt;
S:     &lt;extension&gt;
S:       &lt;ttl:infData
S:         xmlns:ttl="urn:ietf:params:xml:ns:epp:ttl-1.0"&gt;
S:         &lt;ttl:ttl for="A"
S:           min="3600"
S:           default="86400"
S:           max="172800"&gt;172800&lt;/ttl:ttl&gt;
S:         &lt;ttl:ttl for="AAAA"
S:           min="3600"
S:           default="86400"
S:           max="172800"&gt;86400&lt;/ttl:ttl&gt;
S:       &lt;/ttl:infData&gt;
S:     &lt;/extension&gt;
S:     &lt;trID&gt;
S:       &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt;
S:       &lt;svTRID&gt;54322-XYZ&lt;/svTRID&gt;
S:     &lt;/trID&gt;
S:   &lt;/response&gt;
S: &lt;/epp&gt;
</sourcecode>
          </section>
        </section>
      </section>
      <section numbered="true" removeInRFC="false" toc="include" pn="section-2.2">
        <name slugifiedName="name-epp-transform-commands">EPP Transform Commands</name>
        <section numbered="true" removeInRFC="false" toc="include" pn="section-2.2.1">
          <name slugifiedName="name-epp-create-command">EPP &lt;create&gt; Command</name>
          <t indent="0" pn="section-2.2.1-1">
	    This extension defines an additional element for EPP
	    <tt>&lt;create&gt;</tt> commands for domain and host objects.</t>
          <t indent="0" pn="section-2.2.1-2">
	    The <tt>&lt;command&gt;</tt> element of the
	    <tt>&lt;create&gt;</tt> command <bcp14>MAY</bcp14> contain an
	    <tt>&lt;extension&gt;</tt> element that <bcp14>MAY</bcp14>
	    contain a <tt>&lt;ttl:create&gt;</tt> element.  This element
	    <bcp14>MUST</bcp14> contain one or more <tt>&lt;ttl:ttl&gt;</tt>
	    records as described in <xref target="extension-elements" format="default" sectionFormat="of" derivedContent="Section 1.2"/>.</t>
          <t indent="0" pn="section-2.2.1-3">If an EPP server receives a <tt>&lt;create&gt;</tt> command
      containing a TTL value that is outside the server's permitted range,
      it <bcp14>MUST</bcp14> reject the command with a 2004
      "Parameter value range error" response.</t>
          <t indent="0" pn="section-2.2.1-4">
	    Below is an example domain <tt>&lt;create&gt;</tt> command:</t>
          <sourcecode type="xml" markers="false" pn="section-2.2.1-5">
C: &lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt;
C: &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt;
C:   &lt;command&gt;
C:     &lt;create&gt;
C:       &lt;domain:create
C:         xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"&gt;
C:         &lt;domain:name&gt;example.com&lt;/domain:name&gt;
C:         &lt;domain:period unit="y"&gt;1&lt;/domain:period&gt;
C:         &lt;domain:ns&gt;
C:           &lt;domain:hostObj&gt;ns1.example.com&lt;/domain:hostObj&gt;
C:           &lt;domain:hostObj&gt;ns1.example.net&lt;/domain:hostObj&gt;
C:         &lt;/domain:ns&gt;
C:         &lt;domain:authInfo&gt;
C:           &lt;domain:pw/&gt;
C:         &lt;/domain:authInfo&gt;
C:       &lt;/domain:create&gt;
C:     &lt;/create&gt;
C:     &lt;extension&gt;
C:       &lt;ttl:create
C:         xmlns:ttl="urn:ietf:params:xml:ns:epp:ttl-1.0"&gt;
C:         &lt;ttl:ttl for="NS"&gt;172800&lt;/ttl:ttl&gt;
C:         &lt;ttl:ttl for="DS"&gt;300&lt;/ttl:ttl&gt;
C:       &lt;/ttl:create&gt;
C:       &lt;secDNS:create
C:         xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1"&gt;
C:         &lt;secDNS:dsData&gt;
C:           &lt;secDNS:keyTag&gt;12345&lt;/secDNS:keyTag&gt;
C:           &lt;secDNS:alg&gt;13&lt;/secDNS:alg&gt;
C:           &lt;secDNS:digestType&gt;2&lt;/secDNS:digestType&gt;
C:           &lt;secDNS:digest&gt;49FD46E6C4B45C55D4AC&lt;/secDNS:digest&gt;
C:         &lt;/secDNS:dsData&gt;
C:       &lt;/secDNS:create&gt;
C:     &lt;/extension&gt;
C:     &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt;
C:   &lt;/command&gt;
C: &lt;/epp&gt;
</sourcecode>
          <t indent="0" pn="section-2.2.1-6">Below is an example host <tt>&lt;create&gt;</tt> command:</t>
          <sourcecode type="xml" markers="false" pn="section-2.2.1-7">
C: &lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt;
C: &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt;
C:   &lt;command&gt;
C:     &lt;create&gt;
C:       &lt;host:create
C:         xmlns:host="urn:ietf:params:xml:ns:host-1.0"&gt;
C:         &lt;host:name&gt;ns1.example.com&lt;/host:name&gt;
C:         &lt;host:addr ip="v4"&gt;192.0.2.2&lt;/host:addr&gt;
C:         &lt;host:addr ip="v6"&gt;2001:db8::8:800:200c:417a&lt;/host:addr&gt;
C:       &lt;/host:create&gt;
C:     &lt;/create&gt;
C:     &lt;extension&gt;
C:       &lt;ttl:create
C:         xmlns:ttl="urn:ietf:params:xml:ns:epp:ttl-1.0"&gt;
C:         &lt;ttl:ttl for="A"/&gt;
C:         &lt;ttl:ttl for="AAAA"&gt;86400&lt;/ttl:ttl&gt;
C:       &lt;/ttl:create&gt;
C:     &lt;/extension&gt;
C:     &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt;
C:   &lt;/command&gt;
C: &lt;/epp&gt;
</sourcecode>
        </section>
        <section numbered="true" removeInRFC="false" toc="include" pn="section-2.2.2">
          <name slugifiedName="name-epp-update-command">EPP &lt;update&gt; Command</name>
          <t indent="0" pn="section-2.2.2-1">
	    This extension defines an additional element for EPP
	    <tt>&lt;update&gt;</tt> commands for domain and host objects.</t>
          <t indent="0" pn="section-2.2.2-2">
	    The <tt>&lt;command&gt;</tt> element of the
	    <tt>&lt;update&gt;</tt> command <bcp14>MAY</bcp14> contain an
	    <tt>&lt;extension&gt;</tt> element that <bcp14>MAY</bcp14>
	    contain a <tt>&lt;ttl:update&gt;</tt> element.  This element
	    <bcp14>MUST</bcp14> contain one or more <tt>&lt;ttl:ttl&gt;</tt>
	    records as described in <xref target="extension-elements" format="default" sectionFormat="of" derivedContent="Section 1.2"/>.</t>
          <t indent="0" pn="section-2.2.2-3">
  If an EPP server receives an <tt>&lt;update&gt;</tt> command
  containing a TTL value that is outside the server's permitted
  range, it <bcp14>MUST</bcp14> reject the command with a
  2004 "Parameter value range error" response.</t>
          <t indent="0" pn="section-2.2.2-4">
	    Below is an example domain <tt>&lt;update&gt;</tt> command:</t>
          <sourcecode type="xml" markers="false" pn="section-2.2.2-5">
C: &lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt;
C: &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt;
C:   &lt;command&gt;
C:     &lt;update&gt;
C:       &lt;domain:update
C:         xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"&gt;
C:         &lt;domain:name&gt;example.com&lt;/domain:name&gt;
C:       &lt;/domain:update&gt;
C:     &lt;/update&gt;
C:     &lt;extension&gt;
C:       &lt;ttl:update
C:         xmlns:ttl="urn:ietf:params:xml:ns:epp:ttl-1.0"&gt;
C:         &lt;ttl:ttl for="NS"/&gt;
C:         &lt;ttl:ttl for="custom"
C:           custom="DELEG"/&gt;
C:         &lt;ttl:ttl for="DS"&gt;86400&lt;/ttl:ttl&gt;
C:       &lt;/ttl:update&gt;
C:     &lt;/extension&gt;
C:     &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt;
C:   &lt;/command&gt;
C: &lt;/epp&gt;
</sourcecode>
          <t indent="0" pn="section-2.2.2-6">Below is an example host <tt>&lt;update&gt;</tt> command:</t>
          <sourcecode type="xml" markers="false" pn="section-2.2.2-7">
C: &lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt;
C: &lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt;
C:   &lt;command&gt;
C:     &lt;update&gt;
C:       &lt;host:update
C:         xmlns:host="urn:ietf:params:xml:ns:host-1.0"&gt;
C:         &lt;host:name&gt;ns1.example.com&lt;/host:name&gt;
C:       &lt;/host:update&gt;
C:     &lt;/update&gt;
C:     &lt;extension&gt;
C:       &lt;ttl:update
C:         xmlns:ttl="urn:ietf:params:xml:ns:epp:ttl-1.0"&gt;
C:         &lt;ttl:ttl for="A"&gt;86400&lt;/ttl:ttl&gt;
C:         &lt;ttl:ttl for="AAAA"&gt;3600&lt;/ttl:ttl&gt;
C:       &lt;/ttl:update&gt;
C:     &lt;/extension&gt;
C:     &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt;
C:   &lt;/command&gt;
C: &lt;/epp&gt;
</sourcecode>
        </section>
      </section>
    </section>
    <section anchor="server-processing" numbered="true" removeInRFC="false" toc="include" pn="section-3">
      <name slugifiedName="name-server-processing-of-ttl-va">Server Processing of TTL Values</name>
      <section anchor="permitted-types" numbered="true" removeInRFC="false" toc="include" pn="section-3.1">
        <name slugifiedName="name-permitted-record-types">Permitted Record Types</name>
        <t indent="0" pn="section-3.1-1">
	  EPP servers <bcp14>MAY</bcp14> restrict the supported DNS record
	  types.  For example, a server <bcp14>MAY</bcp14> allow clients to
	  specify TTL values for <tt>DS</tt> records only.</t>
        <t indent="0" pn="section-3.1-2">
	  A server that receives a <tt>&lt;create&gt;</tt> or
	  <tt>&lt;update&gt;</tt> command that includes a restricted record
	  type <bcp14>MUST</bcp14> respond with a 2306 "Parameter value
	  policy" error.</t>
        <t indent="0" pn="section-3.1-3">
	  Clients can discover the DNS record types for which an EPP server
	  permits TTL values to be changed by performing a Policy Mode
	  <tt>&lt;info&gt;</tt> command, as outlined in <xref target="policy-mode" format="default" sectionFormat="of" derivedContent="Section 2.1.1.2"/>.</t>
      </section>
      <section anchor="using_ttl_values" numbered="true" removeInRFC="false" toc="include" pn="section-3.2">
        <name slugifiedName="name-use-of-ttl-values-in-delega">Use of TTL Values in Delegation Records</name>
        <t indent="0" pn="section-3.2-1">
	  EPP servers that implement this extension <bcp14>SHOULD</bcp14> use
	  the values provided by EPP clients for the TTL values of records
	  published in the DNS for domain and (if supported) host objects.
	  Server operators <bcp14>MAY</bcp14> disregard these values in order
	  to address security and stability issues, as described in <xref target="operational-considerations" format="default" sectionFormat="of" derivedContent="Section 5"/> and <xref target="security-considerations" format="default" sectionFormat="of" derivedContent="Section 6"/>.</t>
        <t indent="0" pn="section-3.2-2">
	  EPP servers that use the host attribute model
	  <bcp14>SHOULD</bcp14> use any <tt>NS</tt>, <tt>A</tt>, and/or
	  <tt>AAAA</tt> TTL values specified for the domain object when
	  publishing <tt>NS</tt>, <tt>A</tt>, and/or <tt>AAAA</tt> records
	  derived from host attributes.</t>
      </section>
    </section>
    <section anchor="oob-changes" numbered="true" removeInRFC="false" toc="include" pn="section-4">
      <name slugifiedName="name-out-of-band-changes-to-ttl-">Out-of-Band Changes to TTL Values</name>
      <t indent="0" pn="section-4-1">In order to address operational or security issues, EPP server
      operators <bcp14>MAY</bcp14> make changes to TTL values out-of-band
      (that is, not in response to an <tt>&lt;update&gt;</tt> command received
      from the sponsoring client).
      </t>
      <t indent="0" pn="section-4-2">
	Server operators <bcp14>MAY</bcp14> also implement automatic reset of
	TTL values, so that they revert to the default value a certain amount
	of time after an update has been made.
      </t>
      <t indent="0" pn="section-4-3">
	If a TTL value is changed out-of-band, EPP server operators
	<bcp14>MAY</bcp14> notify the sponsoring client using the EPP Change
	Poll Extension <xref target="RFC8590" format="default" sectionFormat="of" derivedContent="RFC8590"/>, which provides a
	generalized method for EPP servers to notify clients of changes to
	objects under their sponsorship.
      </t>
    </section>
    <section anchor="operational-considerations" numbered="true" removeInRFC="false" toc="include" pn="section-5">
      <name slugifiedName="name-operational-considerations">Operational Considerations</name>
      <section numbered="true" removeInRFC="false" toc="include" pn="section-5.1">
        <name slugifiedName="name-operational-impact-of-ttl-v">Operational Impact of TTL Values</name>
        <t indent="0" pn="section-5.1-1">
	  Registry operators must consider the balance between registrants'
	  desire for changes to domains to be visible in the DNS quickly, and
	  the increased DNS query traffic that short TTLs can bring.</t>
        <t indent="0" pn="section-5.1-2">
	  Registry operators <bcp14>SHOULD</bcp14> implement limits on the
	  maximum and minimum accepted TTL values that are narrower than the
	  values permitted in the XML schema in <xref target="formal-syntax" format="default" sectionFormat="of" derivedContent="Section 8"/>
	  (which were chosen to allow any TTL permitted in DNS records). This
	  is in order to prevent scenarios where an excessively high or low
	  TTL causes operational issues on either side of the zone cut.</t>
        <t indent="0" pn="section-5.1-3"><xref target="oob-changes" format="default" sectionFormat="of" derivedContent="Section 4"/> describes how server operators
        <bcp14>MAY</bcp14> unilaterally change TTL values in order to address
        operational or security issues, or only permit changes for limited
        time periods (after which TTLs revert to the default).</t>
      </section>
      <section numbered="true" removeInRFC="false" toc="include" pn="section-5.2">
        <name slugifiedName="name-when-ttl-values-should-be-c">When TTL Values Should Be Changed</name>
        <t indent="0" pn="section-5.2-1">
	  A common operational mistake is changing the DNS record TTLs during
	  or after the planned change to the records themselves.  This arises
	  due to a misunderstanding about how TTLs work.</t>
        <t indent="0" pn="section-5.2-2">
	  It is <bcp14>RECOMMENDED</bcp14> that guidance be provided to users
	  so they are aware that changes to a TTL are only effective in
	  shortening transition periods if implemented a period of time (at
	  least equal to the current TTL) <em>before</em> the planned change.
	  The latency between receipt of the <tt>&lt;update&gt;</tt> command
	  and the actual publication of the changes in the DNS should also be
	  taken into consideration in this calculation.</t>
      </section>
      <section numbered="true" removeInRFC="false" toc="include" pn="section-5.3">
        <name slugifiedName="name-changes-to-server-policy">Changes to Server Policy</name>
        <t indent="0" pn="section-5.3-1">
	  Registry operators may change their policies relating to TTL values
	  from time to time.  Previously configured TTL values may
	  consequently fall outside a newly applied policy.  This document
	  places no obligation on EPP server operators in respect of these
	  values, and server operators may, as part of a policy change, change
	  the TTL values specified by clients for domain and host objects.
	  <xref target="oob-changes" format="default" sectionFormat="of" derivedContent="Section 4"/> describes how such out-of-band changes
	  should be carried out.</t>
      </section>
    </section>
    <section anchor="security-considerations" numbered="true" removeInRFC="false" toc="include" pn="section-6">
      <name slugifiedName="name-security-considerations">Security Considerations</name>
      <section numbered="true" removeInRFC="false" toc="include" pn="section-6.1">
        <name slugifiedName="name-fast-flux-dns">Fast Flux DNS</name>
        <t indent="0" pn="section-6.1-1">
	  Some malicious actors use a technique called "fast flux DNS" <xref target="SAC-025" format="default" sectionFormat="of" derivedContent="SAC-025"/> to rapidly change the DNS configuration for a
	  zone in order to evade takedown and law enforcement activity.
	  Server operators should take this into consideration when setting
	  the lower limit on TTL values, since a short TTL on delegations may
	  enhance the effectiveness of fast flux techniques on evasion.</t>
        <t indent="0" pn="section-6.1-2">
	  Client implementations that provide an interface for customers to
	  configure TTL values for domain names should consider implementing
	  controls to deter and mitigate abusive behavior, such as those
	  outlined in the "Current and Possible Mitigation Alternatives"
	  section of <xref target="SAC-025" format="default" sectionFormat="of" derivedContent="SAC-025"/>.</t>
      </section>
      <section numbered="true" removeInRFC="false" toc="include" pn="section-6.2">
        <name slugifiedName="name-compromised-user-accounts">Compromised User Accounts</name>
        <t indent="0" pn="section-6.2-1">
	  An attacker who obtains access to a customer account at a domain
	  registrar that supports this extension could make unauthorized
	  changes to the <tt>NS</tt> and/or glue records for a domain, and
	  then increase the associated TTLs so that the changes persist in
	  caches for a long time after the attack has been detected.</t>
        <t indent="0" pn="section-6.2-2">
	  Client implementations that provide an interface for customers to
	  configure TTL values for domain names should consider implementing
	  upper limits in order to reduce the impact of account compromise, in
	  addition to best practices relating to credential management,
	  multi-factor authentication, risk-based access control, and so on.</t>
      </section>
    </section>
    <section anchor="IANA" numbered="true" removeInRFC="false" toc="include" pn="section-7">
      <name slugifiedName="name-iana-considerations">IANA Considerations</name>
      <section numbered="true" removeInRFC="false" toc="include" pn="section-7.1">
        <name slugifiedName="name-xml-namespace">XML Namespace</name>
        <t indent="0" pn="section-7.1-1">This document uses URNs to describe XML namespaces and XML schemas
        conforming to a registry mechanism described in <xref target="RFC3688" format="default" sectionFormat="of" derivedContent="RFC3688"/>.  The following URI assignments have been made by
        IANA:</t>
        <t indent="0" pn="section-7.1-2">Registration for the TTL namespace:</t>
        <dl spacing="compact" newline="false" indent="3" pn="section-7.1-3">
          <dt pn="section-7.1-3.1">URI:</dt>
          <dd pn="section-7.1-3.2">
            <tt>urn:ietf:params:xml:ns:epp:ttl-1.0</tt></dd>
          <dt pn="section-7.1-3.3">Registrant Contact:</dt>
          <dd pn="section-7.1-3.4">IESG</dd>
          <dt pn="section-7.1-3.5">XML:</dt>
          <dd pn="section-7.1-3.6">None. Namespace URIs do not represent an XML specification.</dd>
        </dl>
        <t indent="0" pn="section-7.1-4">Registration for the TTL XML schema:</t>
        <dl spacing="compact" newline="false" indent="3" pn="section-7.1-5">
          <dt pn="section-7.1-5.1">URI:</dt>
          <dd pn="section-7.1-5.2">
            <tt>urn:ietf:params:xml:schema:epp:ttl-1.0</tt></dd>
          <dt pn="section-7.1-5.3">Registrant Contact:</dt>
          <dd pn="section-7.1-5.4">IESG</dd>
          <dt pn="section-7.1-5.5">XML:</dt>
          <dd pn="section-7.1-5.6">See <xref target="formal-syntax" format="default" sectionFormat="of" derivedContent="Section 8"/> of this
          document.</dd>
        </dl>
      </section>
      <section numbered="true" removeInRFC="false" toc="include" pn="section-7.2">
        <name slugifiedName="name-epp-extension-registry">EPP Extension Registry</name>
        <t indent="0" pn="section-7.2-1">The EPP extension described in this document has been registered by
        IANA in the "Extensions for the Extensible Provisioning Protocol
        (EPP)" registry described in <xref target="RFC7451" format="default" sectionFormat="of" derivedContent="RFC7451"/>.  The details of
        the registration are as follows:</t>
        <dl spacing="compact" newline="false" indent="3" pn="section-7.2-2">
          <dt pn="section-7.2-2.1">Name of Extension:</dt>
          <dd pn="section-7.2-2.2">Extensible Provisioning Protocol (EPP) Mapping for DNS Time-to-Live (TTL) Values</dd>
          <dt pn="section-7.2-2.3">Document Status:</dt>
          <dd pn="section-7.2-2.4">Standards Track</dd>
          <dt pn="section-7.2-2.5">Reference:</dt>
          <dd pn="section-7.2-2.6">RFC 9803</dd>
          <dt pn="section-7.2-2.7">Registrant:</dt>
          <dd pn="section-7.2-2.8">IESG</dd>
          <dt pn="section-7.2-2.9">TLDs:</dt>
          <dd pn="section-7.2-2.10">Any</dd>
          <dt pn="section-7.2-2.11">IPR Disclosure:</dt>
          <dd pn="section-7.2-2.12">None</dd>
          <dt pn="section-7.2-2.13">Status:</dt>
          <dd pn="section-7.2-2.14">Active</dd>
          <dt pn="section-7.2-2.15">Notes:</dt>
          <dd pn="section-7.2-2.16">None</dd>
        </dl>
      </section>
    </section>
    <section anchor="formal-syntax" numbered="true" removeInRFC="false" toc="include" pn="section-8">
      <name slugifiedName="name-formal-syntax">Formal Syntax</name>
      <t indent="0" pn="section-8-1">
	The formal syntax presented here is a complete schema representation
	of the extension suitable for automated validation of EPP XML
	instances.</t>
      <sourcecode type="xml" markers="false" pn="section-8-2">
&lt;?xml version="1.0" encoding="UTF-8"?&gt;
&lt;schema
  xmlns="http://www.w3.org/2001/XMLSchema"
  targetNamespace="urn:ietf:params:xml:ns:epp:ttl-1.0"
  xmlns:ttl="urn:ietf:params:xml:ns:epp:ttl-1.0"
  elementFormDefault="qualified"&gt;
  &lt;annotation&gt;
    &lt;documentation&gt;
      Extensible Provisioning Protocol v1.0 extension
      schema for Time-to-Live (TTL) Values for domain
      and host objects.
    &lt;/documentation&gt;
  &lt;/annotation&gt;

  &lt;element name="info"&gt;
    &lt;complexType&gt;
      &lt;attribute name="policy" type="boolean" default="false"/&gt;
    &lt;/complexType&gt;
  &lt;/element&gt;

  &lt;!--
    &lt;ttl&gt; elements can appear in &lt;create&gt; and
    &lt;update&gt; commands, and &lt;info&gt; responses
  --&gt;

  &lt;element name="create" type="ttl:commandContainer"&gt;
    &lt;unique name="uniqueRRTypeForCreate"&gt;
      &lt;selector xpath="ttl:ttl"/&gt;
      &lt;field xpath="@for"/&gt;
    &lt;/unique&gt;
  &lt;/element&gt;

  &lt;element name="update" type="ttl:commandContainer"&gt;
    &lt;unique name="uniqueRRTypeForUpdate"&gt;
      &lt;selector xpath="ttl:ttl"/&gt;
      &lt;field xpath="@for"/&gt;
    &lt;/unique&gt;
  &lt;/element&gt;

  &lt;element name="infData" type="ttl:responseContainer"&gt;
    &lt;unique name="uniqueRRTypeForInfo"&gt;
      &lt;selector xpath="ttl:ttl"/&gt;
      &lt;field xpath="@for"/&gt;
    &lt;/unique&gt;
  &lt;/element&gt;

  &lt;complexType name="commandContainer"&gt;
    &lt;sequence&gt;
      &lt;element
        name="ttl"
        type="ttl:commandTTLType"
        minOccurs="1"
        maxOccurs="unbounded"/&gt;
    &lt;/sequence&gt;
  &lt;/complexType&gt;

  &lt;complexType name="responseContainer"&gt;
    &lt;sequence&gt;
      &lt;element
        name="ttl"
        type="ttl:responseTTLType"
        minOccurs="1"
        maxOccurs="unbounded"/&gt;
    &lt;/sequence&gt;
  &lt;/complexType&gt;

  &lt;complexType name="commandTTLType"&gt;
    &lt;simpleContent&gt;
      &lt;extension base="ttl:ttlOrNull"&gt;
        &lt;attribute
          name="for"
          type="ttl:rrType"
          use="required"/&gt;

        &lt;attribute
          name="custom"
          type="ttl:customRRType"/&gt;
      &lt;/extension&gt;
    &lt;/simpleContent&gt;
  &lt;/complexType&gt;

  &lt;complexType name="responseTTLType"&gt;
    &lt;simpleContent&gt;
      &lt;extension base="ttl:ttlOrNull"&gt;
        &lt;attribute
          name="for"
          type="ttl:rrType"
          use="required"/&gt;

        &lt;attribute
          name="custom"
          type="ttl:customRRType"/&gt;

        &lt;attribute
          name="min"
          type="ttl:ttlValue"/&gt;

        &lt;attribute
          name="default"
          type="ttl:ttlValue"/&gt;

        &lt;attribute
          name="max"
          type="ttl:ttlValue"/&gt;
      &lt;/extension&gt;
    &lt;/simpleContent&gt;
  &lt;/complexType&gt;

  &lt;!--
    union type allowing the element to either contain
    nothing or a TTL value
  --&gt;
  &lt;simpleType name="ttlOrNull"&gt;
    &lt;union
      memberTypes="ttl:emptyValue ttl:ttlValue"/&gt;
  &lt;/simpleType&gt;

  &lt;!-- empty value type --&gt;
  &lt;simpleType name="emptyValue"&gt;
    &lt;restriction base="token"&gt;
      &lt;length value="0"/&gt;
    &lt;/restriction&gt;
  &lt;/simpleType&gt;

  &lt;!-- TTL value type --&gt;
  &lt;simpleType name="ttlValue"&gt;
    &lt;restriction base="nonNegativeInteger"&gt;
      &lt;minInclusive value="0"/&gt;
      &lt;maxInclusive value="2147483647"/&gt;
    &lt;/restriction&gt;
  &lt;/simpleType&gt;

  &lt;!-- resource record mnemonic type --&gt;
  &lt;simpleType name="rrType"&gt;
    &lt;restriction base="token"&gt;
      &lt;enumeration value="NS" /&gt;
      &lt;enumeration value="DS" /&gt;
      &lt;enumeration value="DNAME" /&gt;
      &lt;enumeration value="A" /&gt;
      &lt;enumeration value="AAAA" /&gt;
      &lt;enumeration value="custom" /&gt;
    &lt;/restriction&gt;
  &lt;/simpleType&gt;

  &lt;!-- custom resource record type --&gt;
  &lt;simpleType name="customRRType"&gt;
    &lt;restriction base="token"&gt;
      &lt;pattern value="A|[A-Z][A-Z0-9\-]*[A-Z0-9]"/&gt;
    &lt;/restriction&gt;
  &lt;/simpleType&gt;
&lt;/schema&gt;
</sourcecode>
    </section>
  </middle>
  <back>
    <references pn="section-9">
      <name slugifiedName="name-references">References</name>
      <references pn="section-9.1">
        <name slugifiedName="name-normative-references">Normative References</name>
        <reference anchor="IANA-RRTYPES" target="https://www.iana.org/assignments/dns-parameters" quoteTitle="true" derivedAnchor="IANA-RRTYPES">
          <front>
            <title>Resource Record (RR) TYPEs</title>
            <author>
              <organization showOnFrontPage="true">IANA</organization>
            </author>
          </front>
        </reference>
        <reference anchor="RFC2119" target="https://www.rfc-editor.org/info/rfc2119" quoteTitle="true" derivedAnchor="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 indent="0">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="RFC3688" target="https://www.rfc-editor.org/info/rfc3688" quoteTitle="true" derivedAnchor="RFC3688">
          <front>
            <title>The IETF XML Registry</title>
            <author fullname="M. Mealling" initials="M." surname="Mealling"/>
            <date month="January" year="2004"/>
            <abstract>
              <t indent="0">This document describes an IANA maintained registry for IETF standards which use Extensible Markup Language (XML) related items such as Namespaces, Document Type Declarations (DTDs), Schemas, and Resource Description Framework (RDF) Schemas.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="81"/>
          <seriesInfo name="RFC" value="3688"/>
          <seriesInfo name="DOI" value="10.17487/RFC3688"/>
        </reference>
        <reference anchor="RFC5731" target="https://www.rfc-editor.org/info/rfc5731" quoteTitle="true" derivedAnchor="RFC5731">
          <front>
            <title>Extensible Provisioning Protocol (EPP) Domain Name Mapping</title>
            <author fullname="S. Hollenbeck" initials="S." surname="Hollenbeck"/>
            <date month="August" year="2009"/>
            <abstract>
              <t indent="0">This document describes an Extensible Provisioning Protocol (EPP) mapping for the provisioning and management of Internet domain names stored in a shared central repository. Specified in XML, the mapping defines EPP command syntax and semantics as applied to domain names. This document obsoletes RFC 4931. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="69"/>
          <seriesInfo name="RFC" value="5731"/>
          <seriesInfo name="DOI" value="10.17487/RFC5731"/>
        </reference>
        <reference anchor="RFC5732" target="https://www.rfc-editor.org/info/rfc5732" quoteTitle="true" derivedAnchor="RFC5732">
          <front>
            <title>Extensible Provisioning Protocol (EPP) Host Mapping</title>
            <author fullname="S. Hollenbeck" initials="S." surname="Hollenbeck"/>
            <date month="August" year="2009"/>
            <abstract>
              <t indent="0">This document describes an Extensible Provisioning Protocol (EPP) mapping for the provisioning and management of Internet host names stored in a shared central repository. Specified in XML, the mapping defines EPP command syntax and semantics as applied to host names. This document obsoletes RFC 4932. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="69"/>
          <seriesInfo name="RFC" value="5732"/>
          <seriesInfo name="DOI" value="10.17487/RFC5732"/>
        </reference>
        <reference anchor="RFC5910" target="https://www.rfc-editor.org/info/rfc5910" quoteTitle="true" derivedAnchor="RFC5910">
          <front>
            <title>Domain Name System (DNS) Security Extensions Mapping for the Extensible Provisioning Protocol (EPP)</title>
            <author fullname="J. Gould" initials="J." surname="Gould"/>
            <author fullname="S. Hollenbeck" initials="S." surname="Hollenbeck"/>
            <date month="May" year="2010"/>
            <abstract>
              <t indent="0">This document describes an Extensible Provisioning Protocol (EPP) extension mapping for the provisioning and management of Domain Name System security (DNSSEC) extensions for domain names stored in a shared central repository. Specified in XML, this mapping extends the EPP domain name mapping to provide additional features required for the provisioning of DNS security extensions. This document obsoletes RFC 4310. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5910"/>
          <seriesInfo name="DOI" value="10.17487/RFC5910"/>
        </reference>
        <reference anchor="RFC6895" target="https://www.rfc-editor.org/info/rfc6895" quoteTitle="true" derivedAnchor="RFC6895">
          <front>
            <title>Domain Name System (DNS) IANA Considerations</title>
            <author fullname="D. Eastlake 3rd" initials="D." surname="Eastlake 3rd"/>
            <date month="April" year="2013"/>
            <abstract>
              <t indent="0">This document specifies Internet Assigned Numbers Authority (IANA) parameter assignment considerations for the allocation of Domain Name System (DNS) resource record types, CLASSes, operation codes, error codes, DNS protocol message header bits, and AFSDB resource record subtypes. It obsoletes RFC 6195 and updates RFCs 1183, 2845, 2930, and 3597.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="42"/>
          <seriesInfo name="RFC" value="6895"/>
          <seriesInfo name="DOI" value="10.17487/RFC6895"/>
        </reference>
        <reference anchor="RFC8174" target="https://www.rfc-editor.org/info/rfc8174" quoteTitle="true" derivedAnchor="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 indent="0">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>
        <reference anchor="XSD-DATATYPES" target="https://www.w3.org/TR/2004/REC-xmlschema-2-20041028/" quoteTitle="true" derivedAnchor="XSD-DATATYPES">
          <front>
            <title>XML Schema Part 2: Datatypes Second Edition</title>
            <author initials="P." surname="Biron" fullname="Paul V. Biron" role="editor"/>
            <author initials="A." surname="Malhotra" fullname="Ashok Malhotra" role="editor"/>
            <date month="October" year="2004"/>
          </front>
          <refcontent>W3C Recommendation</refcontent>
          <annotation>Latest version available at <eref target="https://www.w3.org/TR/xmlschema-2/" brackets="angle"/>.</annotation>
        </reference>
      </references>
      <references pn="section-9.2">
        <name slugifiedName="name-informative-references">Informative References</name>
        <reference anchor="RFC6927" target="https://www.rfc-editor.org/info/rfc6927" quoteTitle="true" derivedAnchor="RFC6927">
          <front>
            <title>Variants in Second-Level Names Registered in Top-Level Domains</title>
            <author fullname="J. Levine" initials="J." surname="Levine"/>
            <author fullname="P. Hoffman" initials="P." surname="Hoffman"/>
            <date month="May" year="2013"/>
            <abstract>
              <t indent="0">Internationalized Domain Names for Applications (IDNA) provides a method to map a subset of names written in Unicode into the DNS. Because of Unicode decisions, appearance, language and writing system conventions, and historical reasons, it often has been asserted that there is more than one way to write what competent readers and writers think of as the same host name; these different ways of writing are often called "variants". (The authors note that there are many conflicting definitions for the term "variant" in the IDNA community.) This document surveys the approaches that top-level domains have taken to the registration and provisioning of domain names that have variants. This document is not a product of the IETF, does not propose any method to make variants work "correctly", and is not an introduction to internationalization or IDNA.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6927"/>
          <seriesInfo name="DOI" value="10.17487/RFC6927"/>
        </reference>
        <reference anchor="RFC7451" target="https://www.rfc-editor.org/info/rfc7451" quoteTitle="true" derivedAnchor="RFC7451">
          <front>
            <title>Extension Registry for the Extensible Provisioning Protocol</title>
            <author fullname="S. Hollenbeck" initials="S." surname="Hollenbeck"/>
            <date month="February" year="2015"/>
            <abstract>
              <t indent="0">The Extensible Provisioning Protocol (EPP) includes features to add functionality by extending the protocol. It does not, however, describe how those extensions are managed. This document describes a procedure for the registration and management of extensions to EPP, and it specifies a format for an IANA registry to record those extensions.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7451"/>
          <seriesInfo name="DOI" value="10.17487/RFC7451"/>
        </reference>
        <reference anchor="RFC8590" target="https://www.rfc-editor.org/info/rfc8590" quoteTitle="true" derivedAnchor="RFC8590">
          <front>
            <title>Change Poll Extension for the Extensible Provisioning Protocol (EPP)</title>
            <author fullname="J. Gould" initials="J." surname="Gould"/>
            <author fullname="K. Feher" initials="K." surname="Feher"/>
            <date month="May" year="2019"/>
            <abstract>
              <t indent="0">This document describes an Extensible Provisioning Protocol (EPP) extension for notifying clients of operations on client-sponsored objects that were not initiated by the client through EPP. These operations may include contractual or policy requirements including, but not limited to, regular batch processes, customer support actions, Uniform Domain-Name Dispute-Resolution Policy (UDRP) or Uniform Rapid Suspension (URS) actions, court-directed actions, and bulk updates based on customer requests. Since the client is not directly involved or knowledgable of these operations, the extension is used along with an EPP object mapping to provide the resulting state of the postoperation object, and optionally a preoperation object, with the operation metadata of what, when, who, and why.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8590"/>
          <seriesInfo name="DOI" value="10.17487/RFC8590"/>
        </reference>
        <reference anchor="RFC9364" target="https://www.rfc-editor.org/info/rfc9364" quoteTitle="true" derivedAnchor="RFC9364">
          <front>
            <title>DNS Security Extensions (DNSSEC)</title>
            <author fullname="P. Hoffman" initials="P." surname="Hoffman"/>
            <date month="February" year="2023"/>
            <abstract>
              <t indent="0">This document describes the DNS Security Extensions (commonly called "DNSSEC") that are specified in RFCs 4033, 4034, and 4035, as well as a handful of others. One purpose is to introduce all of the RFCs in one place so that the reader can understand the many aspects of DNSSEC. This document does not update any of those RFCs. A second purpose is to state that using DNSSEC for origin authentication of DNS data is the best current practice. A third purpose is to provide a single reference for other documents that want to refer to DNSSEC.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="237"/>
          <seriesInfo name="RFC" value="9364"/>
          <seriesInfo name="DOI" value="10.17487/RFC9364"/>
        </reference>
        <reference anchor="RFC9499" target="https://www.rfc-editor.org/info/rfc9499" quoteTitle="true" derivedAnchor="RFC9499">
          <front>
            <title>DNS Terminology</title>
            <author fullname="P. Hoffman" initials="P." surname="Hoffman"/>
            <author fullname="K. Fujiwara" initials="K." surname="Fujiwara"/>
            <date month="March" year="2024"/>
            <abstract>
              <t indent="0">The Domain Name System (DNS) is defined in literally dozens of different RFCs. The terminology used by implementers and developers of DNS protocols, and by operators of DNS systems, has changed in the decades since the DNS was first defined. This document gives current definitions for many of the terms used in the DNS in a single document.</t>
              <t indent="0">This document updates RFC 2308 by clarifying the definitions of "forwarder" and "QNAME". It obsoletes RFC 8499 by adding multiple terms and clarifications. Comprehensive lists of changed and new definitions can be found in Appendices A and B.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="219"/>
          <seriesInfo name="RFC" value="9499"/>
          <seriesInfo name="DOI" value="10.17487/RFC9499"/>
        </reference>
        <reference anchor="SAC-025" target="https://www.icann.org/en/system/files/files/sac-025-en.pdf" quoteTitle="true" derivedAnchor="SAC-025">
          <front>
            <title>SSAC Advisory on Fast Flux Hosting and DNS</title>
            <author>
              <organization showOnFrontPage="true">ICANN Security and Stability Advisory Committee (SSAC)</organization>
            </author>
            <date month="January" year="2008"/>
          </front>
          <seriesInfo name="SAC" value="025"/>
        </reference>
      </references>
    </references>
    <section numbered="false" removeInRFC="false" toc="include" pn="section-appendix.a">
      <name slugifiedName="name-acknowledgments">Acknowledgments</name>
      <t indent="0" pn="section-appendix.a-1">The author wishes to thank the following people for their advice and
      feedback during the development of this document:</t>
      <ul bare="false" empty="false" indent="3" spacing="normal" pn="section-appendix.a-2">
        <li pn="section-appendix.a-2.1">
          <t indent="0" pn="section-appendix.a-2.1.1"><contact fullname="James Gould"/></t>
        </li>
        <li pn="section-appendix.a-2.2">
          <t indent="0" pn="section-appendix.a-2.2.1"><contact fullname="Hugo Salgado"/></t>
        </li>
        <li pn="section-appendix.a-2.3">
          <t indent="0" pn="section-appendix.a-2.3.1"><contact fullname="Patrick Mevzek"/></t>
        </li>
        <li pn="section-appendix.a-2.4">
          <t indent="0" pn="section-appendix.a-2.4.1"><contact fullname="Rick Wilhelm"/></t>
        </li>
        <li pn="section-appendix.a-2.5">
          <t indent="0" pn="section-appendix.a-2.5.1"><contact fullname="Marc Groeneweg"/></t>
        </li>
        <li pn="section-appendix.a-2.6">
          <t indent="0" pn="section-appendix.a-2.6.1"><contact fullname="Ties de Kock"/></t>
        </li>
        <li pn="section-appendix.a-2.7">
          <t indent="0" pn="section-appendix.a-2.7.1"><contact fullname="Tim Wicinski"/></t>
        </li>
        <li pn="section-appendix.a-2.8">
          <t indent="0" pn="section-appendix.a-2.8.1"><contact fullname="Jasdip Singh"/></t>
        </li>
      </ul>
    </section>
    <section anchor="authors-addresses" numbered="false" removeInRFC="false" toc="include" pn="section-appendix.b">
      <name slugifiedName="name-authors-address">Author's Address</name>
      <author fullname="Gavin Brown">
        <organization showOnFrontPage="true">ICANN</organization>
        <address>
          <postal>
            <street>12025 Waterfront Drive, Suite 300</street>
            <city>Los Angeles</city>
            <region>CA</region>
            <code>90292</code>
            <country>United States of America</country>
          </postal>
          <email>gavin.brown@icann.org</email>
          <uri>https://www.icann.org/</uri>
        </address>
      </author>
    </section>
  </back>
</rfc>
