<?xml<?xml version="1.0" encoding="utf-8"?> encoding="UTF-8"?>

<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?rfc toc="yes"?>
<?rfc rfcedstyle="yes"?>
<?rfc subcompact="no"?>
<?rfc symrefs="yes"?> [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>

<rfc xmlns:xi="http://www.w3.org/2001/XInclude"
     ipr="trust200902"
     submissionType="IETF"
     category="std"
     docName="draft-ietf-extra-sieve-action-registry-06">
     consensus="true"
     docName="draft-ietf-extra-sieve-action-registry-06"
     number="9122"
     obsoletes=""
     updates=""
     xml:lang="en"
     tocInclude="true"
     symRefs="true"
     sortRefs="true"
     version="3">

  <!-- xml2rfc v2v3 conversion 3.17.0 -->
  <front>
    <title abbrev="IANA registry Registry for Sieve actions"> Actions">
      IANA registry Registry for Sieve actions Actions
    </title>
    <seriesInfo name="RFC" value="9122"/>
    <author initials="A." surname="Melnikov" fullname="Alexey Melnikov">
      <organization>Isode Ltd</organization>
      <address>
        <postal>
          <street>14 Castle Mews</street>
          <city>Hampton</city>
	        <region>Middlesex</region>
          <code>TW12 2NP</code>
	        <country>UK</country>
          <country>United Kingdom</country>
        </postal>
        <email>Alexey.Melnikov@isode.com</email>
      </address>
    </author>
    <author initials="K." surname="Murchison" fullname="Kenneth Murchison">
      <organization abbrev="Fastmail">Fastmail US LLC</organization>
      <address>
        <postal>
          <extaddr>Suite 1201</extaddr>
          <street>1429 Walnut Street - Suite 1201</street> Street</street>
          <city>Philadelphia</city>
          <region>PA</region>
          <code>19102</code>
          <country>USA</country>
          <country>United States of America</country>
        </postal>
        <email>murch@fastmailteam.com</email>
      </address>
    </author>
    <date year="2023" month="June" />
    <area>art</area>
    <workgroup>extra</workgroup>
    <keyword>Sieve</keyword>
    <abstract>
      <t>
        The Sieve Email Filtering Language (RFC 5228) is a popular email filtering language
        used upon final mail delivery.
        This document creates a registry of for Sieve (RFC 5228) actions in order to help developers and
        Sieve extension writers track interactions between different extensions.
      </t>
    </abstract>
  </front>
  <middle>
    <section title="Introduction"> numbered="true" toc="default">
      <name>Introduction</name>
      <t>
      The Sieve Email Filtering Language <xref target="RFC5228"/> target="RFC5228" format="default"/> is a popular email filtering language
      used upon final mail delivery. Popularity The popularity of Sieve resulted in a myriad of Sieve extensions
      that can interact with each other in wonderful and complex ways.
      There
      Currently, there is currently no easy way to find out all actions defined by Sieve extensions published
      in RFCs, which make makes it quite difficult for Sieve extension writers and Sieve implementation
      developers to forsee foresee interactions between Sieve actions.
      </t>
      <t>
      This document creates a registry of for Sieve <xref target="RFC5228"/> target="RFC5228" format="default"/> actions in order to help developers and
      Sieve extension writers track interactions between different extensions.
      </t>
    </section>
    <section title="IANA Considerations"> numbered="true" toc="default">
      <name>IANA Considerations</name>
      <section title="Sieve numbered="true" toc="default">
        <name>Sieve Actions Registration Template and Procedure"> Procedure</name>
        <t>
      IANA is requested to create a new has created the "Sieve Actions" registry for Sieve actions (see Section 2.9 of <xref target="RFC5228"/> target="RFC5228" section="2.9" sectionFormat="of"/>
      for details on Sieve actions). Registration of both actions specified in IETF Stream both RFCs
      and vendor specific actions vendor-specific documentation is allowed and encouraged.
      The registration template contains:

      <list style="numbers">
        <t>name contains the following:
        </t>
      <dl spacing="compact">
        <dt>Name:</dt><dd>Name of the action;</t>
        <t>short description;</t>
        <t>references: one action</dd>
        <dt>Description:</dt><dd>Short description</dd>
        <dt>References:</dt><dd>One or more documents describing the action and
   any significant updates to its definition (this field
   is required for actions described in RFCs and is optional otherwise);</t>
        <t>name(s)
   otherwise)</dd>
        <dt>Capabilities:</dt><dd>Name of one or more Sieve capabilit(ies) capabilities associated with the Sieve action being registered;</t>
        <t>interactions registered</dd>
        <dt>Action Interactions:</dt><dd>Interactions with other Sieve actions (as described in Section 2.10.1 of <xref target="RFC5228"/>), target="RFC5228" sectionFormat="of" section="2.10.1"/>), if any;</t>
        <t>flag any</dd>
        <dt>Cancels Implicit Keep?</dt><dd>Flag specifying whether the action cancels the implicit keep (see Section 2.10.2 of <xref target="RFC5228"/>);</t>
        <t>whether target="RFC5228" sectionFormat="of" section="2.10.2"/>)</dd>
        <dt>Can Use With IMAP Events?</dt><dd>Whether or not this action can be used with IMAP events in Sieve (<xref target="RFC6785"/>);</t>
        <t>optional comment.</t>
      </list>
      </t> <xref target="RFC6785"/></dd>
        <dt>Comments:</dt><dd>Optional comment or comments</dd>
      </dl>
        <t>
      Registration
      The registration procedure for this registry is Expert Review. Review <xref target="RFC8126"/>.
      The Designated Expert designated expert only checks that the name of the action being registered
      matches documentation, that the description field is accurate,
      that
      the correct documents are referenced referenced, and that the list of
      relevant documents is as complete as possible.
      The Designated Expert can’t designated expert can't reject a registration based on because of a personal dislike of for
      the document defining an action and should always err on the side of registering, approving the registration,
      even if documentation is not complete.
        </t>

      <t>
      Addition of
      <t>The same registration procedure is used to add a new reference to an existing registration
  or change to change the description field goes through
      the same registration procedure as a new registration.
      </t> of an existing registration.</t>
      </section>
      <section title="Initial anchor="initial-regs" numbered="true" toc="default">
        <name>Initial Sieve Action Registry" anchor="initial-regs"> Registry</name>
        <t>The following table is registrations are used to initialize the actions "Sieve Actions"
        registry. Note that when the relevant "Action Interactions" cell entry is empty marked "N/A", it means that there is no restriction
        on use of the corresponding action with any other action, however action; however, implementors still need to read
        the one or more corresponding specification(s) specifications to see determine if there is are any surprising behaviour. behaviors.
        Also note that the "Comments" field of the IANA registration template is omitted from this table, these registrations,
        as no registration none of them currently have any comment. comments.
        </t>

        <texttable>
          <ttcol>Name</ttcol>
          <ttcol>Description</ttcol>
          <ttcol>References</ttcol>
          <ttcol>Capabilities</ttcol>
          <ttcol>Action Interactions</ttcol>
          <ttcol>Cancels Implicit Keep?</ttcol>
          <ttcol>Can use with IMAP Events?</ttcol>

          <c>addheader</c>
          <c>Add
        <dl spacing="compact">
         <dt>Name:</dt><dd>addheader</dd>
         <dt>Description:</dt><dd>Add a header field to the existing message header</c>
          <c><xref target="RFC5293"/></c>
          <c>"editheader"</c>
          <c>All
header</dd>
         <dt>References:</dt><dd><xref target="RFC5293" format="default"/></dd>
         <dt>Capabilities:</dt><dd>"editheader"</dd>
         <dt>Action Interactions:</dt><dd>All subsequent tests and actions apply to the altered message</c>
          <c>No</c>
          <c>Yes</c>

          <c>addflag</c>
          <c>Add message</dd>
         <dt>Cancels Implicit Keep?</dt><dd>No</dd>
         <dt>Can Use with IMAP Events?</dt><dd>Yes</dd>
        </dl>

        <dl spacing="compact">
         <dt>Name:</dt><dd>addflag</dd>
         <dt>Description:</dt><dd>Add IMAP flags to a list of IMAP flags that would be set on the message if it gets delivered to a mailbox</c>
          <c><xref target="RFC5232"/>, <xref target="RFC5229"/></c>
          <c>"imap4flags", "variables"</c>
          <c/>
          <c>No</c>
          <c>Yes</c>

          <c>convert</c>
          <c>Convert mailbox</dd>
         <dt>References:</dt><dd><xref target="RFC5232" format="default"/> <xref target="RFC5229" format="default"/></dd>
         <dt>Capabilities:</dt><dd>"imap4flags", "variables"</dd>
         <dt>Action Interactions:</dt><dd>N/A</dd>
         <dt>Cancels Implicit Keep?</dt><dd>No</dd>
         <dt>Can Use with IMAP Events?</dt><dd>Yes</dd>
        </dl>

        <dl spacing="compact">
         <dt>Name:</dt><dd>convert</dd>
         <dt>Description:</dt><dd>Convert body parts from one MIME type to another</c>
          <c><xref target="RFC6558"/></c>
          <c>"convert"</c>
          <c>All another</dd>
         <dt>References:</dt><dd><xref target="RFC6558" format="default"/></dd>
         <dt>Capabilities:</dt><dd>"convert"</dd>
         <dt>Action Interactions:</dt><dd>All subsequent tests and actions apply to the altered message</c>
          <c>No</c>
          <c>Yes</c>

          <c>deleteheader</c>
          <c>Remove message</dd>
         <dt>Cancels Implicit Keep?</dt><dd>No</dd>
         <dt>Can Use with IMAP Events?</dt><dd>Yes</dd>
        </dl>

        <dl spacing="compact">
         <dt>Name:</dt><dd>deleteheader</dd>
         <dt>Description:</dt><dd>Remove a header field from the existing message header</c>
          <c><xref target="RFC5293"/></c>
          <c>"editheader"</c>
          <c>All header</dd>
         <dt>References:</dt><dd><xref target="RFC5293" format="default"/></dd>
         <dt>Capabilities:</dt><dd>"editheader"</dd>
         <dt>Action Interactions:</dt><dd>All subsequent tests and actions apply to the altered message</c>
          <c>No</c>
          <c>Yes</c>

          <c>discard</c>
          <c>Silently message</dd>
         <dt>Cancels Implicit Keep?</dt><dd>No</dd>
         <dt>Can Use with IMAP Events?</dt><dd>Yes</dd>
        </dl>

        <dl spacing="compact">
         <dt>Name:</dt><dd>discard</dd>
         <dt>Description:</dt><dd>Silently throw away the message</c>
          <c><xref target="RFC5228"/></c>
          <c/>
          <c/>
          <c>Yes</c>
          <c>Yes</c>

          <c>enclose</c>
          <c>Enclose message</dd>
         <dt>References:</dt><dd><xref target="RFC5228" format="default"/></dd>
         <dt>Capabilities:</dt><dd>N/A</dd>
         <dt>Action Interactions:</dt><dd>N/A</dd>
         <dt>Cancels Implicit Keep?</dt><dd>Yes</dd>
         <dt>Can Use with IMAP Events?</dt><dd>Yes</dd>
        </dl>

        <dl spacing="compact">
         <dt>Name:</dt><dd>enclose</dd>
         <dt>Description:</dt><dd>Enclose a message as an attachment to a new message</c>
          <c><xref target="RFC5703"/></c>
          <c>"enclose"</c>
          <c>All message</dd>
         <dt>References:</dt><dd><xref target="RFC5703" format="default"/></dd>
         <dt>Capabilities:</dt><dd>"enclose"</dd>
         <dt>Action Interactions:</dt><dd>All subsequent tests and actions, actions except "redirect" apply to the altered message</c>
          <c>No</c>
          <c>Yes</c>

          <c>ereject</c>
          <c>Refuse message</dd>
         <dt>Cancels Implicit Keep?</dt><dd>No</dd>
         <dt>Can Use with IMAP Events?</dt><dd>Yes</dd>
        </dl>

        <dl spacing="compact">
         <dt>Name:</dt><dd>ereject</dd>
         <dt>Description:</dt><dd>Refuse delivery of the message</c>
          <c><xref target="RFC5429"/></c>
          <c>"ereject"</c>
          <c>Incompatible message</dd>
         <dt>References:</dt><dd><xref target="RFC5429" format="default"/></dd>
         <dt>Capabilities:</dt><dd>"ereject"</dd>
         <dt>Action Interactions:</dt><dd>This action is incompatible with the "vacation" action. Typically is not permitted with actions that cause mail delivery, such as "keep", "fileinto", and "redirect".</c>
          <c>Yes</c>
          <c>No</c>

          <c>extracttext</c>
          <c>Store "redirect"</dd>
         <dt>Cancels Implicit Keep?</dt><dd>Yes</dd>
         <dt>Can Use with IMAP Events?</dt><dd>No</dd>
        </dl>

        <dl spacing="compact">
         <dt>Name:</dt><dd>extracttext</dd>
         <dt>Description:</dt><dd>Store text of a MIME part into a variable</c>
          <c><xref target="RFC5703"/>, <xref target="RFC5229"/></c>
          <c>"extracttext", "variables"</c>
          <c/>
          <c>No</c>
          <c>Yes</c>

          <c>fileinto</c>
          <c>Deliver variable</dd>
         <dt>References:</dt><dd><xref target="RFC5703" format="default"/> <xref target="RFC5229" format="default"/></dd>
         <dt>Capabilities:</dt><dd>"extracttext", "variables"</dd>
         <dt>Action Interactions:</dt><dd>N/A</dd>
         <dt>Cancels Implicit Keep?</dt><dd>No</dd>
         <dt>Can Use with IMAP Events?</dt><dd>Yes</dd>
        </dl>

        <dl spacing="compact">
         <dt>Name:</dt><dd>fileinto</dd>
         <dt>Description:</dt><dd>Deliver the message into the specified mailbox</c>
          <c><xref target="RFC5228"/>, <xref target="RFC3894"/>,
          <xref target="RFC5232"/>, <xref target="RFC5490"/>,
          <xref target="RFC9042"/>, <xref target="RFC8579"/></c>
          <c>"fileinto", mailbox</dd>
         <dt>References:</dt><dd><xref target="RFC5228" format="default"/> <xref target="RFC3894" format="default"/> <xref target="RFC5232" format="default"/> <xref target="RFC5490" format="default"/> <xref target="RFC9042" format="default"/> <xref target="RFC8579" format="default"/></dd>
         <dt>Capabilities:</dt><dd>"fileinto", "copy", "imap4flags", "mailbox", "mailboxid",
          "special-use"</c>
          <c>Use "special-use"</dd>
         <dt>Action Interactions:</dt><dd>Use of :copy suppresses cancelation cancellation of implicit keep</c>
          <c>Yes</c>
          <c>Yes</c>

          <c>keep</c>
          <c>File keep</dd>
         <dt>Cancels Implicit Keep?</dt><dd>Yes</dd>
         <dt>Can Use with IMAP Events?</dt><dd>Yes</dd>
        </dl>

        <dl spacing="compact">
         <dt>Name:</dt><dd>keep</dd>
         <dt>Description:</dt><dd>File the message into the user's main mailbox</c>
          <c><xref target="RFC5228"/>, <xref target="RFC5232"/></c>
          <c>"imap4flags"</c>
          <c/>
          <c>Yes</c>
          <c>Yes</c>

          <c>notify</c>
          <c>Send mailbox</dd>
         <dt>References:</dt><dd><xref target="RFC5228" format="default"/> <xref target="RFC5232" format="default"/></dd>
         <dt>Capabilities:</dt><dd>"imap4flags"</dd>
         <dt>Action Interactions:</dt><dd>N/A</dd>
         <dt>Cancels Implicit Keep?</dt><dd>Yes</dd>
         <dt>Can Use with IMAP Events?</dt><dd>Yes</dd>
        </dl>

        <dl spacing="compact">
         <dt>Name:</dt><dd>notify</dd>
         <dt>Description:</dt><dd>Send a notification to a user</c>
          <c><xref target="RFC5435"/>, <xref target="RFC8580"/></c>
          <c>"enotify", "fcc"</c>
          <c/>
          <c>No</c>
          <c>Yes</c>

          <c>redirect</c>
          <c>Send user</dd>
         <dt>References:</dt><dd><xref target="RFC5435" format="default"/> <xref target="RFC8580" format="default"/></dd>
         <dt>Capabilities:</dt><dd>"enotify", "fcc"</dd>
         <dt>Action Interactions:</dt><dd>N/A</dd>
         <dt>Cancels Implicit Keep?</dt><dd>No</dd>
         <dt>Can Use with IMAP Events?</dt><dd>Yes</dd>
        </dl>

        <dl spacing="compact">
         <dt>Name:</dt><dd>redirect</dd>
         <dt>Description:</dt><dd>Send (forward) the message to another user</c>
          <c><xref target="RFC5228"/>, <xref target="RFC3894"/>,
          <xref target="RFC6009"/>, <xref target="RFC6134"/></c>
          <c>"copy", user</dd>
         <dt>References:</dt><dd><xref target="RFC5228" format="default"/> <xref target="RFC3894" format="default"/> <xref target="RFC6009" format="default"/> <xref target="RFC6134" format="default"/></dd>
         <dt>Capabilities:</dt><dd>"copy", "redirect-dsn", "redirect-deliverby", "extlists"</c>
          <c>Use "extlists"</dd>
         <dt>Action Interactions:</dt><dd>Use of :copy suppresses cancelation cancellation of implicit keep</c>
          <c>Yes</c>
          <c>Yes</c>

          <c>reject</c>
          <c>Refuse keep</dd>
         <dt>Cancels Implicit Keep?</dt><dd>Yes</dd>
         <dt>Can Use with IMAP Events?</dt><dd>Yes</dd>
        </dl>

        <dl spacing="compact">
         <dt>Name:</dt><dd>reject</dd>
         <dt>Description:</dt><dd>Refuse delivery of the message</c>
          <c><xref target="RFC5429"/></c>
          <c>"reject"</c>
          <c>Incompatible message</dd>
         <dt>References:</dt><dd><xref target="RFC5429" format="default"/></dd>
         <dt>Capabilities:</dt><dd>"reject"</dd>
         <dt>Action Interactions:</dt><dd>This action is incompatible with the "vacation" action. Typically is not permitted with actions that cause mail delivery, such as "keep", "fileinto", and "redirect".</c>
          <c>Yes</c>
          <c>No</c>

          <c>removeflag</c>
          <c>Remove "redirect"</dd>
         <dt>Cancels Implicit Keep?</dt><dd>Yes</dd>
         <dt>Can Use with IMAP Events?</dt><dd>No</dd>
        </dl>

        <dl spacing="compact">
         <dt>Name:</dt><dd>removeflag</dd>
         <dt>Description:</dt><dd>Remove IMAP flags from a list of IMAP flags that would be set on the message if it gets delivered to a mailbox</c>
          <c><xref target="RFC5232"/>, <xref target="RFC5229"/></c>
          <c>"imap4flags", "variables"</c>
          <c/>
          <c>No</c>
          <c>Yes</c>

          <c>replace</c>
          <c>Replace mailbox</dd>
         <dt>References:</dt><dd><xref target="RFC5232" format="default"/> <xref target="RFC5229" format="default"/></dd>
         <dt>Capabilities:</dt><dd>"imap4flags", "variables"</dd>
         <dt>Action Interactions:</dt><dd>N/A</dd>
         <dt>Cancels Implicit Keep?</dt><dd>No</dd>
         <dt>Can Use with IMAP Events?</dt><dd>Yes</dd>
        </dl>

        <dl spacing="compact">
         <dt>Name:</dt><dd>replace</dd>
         <dt>Description:</dt><dd>Replace a MIME part</c>
          <c><xref target="RFC5703"/></c>
          <c>"replace"</c>
          <c>All part</dd>
         <dt>References:</dt><dd><xref target="RFC5703" format="default"/></dd>
         <dt>Capabilities:</dt><dd>"replace"</dd>
         <dt>Action Interactions:</dt><dd>All subsequent tests and actions, actions except "redirect" apply to the altered message</c>
          <c>No</c>
          <c>Yes</c>

          <c>set</c>
          <c>Store message</dd>
         <dt>Cancels Implicit Keep?</dt><dd>No</dd>
         <dt>Can Use with IMAP Events?</dt><dd>Yes</dd>
        </dl>

        <dl spacing="compact">
         <dt>Name:</dt><dd>set</dd>
         <dt>Description:</dt><dd>Store a value in a variable</c>
          <c><xref target="RFC5229"/></c>
          <c>"variables"</c>
          <c/>
          <c>No</c>
          <c>Yes</c>

          <c>setflag</c>
          <c>
          Set variable</dd>
         <dt>References:</dt><dd><xref target="RFC5229" format="default"/></dd>
         <dt>Capabilities:</dt><dd>"variables"</dd>
         <dt>Action Interactions:</dt><dd>N/A</dd>
         <dt>Cancels Implicit Keep?</dt><dd>No</dd>
         <dt>Can Use with IMAP Events?</dt><dd>Yes</dd>
        </dl>

        <dl spacing="compact">
         <dt>Name:</dt><dd>setflag</dd>
         <dt>Description:</dt><dd>Set IMAP system flags or keywords that would be set on the message if it gets delivered to a mailbox
          </c>
          <c><xref target="RFC5232"/>, <xref target="RFC5229"/></c>
          <c>"imap4flags", "variables"</c>
          <c/>
          <c>No</c>
          <c>Yes</c>

          <c>vacation</c>
          <c>Vacation autoresponder</c>
          <c><xref target="RFC5230"/>, <xref target="RFC6131"/>,
          <xref target="RFC8580"/></c>
          <c>"vacation", mailbox</dd>
         <dt>References:</dt><dd><xref target="RFC5232" format="default"/> <xref target="RFC5229" format="default"/></dd>
         <dt>Capabilities:</dt><dd>"imap4flags", "variables"</dd>
         <dt>Action Interactions:</dt><dd>N/A</dd>
         <dt>Cancels Implicit Keep?</dt><dd>No</dd>
         <dt>Can Use with IMAP Events?</dt><dd>Yes</dd>
        </dl>

        <dl spacing="compact">
         <dt>Name:</dt><dd>vacation</dd>
         <dt>Description:</dt><dd>Implement a vacation autoresponder</dd>
         <dt>References:</dt><dd><xref target="RFC5230" format="default"/> <xref target="RFC6131" format="default"/> <xref target="RFC8580" format="default"/></dd>
         <dt>Capabilities:</dt><dd>"vacation", "vacation-seconds", "fcc"</c>
          <c>
          Incompatible "fcc"</dd>
         <dt>Action Interactions:</dt><dd>This action is incompatible with "reject" and "ereject" actions.
          </c>
          <c>No</c>
          <c>No</c>

        </texttable> actions</dd>
         <dt>Cancels Implicit Keep?</dt><dd>No</dd>
         <dt>Can Use with IMAP Events?</dt><dd>No</dd>
        </dl>

      </section>
    </section>
    <section title="Security Considerations" anchor="seccons"> anchor="seccons" numbered="true" toc="default">
      <name>Security Considerations</name>
      <t>
      The sole purpose of this document is to create a new IANA registry,
      so the "Sieve Actions" registry;
      therefore, it doesn't create new security considerations for Sieve implementations.
      </t>
      <t>
      The new registry should help Sieve extension writers and Sieve implementors
      track interactions between different Sieve actions, so actions; therefore, it might improve the quality
      of specifications and implementations, including security aspects.
      </t>
      <t>
      For the Security Considerations of security considerations related to particular actions, see the RFC(s) one or more RFCs referenced
      for that the action in the Initial Sieve Action Registry question in <xref target="initial-regs"/>. the "Sieve Actions" registry (<xref target="initial-regs" format="default"/>).
      </t>
    </section>
  </middle>
  <back>
    <references title="Normative References">

      <!--<?rfc include="reference.RFC.2119"?>--> <!-- Keywords, part 1 -->
      <?rfc include="reference.RFC.5228"?> <!-- Sieve -->
      <?rfc include="reference.RFC.6785"?> <!-- IMAP Sieve -->
      <!--<?rfc include="reference.RFC.8174"?>--> <!-- Keywords, part 2 -->
    <references>
      <name>References</name>
      <references>
        <name>Normative References</name>
      <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5228.xml"/>
      <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6785.xml"/>
    </references>
      <references>
        <name>Informative References</name>
      <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3894.xml"/>
      <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5229.xml"/>
      <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5230.xml"/>
      <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5232.xml"/>
      <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5293.xml"/>
      <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5429.xml"/>
      <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5435.xml"/>
      <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5490.xml"/>
      <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5703.xml"/>
      <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6009.xml"/>
      <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6131.xml"/>
      <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6134.xml"/>
      <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6558.xml"/>
      <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8126.xml"/>
      <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8579.xml"/>
      <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8580.xml"/>
      <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9042.xml"/>

    </references>

    <references title="Informative References">

      <?rfc include="reference.RFC.3894"?> <!-- Copy -->
      <?rfc include="reference.RFC.5229"?> <!-- Variables -->
      <?rfc include="reference.RFC.5230"?> <!-- Vacation -->
      <?rfc include="reference.RFC.5232"?> <!-- Imap4Flags -->
      <?rfc include="reference.RFC.5293"?> <!-- Editheader -->
      <?rfc include="reference.RFC.5429"?> <!-- [Extended] Reject -->
      <?rfc include="reference.RFC.5435"?> <!-- Notify -->
      <?rfc include="reference.RFC.5490"?> <!-- Mailbox -->
      <?rfc include="reference.RFC.5703"?> <!-- MIME -->
      <?rfc include="reference.RFC.6009"?> <!-- DSN / Deliver-By -->
      <?rfc include="reference.RFC.6131"?> <!-- Vacation-Seconds -->
      <?rfc include="reference.RFC.6134"?> <!-- Externally Stored Lists -->
      <?rfc include="reference.RFC.6558"?> <!-- Convert -->
      <?rfc include="reference.RFC.8579"?> <!-- Special-Use -->
      <?rfc include="reference.RFC.8580"?> <!-- FCC -->
      <?rfc include="reference.RFC.9042"?> <!-- Mailbox ID -->
    </references>

    <section title="Acknowledgements">

      <!-- numbered="true" toc="default">
      <name>Acknowledgements</name>
      <t>
      Thank you to XXX <contact fullname="Barry Leiba"/>, <contact fullname="Donald Eastlake"/>, <contact fullname="Yoshiro Yoneya"/>, and <contact fullname="Murray Kucherawy"/> for comments reviews and feedback on this document.
      </t>
      -->

      <t>TBD.</t>
    </section>
  </back>
</rfc>