<?xml version='1.0' encoding='utf-8'?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" version="3" category="std" submissionType="IETF" consensus="true" ipr="trust200902" docName="draft-ietf-regext-epp-quic-12" number="10087" tocInclude="true" updates="" obsoletes="" sortRefs="false" symRefs="true" xml:lang="en" prepTime="2026-11-17T00:13:25" indexInclude="true" scripts="Common,Latin" tocDepth="3">
  <link href="https://datatracker.ietf.org/doc/draft-ietf-regext-epp-quic-12" rel="prev"/>
  <link href="https://dx.doi.org/10.17487/rfc10087" rel="alternate"/>
  <link href="urn:issn:2070-1721" rel="alternate"/>
  <front>
    <title abbrev="EPP over QUIC">Extensible Provisioning Protocol (EPP) Transport over QUIC</title>
    <seriesInfo name="RFC" value="10087" stream="IETF"/>
    <author fullname="Jiankang Yao" initials="J." surname="Yao">
      <organization showOnFrontPage="true">CNNIC</organization>
      <address>
        <postal>
          <street>4 South 4th Street, Zhongguancun, Haidian District</street>
          <city>Beijing</city>
          <code>100190</code>
          <country>China</country>
        </postal>
        <phone>+86 10 59116505</phone>
        <email>yaojk@cnnic.cn</email>
      </address>
    </author>
    <author fullname="Hongtao Li" initials="H." surname="Li">
      <organization showOnFrontPage="true">CNNIC</organization>
      <address>
        <postal>
          <street>4 South 4th Street, Zhongguancun, Haidian District</street>
          <city>Beijing</city>
          <code>100190</code>
          <country>China</country>
        </postal>
        <email>lihongtao@cnnic.cn</email>
      </address>
    </author>
    <author fullname="Man Zhang" initials="M." surname="Zhang">
      <organization showOnFrontPage="true">CNNIC</organization>
      <address>
        <postal>
          <street>4 South 4th Street, Zhongguancun, Haidian District</street>
          <city>Beijing</city>
          <code>100190</code>
          <country>China</country>
        </postal>
        <email>zhangman@cnnic.cn</email>
      </address>
    </author>
    <author fullname="Daniel Keathley" initials="D." surname="Keathley">
      <organization showOnFrontPage="true">VeriSign, Inc.</organization>
      <address>
        <postal>
          <street>12061 Bluemont Way</street>
          <city>Reston</city>
          <region>VA</region>
          <code>20190</code>
          <country>United States of America</country>
        </postal>
        <email>dkeathley@verisign.com</email>
        <uri>http://www.verisigninc.com</uri>
      </address>
    </author>
    <author fullname="James Gould" initials="J." surname="Gould">
      <organization showOnFrontPage="true">VeriSign, Inc.</organization>
      <address>
        <postal>
          <street>12061 Bluemont Way</street>
          <city>Reston</city>
          <region>VA</region>
          <code>20190</code>
          <country>United States of America</country>
        </postal>
        <email>jgould@verisign.com</email>
        <uri>http://www.verisigninc.com</uri>
      </address>
    </author>
    <date month="11" year="2026"/>
    <area>OPS</area>
    <workgroup>regext</workgroup>
    <keyword>epp</keyword>
    <keyword>quic</keyword>
    <keyword>tcp</keyword>
    <keyword>eoq</keyword>
    <abstract pn="section-abstract">
      <t indent="0" pn="section-abstract-1">This document specifies how an Extensible Provisioning Protocol (EPP)
      session is mapped onto a QUIC connection. EPP over QUIC (EoQ) leverages
      features of the QUIC protocol.</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/rfc10087" 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) 2026 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" keepWithNext="true" pn="section-toc.1-1.1.1"><xref derivedContent="1" format="counter" sectionFormat="of" target="section-1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-introduction">Introduction</xref></t>
          </li>
          <li pn="section-toc.1-1.2">
            <t indent="0" keepWithNext="true" pn="section-toc.1-1.2.1"><xref derivedContent="2" format="counter" sectionFormat="of" target="section-2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-terminology">Terminology</xref></t>
          </li>
          <li pn="section-toc.1-1.3">
            <t indent="0" keepWithNext="true" 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-session-management">Session Management</xref></t>
          </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-message-exchange">Message Exchange</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-data-unit-format">Data Unit Format</xref></t>
          </li>
          <li pn="section-toc.1-1.6">
            <t indent="0" pn="section-toc.1-1.6.1"><xref derivedContent="6" format="counter" sectionFormat="of" target="section-6"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-eoq-connection-start-packet">EoQ Connection Start Packet</xref></t>
          </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-transport-considerations">Transport Considerations</xref></t>
          </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-operational-considerations"> Operational Considerations</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.8.2">
              <li pn="section-toc.1-1.8.2.1">
                <t indent="0" pn="section-toc.1-1.8.2.1.1"><xref derivedContent="8.1" format="counter" sectionFormat="of" target="section-8.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-clients-fall-back-with-mana"> Clients Fall Back with Management of Multiple Transport</xref></t>
              </li>
              <li pn="section-toc.1-1.8.2.2">
                <t indent="0" pn="section-toc.1-1.8.2.2.1"><xref derivedContent="8.2" format="counter" sectionFormat="of" target="section-8.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-port-number-reuse">Port Number Reuse</xref></t>
              </li>
              <li pn="section-toc.1-1.8.2.3">
                <t indent="0" pn="section-toc.1-1.8.2.3.1"><xref derivedContent="8.3" format="counter" sectionFormat="of" target="section-8.3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-quic-support-announcement-a">QUIC Support Announcement and Discovery</xref></t>
              </li>
              <li pn="section-toc.1-1.8.2.4">
                <t indent="0" pn="section-toc.1-1.8.2.4.1"><xref derivedContent="8.4" format="counter" sectionFormat="of" target="section-8.4"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-configuration-parameters">Configuration Parameters</xref></t>
              </li>
              <li pn="section-toc.1-1.8.2.5">
                <t indent="0" pn="section-toc.1-1.8.2.5.1"><xref derivedContent="8.5" format="counter" sectionFormat="of" target="section-8.5"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-diagnostic-and-troubleshoot">Diagnostic and Troubleshooting</xref></t>
              </li>
              <li pn="section-toc.1-1.8.2.6">
                <t indent="0" pn="section-toc.1-1.8.2.6.1"><xref derivedContent="8.6" format="counter" sectionFormat="of" target="section-8.6"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-address-validation">Address Validation</xref></t>
              </li>
              <li pn="section-toc.1-1.8.2.7">
                <t indent="0" pn="section-toc.1-1.8.2.7.1"><xref derivedContent="8.7" format="counter" sectionFormat="of" target="section-8.7"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-authentication-consideratio">Authentication Considerations</xref></t>
              </li>
              <li pn="section-toc.1-1.8.2.8">
                <t indent="0" pn="section-toc.1-1.8.2.8.1"><xref derivedContent="8.8" format="counter" sectionFormat="of" target="section-8.8"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-0-rtt-and-session-resumptio">0-RTT and Session Resumption</xref></t>
              </li>
              <li pn="section-toc.1-1.8.2.9">
                <t indent="0" pn="section-toc.1-1.8.2.9.1"><xref derivedContent="8.9" format="counter" sectionFormat="of" target="section-8.9"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-mtu-and-fragmentation">MTU and Fragmentation</xref></t>
              </li>
            </ul>
          </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-iana-considerations">IANA Considerations</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-registration-of-an-eoq-iden">Registration of an EoQ Identification String</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-registration-of-port-number">Registration of Port Number</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.10">
            <t indent="0" pn="section-toc.1-1.10.1"><xref derivedContent="10" format="counter" sectionFormat="of" target="section-10"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-security-considerations">Security Considerations</xref></t>
          </li>
          <li pn="section-toc.1-1.11">
            <t indent="0" pn="section-toc.1-1.11.1"><xref derivedContent="11" format="counter" sectionFormat="of" target="section-11"/>. <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.11.2">
              <li pn="section-toc.1-1.11.2.1">
                <t indent="0" pn="section-toc.1-1.11.2.1.1"><xref derivedContent="11.1" format="counter" sectionFormat="of" target="section-11.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-normative-references">Normative References</xref></t>
              </li>
              <li pn="section-toc.1-1.11.2.2">
                <t indent="0" pn="section-toc.1-1.11.2.2.1"><xref derivedContent="11.2" format="counter" sectionFormat="of" target="section-11.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-informative-references">Informative References</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.12">
            <t indent="0" pn="section-toc.1-1.12.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.a"/><xref derivedContent="" format="title" sectionFormat="of" target="name-acknowledgements">Acknowledgements</xref></t>
          </li>
          <li pn="section-toc.1-1.13">
            <t indent="0" pn="section-toc.1-1.13.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.b"/><xref derivedContent="" format="title" sectionFormat="of" target="name-authors-addresses">Authors' Addresses</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">This document specifies how the Extensible Provisioning Protocol
      (EPP) <xref target="RFC5730" format="default" sectionFormat="of" derivedContent="RFC5730"/> is mapped onto QUIC transport
      <xref target="RFC9000" format="default" sectionFormat="of" derivedContent="RFC9000"/>. QUIC is a protocol that is based on UDP and
      incorporates encryption support using TLS <xref target="RFC9001" format="default" sectionFormat="of" derivedContent="RFC9001"/>.
      Though based on UDP, QUIC provides connection semantics like other
      stateful protocols. This document discusses how EPP implementations can work
      with this and other features of QUIC while preserving the core EPP
      semantics.</t>
      <t indent="0" pn="section-1-2">  
	  EPP sessions use a single QUIC stream for all command and response exchanges throughout the session lifecycle. 

Unlike stateless transaction protocols that permit per-command independent streams, EPP is a stateful protocol 

with inherent sequential command dependencies defined in <xref target="RFC5730" format="default" sectionFormat="of" derivedContent="RFC5730"/>. 

Maintaining a single stream preserves ordered transaction processing, consistent session state, 

and full compatibility with existing EPP operational and implementation models.
</t>
      <t indent="0" pn="section-1-3">

EPP <xref target="RFC5730" format="default" sectionFormat="of" derivedContent="RFC5730"/> was designed for pluggability of transports that must follow <xref target="RFC5730" section="2.1" format="default" sectionFormat="of" derivedLink="https://rfc-editor.org/rfc/rfc5730#section-2.1" derivedContent="RFC5730"/>. 
 EoQ defines a fully pluggable QUIC transport for EPP as an alternative to other EPP transports, 
 such as EPP over TCP (EoT) <xref target="RFC5734" format="default" sectionFormat="of" derivedContent="RFC5734"/>.  
 The server can choose to offer EoQ in addition to EoT or as a replacement for EoT, 
 based on the security and performance considerations of QUIC and the preferred deployment architecture of the server and clients. 
</t>
      <t indent="0" pn="section-1-4">    EPP is primarily deployed for communication between domain registries

   and registrars, which commonly run many concurrent EPP sessions.

   Conventional EPP over TCP (EoT) requires a dedicated TCP connection

   for every single EPP session, resulting in connection

   overhead and resource consumption.  EoQ addresses this issue by

   leveraging QUIC stream multiplexing: multiple independent EPP

   sessions can run over one single persistent QUIC connection.
      </t>
    </section>
    <section anchor="conventions" numbered="true" toc="include" removeInRFC="false" pn="section-2">
      <name slugifiedName="name-terminology">Terminology</name>
      <t indent="0" pn="section-2-1">This document makes use of the following terms:</t>
      <dl newline="false" spacing="normal" indent="3" pn="section-2-2">
        <dt pn="section-2-2.1">EoQ:</dt>
        <dd pn="section-2-2.2">
          <t indent="0" pn="section-2-2.2.1">The acronym used for the EPP-over-QUIC transport that defines the use of QUIC 
          as an EPP transport following the considerations in <xref target="RFC5730" section="2.1" format="default" sectionFormat="of" derivedLink="https://rfc-editor.org/rfc/rfc5730#section-2.1" derivedContent="RFC5730"/>.</t>
        </dd>
        <dt pn="section-2-2.3">EoQ connection:</dt>
        <dd pn="section-2-2.4">
          <t indent="0" pn="section-2-2.4.1">Is a client-initiated bidirectional QUIC stream established on a QUIC connection using the "EoQ" Application-Layer Protocol Negotiation (ALPN) <xref target="RFC7301" format="default" sectionFormat="of" derivedContent="RFC7301"/> value.  The EoQ connection maps to the client-server connection defined in <xref target="RFC5730" section="2.1" format="default" sectionFormat="of" derivedLink="https://rfc-editor.org/rfc/rfc5730#section-2.1" derivedContent="RFC5730"/>, 
          where the server returns an EPP &lt;greeting&gt;.  A single QUIC connection supports many EoQ connections.</t>
        </dd>
        <dt pn="section-2-2.5">EoQ session:</dt>
        <dd pn="section-2-2.6">
          <t indent="0" pn="section-2-2.6.1">Is an authenticated EoQ connection, which occurs after a successful EPP &lt;login&gt;.</t>
        </dd>
        <dt pn="section-2-2.7">EoQ Connection Start Packet:</dt>
        <dd pn="section-2-2.8">
          <t indent="0" pn="section-2-2.8.1">Used by clients to complete the creation of an EoQ connection by signaling the server to create the QUIC stream and return the EPP &lt;greeting&gt; needed for an EPP connection.  
          <xref target="eoq-connection-start-packet" format="default" sectionFormat="of" derivedContent="Section 6"/> formally defines the EoQ Connection Start Packet.</t>
        </dd>
      </dl>
      <t indent="0" pn="section-2-3">
    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>
    </section>
    <section anchor="session-management" numbered="true" removeInRFC="false" toc="include" pn="section-3">
      <name slugifiedName="name-session-management">Session Management</name>
      <t indent="0" pn="section-3-1">Mapping EPP session management facilities onto the QUIC service is
      accomplished with a combination of a QUIC connection with the "EoQ" ALPN <xref target="RFC7301" format="default" sectionFormat="of" derivedContent="RFC7301"/> value and client-initiated, bidirectional QUIC streams.
      QUIC supports four stream types (<xref target="RFC9000" section="2.1" format="default" sectionFormat="of" derivedLink="https://rfc-editor.org/rfc/rfc9000#section-2.1" derivedContent="RFC9000"/>), but EoQ only supports the client-initiated, bidirectional stream type. 
</t>
      <t indent="0" pn="section-3-2">
	  
       As shown in <xref target="fig-example-suc-quic" format="default" sectionFormat="of" derivedContent="Figure 1"/>, an EPP session first requires creation of a QUIC connection between two peers, one
      that initiates the connection request and one that responds to the connection
      request. The initiating peer is called the "client", and the responding peer
      is called the "server". By default, an EPP server <bcp14>MUST</bcp14> listen for QUIC connection
      requests on the well-known UDP port number updated by IANA (see <xref target="iana-port" format="default" sectionFormat="of" derivedContent="Section 9.2"/>), unless there is a mutual agreement to use another port number.</t>
      <t indent="0" pn="section-3-3">A successfully established QUIC connection is secured by the
      TLS support that QUIC provides using the "EoQ" ALPN value.</t>
      <t indent="0" pn="section-3-4">Once the QUIC connection is established, the EPP client <bcp14>MUST</bcp14> then create a
      bidirectional QUIC stream by sending the <xref target="eoq-connection-start-packet" format="default" sectionFormat="of" derivedContent="Section 6">EoQ Connection Start Packet</xref>. <xref target="RFC9000" format="default" sectionFormat="of" derivedContent="RFC9000"/> states 
      that "streams can be created by sending data".  If the EPP server accepts the QUIC stream, 
      it reads the <xref target="eoq-connection-start-packet" format="default" sectionFormat="of" derivedContent="Section 6">EoQ Connection Start Packet</xref> and returns an EPP &lt;greeting&gt; to the client
      on the same QUIC stream. After reading the EPP &lt;greeting&gt;
      message, and absent processing errors, the EPP client sends EPP commands and receives EPP responses on the
      same stream. A QUIC stream corresponds to an EPP connection, which is referred to as an EoQ connection.  
      An authenticated QUIC stream, via a successful EPP &lt;login&gt;, 
      corresponds to an EPP session, which is referred to as an EoQ session.</t>
      <t indent="0" pn="section-3-5">An EPP session is normally ended by the client issuing an EPP
      &lt;logout&gt; command. A server receiving an EPP &lt;logout&gt; command <bcp14>MUST</bcp14>
      end the EPP session and close the QUIC stream. 
      A client <bcp14>MAY</bcp14> end an EoQ session by closing the QUIC stream and the server <bcp14>MUST</bcp14> end the EoQ session by closing the QUIC stream.</t>
      <t indent="0" pn="section-3-6">EoQ connections are established as described in the QUIC transport
      specification <xref target="RFC9000" format="default" sectionFormat="of" derivedContent="RFC9000"/>. During connection establishment, EoQ
      support is indicated using the "EoQ" ALPN value in the cryptographic handshake.</t>
      <t indent="0" pn="section-3-7">A single QUIC connection may allow multiple QUIC streams. This means that
      a single QUIC connection may support multiple EoQ sessions. A server <bcp14>MAY</bcp14> limit
      the life span of an established EoQ session. EoQ sessions
      that are inactive for more than a server-defined period <bcp14>MAY</bcp14> be ended by the
      server closing the QUIC stream. A server <bcp14>MAY</bcp14> close EoQ sessions that have been
      open and active for longer than a server-defined limit. 
     
      
      
      The max_idle_timeout transport parameter defined in
<xref target="RFC9000" section="18.2" format="default" sectionFormat="of" derivedLink="https://rfc-editor.org/rfc/rfc9000#section-18.2" derivedContent="RFC9000"/> <bcp14>MUST NOT</bcp14> be set to a non-zero value by the
client or server. Once the last QUIC stream for a QUIC connection is
closed, the server <bcp14>MAY</bcp14> either immediately end the QUIC connection
or retain the open connection in accordance with local configuration and
operational policy.
      
      
      </t>
    </section>
    <section anchor="message-exchange" numbered="true" removeInRFC="false" toc="include" pn="section-4">
      <name slugifiedName="name-message-exchange">Message Exchange</name>
      <t indent="0" pn="section-4-1">
	       
	       EPP messages are passed on an EoQ connection, which is a client-initiated, 
	       bidirectional QUIC stream, defined in <xref target="session-management" format="default" sectionFormat="of" derivedContent="Section 3"/>. 
	      
	      
	      Except for the EPP server &lt;greeting&gt;, EPP messages are
      initiated by the EPP client in the form of EPP commands.  An EPP
      server <bcp14>MUST</bcp14> return an EPP response to an EPP command on the same QUIC stream
      that carried the command.  If the QUIC stream is closed
      after a server receives and successfully processes a command but
      before the response can be returned to the client, the server <bcp14>MAY</bcp14>
      attempt to undo the effects of the command to ensure a consistent
      state between the client and the server.  EPP commands are
      idempotent, so processing a command more than once produces the same
      net effect on the repository as successfully processing the command
      once.</t>
      <t indent="0" pn="section-4-2">An EPP client streams EPP commands to an EPP server on an established
      QUIC stream.  A client <bcp14>MAY</bcp14> establish multiple QUIC streams to support multiple EoQ sessions 
      with each EoQ session mapped to a single QUIC stream. 
      
      
      A server <bcp14>SHOULD</bcp14> limit a client to a maximum number of QUIC streams per QUIC connection based on server capabilities 
and operational load. Absent such a limit, a server may be subject to overload and resource exhaustion.
 <xref target="RFC9000" section="4.6" format="default" sectionFormat="of" derivedLink="https://rfc-editor.org/rfc/rfc9000#section-4.6" derivedContent="RFC9000"/> discusses this situation.
      
      
  
      </t>
      <t indent="0" pn="section-4-3">EPP describes client-server interaction as a command-response
      exchange where the client sends one command to the server and the
      server returns one response to the client.</t>
      <t indent="0" pn="section-4-4">Each EPP data unit <bcp14>MUST</bcp14> contain a single EPP message.  Commands <bcp14>MUST</bcp14>
      be processed independently.</t>
      <t indent="0" pn="section-4-5">A server <bcp14>SHOULD</bcp14> impose a limit on the amount of time required for a client to issue a 
      well-formed EPP command to reduce the risk associated with a resource exhaustion attack.
      For example, the time limit is 10 minutes for the server idle timeout and 8 minutes for client keep-alive.
      
      Absent local policy, a server <bcp14>MUST</bcp14> end an
      EoQ session and close the QUIC stream if a well-formed command
      is not received within the time limit.</t>
      <t indent="0" pn="section-4-6">A general state machine for an EPP server is described in
      <xref target="RFC5730" section="2" format="default" sectionFormat="of" derivedLink="https://rfc-editor.org/rfc/rfc5730#section-2" derivedContent="RFC5730"/>. A  general client-server message exchange
      using QUIC transport is illustrated in <xref target="fig-example-suc-quic" format="default" sectionFormat="of" derivedContent="Figure 1"/>.
      
      
      It shows an example of successful exchange over a
   single QUIC stream of a QUIC connection.
      
      
       Many QUIC streams may be opened and closed
      during the life of a QUIC connection.

      </t>
      <figure anchor="fig-example-suc-quic" align="center" suppress-title="false" pn="figure-1">
        <name slugifiedName="name-example-of-successful-quic-">Example of Successful QUIC Client-Server Message Exchange</name>
        <artwork align="left" pn="section-4-7.1">
     Client                  Server
|                                     |
|      Successful QUIC Connection     |
| &lt;&lt;-------------------------------&gt;&gt; |
|                                     |
|     Successful QUIC Stream with     |
|     EoQ Connection Start Packet     |
| &lt;&lt;-------------------------------&gt;&gt; |
|                                     |
|             Send Greeting           |
| &lt;&lt;-------------------------------&lt;&lt; |
|                                     |
|             Send &lt;login&gt;            |
| &gt;&gt;-------------------------------&gt;&gt; |
|                                     |
|             Send Response           |
| &lt;&lt;-------------------------------&lt;&lt; |
|                                     |
|            Send Command X           |
| &gt;&gt;-------------------------------&gt;&gt; |
|                                     |
|            Send Response X          |
| &lt;&lt;-------------------------------&lt;&lt; |
|                                     |
|            Send Command Y           |
| &gt;&gt;-------------------------------&gt;&gt; |
|                                     |
|            Send Response Y          |
| &lt;&lt;-------------------------------&lt;&lt; |
|                  .                  |
                   .
                   .
|            Send &lt;logout&gt;            |
| &gt;&gt;-------------------------------&gt;&gt; |
|                                     |
|            Send Response            |
| &lt;&lt;-------------------------------&lt;&lt; |
|                                     |
|          Close QUIC Stream          |
| &lt;&lt;-------------------------------&gt;&gt; |
|                                     |
|        Close QUIC Connection        |
| &lt;&lt;-------------------------------&gt;&gt; |</artwork>
      </figure>
      <t indent="0" pn="section-4-8">The EPP server <bcp14>MUST</bcp14> follow the "EPP Server State Machine" procedure (see 
      Figure 1 in <xref target="RFC5730" format="default" sectionFormat="of" derivedContent="RFC5730"/>).</t>
    </section>
    <section anchor="dataunit" numbered="true" removeInRFC="false" toc="include" pn="section-5">
      <name slugifiedName="name-data-unit-format">Data Unit Format</name>
      <t indent="0" pn="section-5-1">The EPP data unit contains two fields: a 32-bit header that describes
      the total length of the data unit, and the EPP XML instance.  The
      length of the EPP XML instance is determined by subtracting four
      octets from the total length of the data unit.  A receiver must
      successfully read that many octets to retrieve the complete EPP XML
      instance before processing the EPP message.

      The EPP data unit format is depicted in <xref target="fig-epp-data-unit-for" format="default" sectionFormat="of" derivedContent="Figure 2"/> (one tick mark represents one bit position).

      </t>
      <figure anchor="fig-epp-data-unit-for" align="center" suppress-title="false" pn="figure-2">
        <name slugifiedName="name-epp-data-unit-format">EPP Data Unit Format</name>
        <artwork align="left" pn="section-5-2.1">
 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                           Total Length                        |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                         EPP XML Instance                      |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+//-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</artwork>
      </figure>
      <t indent="0" pn="section-5-3">The fields shown in <xref target="fig-epp-data-unit-for" format="default" sectionFormat="of" derivedContent="Figure 2"/> are defined as follows:</t>
      <dl indent="3" newline="false" spacing="normal" pn="section-5-4">
        <dt pn="section-5-4.1">Total Length (32 bits):</dt>
        <dd pn="section-5-4.2">
          <t indent="0" pn="section-5-4.2.1">The total length of the EPP data unit
      measured in octets in network (big endian) byte order.  The octets
      contained in this field <bcp14>MUST</bcp14> be included in the total length
      calculation. The 32-bit total length matches the total length used in EoT, 
       defined in <xref target="RFC5734" format="default" sectionFormat="of" derivedContent="RFC5734"/>, to support transport pluggability.
          </t>
        </dd>
        <dt pn="section-5-4.3">
      EPP XML Instance (variable length):</dt>
        <dd pn="section-5-4.4"> The EPP XML instance carried in
      the data unit.</dd>
      </dl>
    </section>
    <section anchor="eoq-connection-start-packet" numbered="true" removeInRFC="false" toc="include" pn="section-6">
      <name slugifiedName="name-eoq-connection-start-packet">EoQ Connection Start Packet</name>
      <t indent="0" pn="section-6-1">The EoQ Connection Start Packet is written by the client after creating 
      a QUIC stream to signal to the server to initialize the QUIC stream. 
 Absent processing errors or local policy,
	  the 
      server accepts the QUIC stream, reads the EoQ Connection Start Packet, and returns the EPP &lt;greeting&gt; 
      to the client on same QUIC stream.</t>
      <t indent="0" pn="section-6-2">The EoQ Connection Start Packet follows the <xref target="dataunit" format="default" sectionFormat="of" derivedContent="Section 5">Data Unit Format</xref> with two fields: 
      a 32-bit header that describes the total length of the data unit, and the 
      constant value of "EoQ Connection Start" instead of an "EPP XML Instance".  
      The length of a valid data unit <bcp14>MUST</bcp14> be 
      24 octets, which includes 4 octets for the Total Length and 20 octets for the 
      "EoQ Connection Start" constant value.</t>
      <t indent="0" pn="section-6-3"> If the EoQ Connection Start Packet received by the server is not valid (e.g., when the total length is not exactly 24 octets),
 the server <bcp14>MUST</bcp14> close that QUIC stream. The server <bcp14>MAY</bcp14> return an error indication prior to closing the stream.
      </t>
    </section>
    <section numbered="true" removeInRFC="false" toc="include" pn="section-7">
      <name slugifiedName="name-transport-considerations">Transport Considerations</name>
      <t indent="0" pn="section-7-1">
        <xref target="RFC5730" section="2.1" format="default" sectionFormat="of" derivedLink="https://rfc-editor.org/rfc/rfc5730#section-2.1" derivedContent="RFC5730"/> describes considerations to be
        addressed by protocol transport mappings. This document addresses each
        of those considerations using a combination of features of the QUIC
        protocol and features of this document as discussed below:

      </t>
      <dl newline="true" spacing="normal" indent="3" pn="section-7-2">
        <dt pn="section-7-2.1">Command Order:</dt>
        <dd pn="section-7-2.2">QUIC guarantees ordered processing of data within each stream.
            <xref target="RFC9000" section="2" format="default" sectionFormat="of" derivedLink="https://rfc-editor.org/rfc/rfc9000#section-2" derivedContent="RFC9000"/> describes streams in detail.</dd>
        <dt pn="section-7-2.3">Session Mapping:</dt>
        <dd pn="section-7-2.4">EPP session management utilizes QUIC streams and is
            described in <xref target="session-management" format="default" sectionFormat="of" derivedContent="Section 3"/>.</dd>
        <dt pn="section-7-2.5">Stateful Nature:</dt>
        <dd pn="section-7-2.6">QUIC supports stateful communications between endpoints via
            Connection IDs and long-lived streams within each connection. QUIC streams on top of QUIC connections, defined in Sections <xref target="RFC9000" section="2" sectionFormat="bare" format="default" derivedLink="https://rfc-editor.org/rfc/rfc9000#section-2" derivedContent="RFC9000"/> and <xref target="RFC9000" section="5" sectionFormat="bare" format="default" derivedLink="https://rfc-editor.org/rfc/rfc9000#section-5" derivedContent="RFC9000"/> of
            <xref target="RFC9000" format="default" sectionFormat="of" derivedContent="RFC9000"/>, 
            are used to create stateful communications between the client and server.</dd>
        <dt pn="section-7-2.7">Frame Data Units:</dt>
        <dd pn="section-7-2.8">EoQ uses the packet framing defined in <xref target="dataunit" format="default" sectionFormat="of" derivedContent="Section 5"/>.</dd>
        <dt pn="section-7-2.9">Congestion Avoidance:</dt>
        <dd pn="section-7-2.10">QUIC provides various mechanisms to help achieve congestion avoidance.
            <xref target="RFC9002" format="default" sectionFormat="of" derivedContent="RFC9002"/> describes these mechanisms in detail.</dd>
        <dt pn="section-7-2.11">Reliability:</dt>
        <dd pn="section-7-2.12">QUIC uses message acknowledgement, packet retransmission, and other features to
            ensure reliability. <xref target="RFC9000" section="13" format="default" sectionFormat="of" derivedLink="https://rfc-editor.org/rfc/rfc9000#section-13" derivedContent="RFC9000"/> describes these features
            in detail.</dd>
        <dt pn="section-7-2.13">Pipelining:</dt>
        <dd pn="section-7-2.14">
          <t indent="0" pn="section-7-2.14.1">Pipelining is allowed in EoQ. QUIC streams support sending
            multiple frames without waiting for responses from the other
            peer. This does not change the basic single command, single response
            operating mode of the core EPP.</t>
          <t indent="0" pn="section-7-2.14.2">Commands <bcp14>MUST</bcp14> be processed independently and in the same order as sent from the client.</t>
          <t indent="0" pn="section-7-2.14.3">Batch-oriented processing (combining
            multiple EPP commands in a single data unit) is not permitted.  Each EPP data unit must contain a single EPP message.</t>
          <t indent="0" pn="section-7-2.14.4">An EPP x5zz "Connection Management" error response, defined in <xref target="RFC5730" section="3" format="default" sectionFormat="of" derivedLink="https://rfc-editor.org/rfc/rfc5730#section-3" derivedContent="RFC5730"/>, 
            of a well-formed EPP client packet results in the server closing the EoQ connection after returning the error response.  A malformed EPP client packet 
            results in the server closing the EoQ connection without providing an error response.  All subsequent EPP commands sent on the EoQ connection will not be processed.</t>
        </dd>
      </dl>
    </section>
    <section anchor="Operational" numbered="true" toc="include" removeInRFC="false" pn="section-8">
      <name slugifiedName="name-operational-considerations"> Operational Considerations</name>
      <t indent="0" pn="section-8-1">
		
		
		Some of the concerns examined within this section are also addressed in <xref target="RFC9308" format="default" sectionFormat="of" derivedContent="RFC9308"/>. 
		Authors of this specification encourage implementers to understand <xref target="RFC9308" format="default" sectionFormat="of" derivedContent="RFC9308"/>.
      </t>
      <section anchor="Operational1" numbered="true" toc="include" removeInRFC="false" pn="section-8.1">
        <name slugifiedName="name-clients-fall-back-with-mana"> Clients Fall Back with Management of Multiple Transport</name>
        <t indent="0" pn="section-8.1-1">


If the establishment of an EoQ connection fails, clients <bcp14>MAY</bcp14> attempt to fall back to EPP over TCP
as specified in <xref target="RFC5734" format="default" sectionFormat="of" derivedContent="RFC5734"/>, depending on local deployment and security policy.
It is up to clients to determine the mix of transports that best meets their business needs.


</t>
      </section>
      <section anchor="Operational2" numbered="true" toc="include" removeInRFC="false" pn="section-8.2">
        <name slugifiedName="name-port-number-reuse">Port Number Reuse</name>
        <t indent="0" pn="section-8.2-1">

Although <xref target="RFC5734" format="default" sectionFormat="of" derivedContent="RFC5734"/>  does only a request for TCP, the companion UDP port number was also allocated. That practice was prior to 
  <xref target="RFC6335" format="default" sectionFormat="of" derivedContent="RFC6335"/> when TCP and UDP port numbers were simultaneously assigned when either was requested.


<xref target="iana-port" format="default" sectionFormat="of" derivedContent="Section 9.2"/> updates EPP UDP/700 allocation to be used exclusively for EoQ.
This update does not introduce any operational issues given that there are no known implementations of EPP over UDP.

</t>
      </section>
      <section anchor="Operational3" numbered="true" toc="include" removeInRFC="false" pn="section-8.3">
        <name slugifiedName="name-quic-support-announcement-a">QUIC Support Announcement and Discovery</name>
        <t indent="0" pn="section-8.3-1">

There is no dedicated in-band mechanism defined in this specification for a server to 
explicitly announce EoQ support to clients.
Operators <bcp14>MAY</bcp14> use out-of-band configuration or provisioning channels 
to advertise server EoQ support to clients in advance.

</t>
      </section>
      <section anchor="Operational4" numbered="true" toc="include" removeInRFC="false" pn="section-8.4">
        <name slugifiedName="name-configuration-parameters">Configuration Parameters</name>
        <t indent="0" pn="section-8.4-1">
Implementations <bcp14>MAY</bcp14> configure operational parameters to control EoQ session behavior.
These parameters can include idle session timeout, maximum QUIC streams per connection, command processing timeout, 
and maximum session timeout. 

Servers and clients <bcp14>SHOULD</bcp14>
configure limits to avoid session disruption and resource
exhaustion.
</t>
        <aside pn="section-8.4-2">
          <t indent="0" pn="section-8.4-2.1">
Implementation Note: There is no in-band protocol mechanism to align limits. Operators typically distribute standard settings via SDKs. Client timeout and stream limits shall be set lower than server values for graceful connection handling. Timeout rules are consistent across EoT and EoQ; per-connection stream limits are newly introduced in EoQ.
</t>
        </aside>
      </section>
      <section anchor="Operational5" numbered="true" toc="include" removeInRFC="false" pn="section-8.5">
        <name slugifiedName="name-diagnostic-and-troubleshoot">Diagnostic and Troubleshooting</name>
        <t indent="0" pn="section-8.5-1">
Operators <bcp14>SHOULD</bcp14> log the EoQ connection establishment status, stream lifecycle events, 
and command transaction results for diagnostic purposes.
QUIC transport errors and EPP protocol failures ought to be distinguishable to facilitate efficient troubleshooting.
Implementations <bcp14>MAY</bcp14> provide granular error reporting to help identify session termination, connection timeout, and stream closure root causes. Operators <bcp14>MUST</bcp14> redact sensitive data in the logs, such as user credentials and 
authorization information values.

</t>
      </section>
      <section anchor="Operational6" numbered="true" toc="include" removeInRFC="false" pn="section-8.6">
        <name slugifiedName="name-address-validation">Address Validation</name>
        <t indent="0" pn="section-8.6-1">
EoQ implementations <bcp14>MUST</bcp14> follow the address validation requirements defined in <xref target="RFC9000" section="8" format="default" sectionFormat="of" derivedLink="https://rfc-editor.org/rfc/rfc9000#section-8" derivedContent="RFC9000"/>  
to mitigate potential amplification attacks and validate client address reachability.
</t>
      </section>
      <section anchor="Operational7" numbered="true" toc="include" removeInRFC="false" pn="section-8.7">
        <name slugifiedName="name-authentication-consideratio">Authentication Considerations</name>
        <t indent="0" pn="section-8.7-1">
	  EoQ relies on the TLS authentication mechanisms defined in <xref target="RFC9001" format="default" sectionFormat="of" derivedContent="RFC9001"/>  for peer authentication
	  and credential validation. Implementations <bcp14>MUST</bcp14> follow the same authentication practices
	  specified for EPP over TLS in <xref target="RFC5734" format="default" sectionFormat="of" derivedContent="RFC5734"/>. 
	  Server and client authentication procedures remain unchanged from existing EPP deployment models 
	  when running over QUIC transport.
</t>
      </section>
      <section anchor="Operational8" numbered="true" toc="include" removeInRFC="false" pn="section-8.8">
        <name slugifiedName="name-0-rtt-and-session-resumptio">0-RTT and Session Resumption</name>
        <t indent="0" pn="section-8.8-1">Using 0-RTT for EoQ allows clients to establish connections and initiate EPP transactions without round-trip delay, 
	  enabling servers to use shorter idle timers and reduce connection overhead.
Session resumption and 0-RTT introduce privacy and replay risks. 

</t>
        <t indent="0" pn="section-8.8-2">
EPP commands fall into three categories: session management, queries, and transform commands. 
EPP query commands perform read-only object information retrieval operations.
Only read-only EPP query commands <bcp14>MAY</bcp14> be carried in 0-RTT STREAM frames; all other EPP commands <bcp14>MUST NOT</bcp14> use 0-RTT. 

Clients <bcp14>SHOULD</bcp14> use resumption tickets only once specified in <xref target="RFC9846" format="default" sectionFormat="of" derivedContent="RFC9846"/>. 
Servers <bcp14>SHOULD</bcp14> issue session-resumption tickets with a sufficiently long lifetime (e.g., 6 hours).
 Servers <bcp14>SHOULD</bcp14> implement the anti-replay mechanisms specified in <xref target="RFC9846" section="8" format="default" sectionFormat="of" derivedLink="https://rfc-editor.org/rfc/rfc9846#section-8" derivedContent="RFC9846"/>.

</t>
        <t indent="0" pn="section-8.8-3">
EoQ implementations <bcp14>SHOULD</bcp14> 
follow the guidance in <xref target="RFC9846" format="default" sectionFormat="of" derivedContent="RFC9846"/>  and <xref target="RFC9001" format="default" sectionFormat="of" derivedContent="RFC9001"/> to balance performance and risk mitigation.
Failure to do so increases privacy exposure and replay attack risks. 


</t>
      </section>
      <section anchor="Operational9" numbered="true" toc="include" removeInRFC="false" pn="section-8.9">
        <name slugifiedName="name-mtu-and-fragmentation">MTU and Fragmentation</name>
        <t indent="0" pn="section-8.9-1">
	      EoQ implementations <bcp14>MUST</bcp14> follow <xref target="RFC9000" section="14" format="default" sectionFormat="of" derivedLink="https://rfc-editor.org/rfc/rfc9000#section-14" derivedContent="RFC9000"/>.

</t>
      </section>
    </section>
    <section anchor="iana" numbered="true" removeInRFC="false" toc="include" pn="section-9">
      <name slugifiedName="name-iana-considerations">IANA Considerations</name>
      <section anchor="iana-alpn" numbered="true" removeInRFC="false" toc="include" pn="section-9.1">
        <name slugifiedName="name-registration-of-an-eoq-iden">Registration of an EoQ Identification String</name>
        <t indent="0" pn="section-9.1-1">This document creates a new registration for the identification of EoQ in
        the "TLS Application-Layer Protocol Negotiation (ALPN) Protocol IDs"
        registry under the "Transport Layer Security (TLS) Extensions" registry group available at <eref target="https://www.iana.org/assignments/tls-extensiontype-values/" brackets="angle"/>.</t>
        <dl spacing="normal" newline="false" indent="3" pn="section-9.1-2">
          <dt pn="section-9.1-2.1">Protocol:</dt>
          <dd pn="section-9.1-2.2">EoQ</dd>
          <dt pn="section-9.1-2.3">Identification Sequence:</dt>
          <dd pn="section-9.1-2.4">0x45 0x6F 0x51 ("EoQ")</dd>
          <dt pn="section-9.1-2.5">Reference:</dt>
          <dd pn="section-9.1-2.6">RFC 10087</dd>
        </dl>
      </section>
      <section anchor="iana-port" numbered="true" removeInRFC="false" toc="include" pn="section-9.2">
        <name slugifiedName="name-registration-of-port-number">Registration of Port Number</name>
        <t indent="0" pn="section-9.2-1">The "Service Name and Transport Protocol Port Number Registry" (<eref target="https://www.iana.org/assignments/service-names-port-numbers/" brackets="angle"/>) contains an entry for EPP UDP/700. However, there is no known usage of EPP over UDP. This document therefore specifies EPP over UDP as defined here. IANA has updated the description field of the EPP UDP/700 entry to be "EPP running over QUIC" and added this document as an additional reference alongside <xref target="RFC5734" format="default" sectionFormat="of" derivedContent="RFC5734"/>.</t>
        <dl spacing="normal" newline="false" indent="3" pn="section-9.2-2">
          <dt pn="section-9.2-2.1">Service Name:</dt>
          <dd pn="section-9.2-2.2">epp</dd>
          <dt pn="section-9.2-2.3">Port Number:</dt>
          <dd pn="section-9.2-2.4">700</dd>
          <dt pn="section-9.2-2.5">Transport Protocol(s):</dt>
          <dd pn="section-9.2-2.6">UDP</dd>
          <dt pn="section-9.2-2.7">Assignee:</dt>
          <dd pn="section-9.2-2.8">IESG</dd>
          <dt pn="section-9.2-2.9">Contact:</dt>
          <dd pn="section-9.2-2.10">IETF Chair</dd>
          <dt pn="section-9.2-2.11">Description:</dt>
          <dd pn="section-9.2-2.12">EPP running over QUIC</dd>
          <dt pn="section-9.2-2.13">Reference:</dt>
          <dd pn="section-9.2-2.14">
            <xref target="RFC5734" format="default" sectionFormat="of" derivedContent="RFC5734"/> RFC 10087</dd>
        </dl>
      </section>
    </section>
    <section anchor="security" numbered="true" removeInRFC="false" toc="include" pn="section-10">
      <name slugifiedName="name-security-considerations">Security Considerations</name>
      <t indent="0" pn="section-10-1">
	      
	      EPP over QUIC provides similar security foundations as EPP over TCP with TLS, 
	      though the security properties of QUIC specified in <xref target="RFC9000" section="21.1" format="default" sectionFormat="of" derivedLink="https://rfc-editor.org/rfc/rfc9000#section-21.1" derivedContent="RFC9000"/> 
	      differ from those of TLS/TCP in that QUIC is an encrypted transport protocol.

	      
      Some related security issues are discussed in <xref target="RFC5734" format="default" sectionFormat="of" derivedContent="RFC5734"/>
      and <xref target="RFC9000" format="default" sectionFormat="of" derivedContent="RFC9000"/>. Sections <xref target="Operational7" format="counter" sectionFormat="of" derivedContent="8.7"/> and <xref target="Operational8" format="counter" sectionFormat="of" derivedContent="8.8"/> of this document also discuss related security issues.</t>
      <t indent="0" pn="section-10-2">
      EoQ servers run the risk of a resource exhaustion attack by allowing the creation of unlimited QUIC streams per QUIC connection.  
      As indicated in <xref target="Operational4" format="default" sectionFormat="of" derivedContent="Section 8.4"/>,
      
      servers should limit a client to a maximum number of QUIC streams per QUIC connection based on server capabilities and operational load.
	  Absent such a limit, the server may be subject to overload that would exhaust its resources.
	  
      </t>
      <t indent="0" pn="section-10-3">
      The 32-bit total length field defined in <xref target="dataunit" format="default" sectionFormat="of" derivedContent="Section 5"/> allows a declared payload size up to approximately 4 gigabytes.
 Implementations <bcp14>MUST</bcp14> validate the advertised total length against a locally configured maximum frame size limit 
before allocating memory or attempting to read the full frame. Without this check, an attacker could send a crafted
 frame with an excessively large length value to exhaust receiver memory and trigger a denial-of-service condition.
      </t>
    </section>
  </middle>
  <back>
    <references pn="section-11">
      <name slugifiedName="name-references">References</name>
      <references pn="section-11.1">
        <name slugifiedName="name-normative-references">Normative References</name>
        <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="RFC5730" target="https://www.rfc-editor.org/info/rfc5730" quoteTitle="true" derivedAnchor="RFC5730">
          <front>
            <title>Extensible Provisioning Protocol (EPP)</title>
            <author fullname="S. Hollenbeck" initials="S." surname="Hollenbeck"/>
            <date month="August" year="2009"/>
            <abstract>
              <t indent="0">This document describes an application-layer client-server protocol for the provisioning and management of objects stored in a shared central repository. Specified in XML, the protocol defines generic object management operations and an extensible framework that maps protocol operations to objects. This document includes a protocol specification, an object mapping template, and an XML media type registration. This document obsoletes RFC 4930. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="69"/>
          <seriesInfo name="RFC" value="5730"/>
          <seriesInfo name="DOI" value="10.17487/RFC5730"/>
        </reference>
        <reference anchor="RFC5734" target="https://www.rfc-editor.org/info/rfc5734" quoteTitle="true" derivedAnchor="RFC5734">
          <front>
            <title>Extensible Provisioning Protocol (EPP) Transport over TCP</title>
            <author fullname="S. Hollenbeck" initials="S." surname="Hollenbeck"/>
            <date month="August" year="2009"/>
            <abstract>
              <t indent="0">This document describes how an Extensible Provisioning Protocol (EPP) session is mapped onto a single Transmission Control Protocol (TCP) connection. This mapping requires use of the Transport Layer Security (TLS) protocol to protect information exchanged between an EPP client and an EPP server. This document obsoletes RFC 4934. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="69"/>
          <seriesInfo name="RFC" value="5734"/>
          <seriesInfo name="DOI" value="10.17487/RFC5734"/>
        </reference>
        <reference anchor="RFC6335" target="https://www.rfc-editor.org/info/rfc6335" quoteTitle="true" derivedAnchor="RFC6335">
          <front>
            <title>Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry</title>
            <author fullname="M. Cotton" initials="M." surname="Cotton"/>
            <author fullname="L. Eggert" initials="L." surname="Eggert"/>
            <author fullname="J. Touch" initials="J." surname="Touch"/>
            <author fullname="M. Westerlund" initials="M." surname="Westerlund"/>
            <author fullname="S. Cheshire" initials="S." surname="Cheshire"/>
            <date month="August" year="2011"/>
            <abstract>
              <t indent="0">This document defines the procedures that the Internet Assigned Numbers Authority (IANA) uses when handling assignment and other requests related to the Service Name and Transport Protocol Port Number registry. It also discusses the rationale and principles behind these procedures and how they facilitate the long-term sustainability of the registry.</t>
              <t indent="0">This document updates IANA's procedures by obsoleting the previous UDP and TCP port assignment procedures defined in Sections 8 and 9.1 of the IANA Allocation Guidelines, and it updates the IANA service name and port assignment procedures for UDP-Lite, the Datagram Congestion Control Protocol (DCCP), and the Stream Control Transmission Protocol (SCTP). It also updates the DNS SRV specification to clarify what a service name is and how it is registered. This memo documents an Internet Best Current Practice.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="165"/>
          <seriesInfo name="RFC" value="6335"/>
          <seriesInfo name="DOI" value="10.17487/RFC6335"/>
        </reference>
        <reference anchor="RFC7301" target="https://www.rfc-editor.org/info/rfc7301" quoteTitle="true" derivedAnchor="RFC7301">
          <front>
            <title>Transport Layer Security (TLS) Application-Layer Protocol Negotiation Extension</title>
            <author fullname="S. Friedl" initials="S." surname="Friedl"/>
            <author fullname="A. Popov" initials="A." surname="Popov"/>
            <author fullname="A. Langley" initials="A." surname="Langley"/>
            <author fullname="E. Stephan" initials="E." surname="Stephan"/>
            <date month="July" year="2014"/>
            <abstract>
              <t indent="0">This document describes a Transport Layer Security (TLS) extension for application-layer protocol negotiation within the TLS handshake. For instances in which multiple application protocols are supported on the same TCP or UDP port, this extension allows the application layer to negotiate which protocol will be used within the TLS connection.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7301"/>
          <seriesInfo name="DOI" value="10.17487/RFC7301"/>
        </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="RFC9846" target="https://www.rfc-editor.org/info/rfc9846" quoteTitle="true" derivedAnchor="RFC9846">
          <front>
            <title>The Transport Layer Security (TLS) Protocol Version 1.3</title>
            <author fullname="E. Rescorla" initials="E." surname="Rescorla"/>
            <date month="July" year="2026"/>
            <abstract>
              <t indent="0">This document specifies version 1.3 of the Transport Layer Security (TLS) protocol. TLS allows client/server applications to communicate over the Internet in a way that is designed to prevent eavesdropping, tampering, and message forgery.</t>
              <t indent="0">This document obsoletes RFC 8446, which specified TLS 1.3. This document obsoletes RFC 5246 (specifying TLS 1.2) and RFCs 5077, 6961, 7627, and 8422, all of which pertain to TLS 1.2 or earlier, and updates RFCs 5705 and 6066. This document also specifies new requirements for TLS 1.2 implementations.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9846"/>
          <seriesInfo name="DOI" value="10.17487/RFC9846"/>
        </reference>
        <reference anchor="RFC9000" target="https://www.rfc-editor.org/info/rfc9000" quoteTitle="true" derivedAnchor="RFC9000">
          <front>
            <title>QUIC: A UDP-Based Multiplexed and Secure Transport</title>
            <author fullname="J. Iyengar" initials="J." role="editor" surname="Iyengar"/>
            <author fullname="M. Thomson" initials="M." role="editor" surname="Thomson"/>
            <date month="May" year="2021"/>
            <abstract>
              <t indent="0">This document defines the core of the QUIC transport protocol. QUIC provides applications with flow-controlled streams for structured communication, low-latency connection establishment, and network path migration. QUIC includes security measures that ensure confidentiality, integrity, and availability in a range of deployment circumstances. Accompanying documents describe the integration of TLS for key negotiation, loss detection, and an exemplary congestion control algorithm.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9000"/>
          <seriesInfo name="DOI" value="10.17487/RFC9000"/>
        </reference>
        <reference anchor="RFC9001" target="https://www.rfc-editor.org/info/rfc9001" quoteTitle="true" derivedAnchor="RFC9001">
          <front>
            <title>Using TLS to Secure QUIC</title>
            <author fullname="M. Thomson" initials="M." role="editor" surname="Thomson"/>
            <author fullname="S. Turner" initials="S." role="editor" surname="Turner"/>
            <date month="May" year="2021"/>
            <abstract>
              <t indent="0">This document describes how Transport Layer Security (TLS) is used to secure QUIC.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9001"/>
          <seriesInfo name="DOI" value="10.17487/RFC9001"/>
        </reference>
        <reference anchor="RFC9002" target="https://www.rfc-editor.org/info/rfc9002" quoteTitle="true" derivedAnchor="RFC9002">
          <front>
            <title>QUIC Loss Detection and Congestion Control</title>
            <author fullname="J. Iyengar" initials="J." role="editor" surname="Iyengar"/>
            <author fullname="I. Swett" initials="I." role="editor" surname="Swett"/>
            <date month="May" year="2021"/>
            <abstract>
              <t indent="0">This document describes loss detection and congestion control mechanisms for QUIC.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9002"/>
          <seriesInfo name="DOI" value="10.17487/RFC9002"/>
        </reference>
      </references>
      <references pn="section-11.2">
        <name slugifiedName="name-informative-references">Informative References</name>
        <reference anchor="RFC9308" target="https://www.rfc-editor.org/info/rfc9308" quoteTitle="true" derivedAnchor="RFC9308">
          <front>
            <title>Applicability of the QUIC Transport Protocol</title>
            <author fullname="M. Kühlewind" initials="M." surname="Kühlewind"/>
            <author fullname="B. Trammell" initials="B." surname="Trammell"/>
            <date month="September" year="2022"/>
            <abstract>
              <t indent="0">This document discusses the applicability of the QUIC transport protocol, focusing on caveats impacting application protocol development and deployment over QUIC. Its intended audience is designers of application protocol mappings to QUIC and implementors of these application protocols.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9308"/>
          <seriesInfo name="DOI" value="10.17487/RFC9308"/>
        </reference>
      </references>
    </references>
    <section anchor="Acknowledgements" numbered="false" removeInRFC="false" toc="include" pn="section-appendix.a">
      <name slugifiedName="name-acknowledgements">Acknowledgements</name>
      <t indent="0" pn="section-appendix.a-1">The authors wish to thank the following persons for their feedback
            and suggestions: <contact fullname="Scott Hollenbeck"/>, <contact fullname="Lucas Pardue"/>, <contact fullname="Martin Thomson"/>, <contact fullname="Mohamed Boucadair"/>, <contact fullname="Gorry Fairhurst"/>, and <contact fullname="Mahesh Jethanandani"/>.</t>
    </section>
    <section anchor="authors-addresses" numbered="false" removeInRFC="false" toc="include" pn="section-appendix.b">
      <name slugifiedName="name-authors-addresses">Authors' Addresses</name>
      <author fullname="Jiankang Yao" initials="J." surname="Yao">
        <organization showOnFrontPage="true">CNNIC</organization>
        <address>
          <postal>
            <street>4 South 4th Street, Zhongguancun, Haidian District</street>
            <city>Beijing</city>
            <code>100190</code>
            <country>China</country>
          </postal>
          <phone>+86 10 59116505</phone>
          <email>yaojk@cnnic.cn</email>
        </address>
      </author>
      <author fullname="Hongtao Li" initials="H." surname="Li">
        <organization showOnFrontPage="true">CNNIC</organization>
        <address>
          <postal>
            <street>4 South 4th Street, Zhongguancun, Haidian District</street>
            <city>Beijing</city>
            <code>100190</code>
            <country>China</country>
          </postal>
          <email>lihongtao@cnnic.cn</email>
        </address>
      </author>
      <author fullname="Man Zhang" initials="M." surname="Zhang">
        <organization showOnFrontPage="true">CNNIC</organization>
        <address>
          <postal>
            <street>4 South 4th Street, Zhongguancun, Haidian District</street>
            <city>Beijing</city>
            <code>100190</code>
            <country>China</country>
          </postal>
          <email>zhangman@cnnic.cn</email>
        </address>
      </author>
      <author fullname="Daniel Keathley" initials="D." surname="Keathley">
        <organization showOnFrontPage="true">VeriSign, Inc.</organization>
        <address>
          <postal>
            <street>12061 Bluemont Way</street>
            <city>Reston</city>
            <region>VA</region>
            <code>20190</code>
            <country>United States of America</country>
          </postal>
          <email>dkeathley@verisign.com</email>
          <uri>http://www.verisigninc.com</uri>
        </address>
      </author>
      <author fullname="James Gould" initials="J." surname="Gould">
        <organization showOnFrontPage="true">VeriSign, Inc.</organization>
        <address>
          <postal>
            <street>12061 Bluemont Way</street>
            <city>Reston</city>
            <region>VA</region>
            <code>20190</code>
            <country>United States of America</country>
          </postal>
          <email>jgould@verisign.com</email>
          <uri>http://www.verisigninc.com</uri>
        </address>
      </author>
    </section>
  </back>
</rfc>
