<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.43 (Ruby 3.4.12) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-ietf-mailmaint-smtputf8-syntax-07" category="std" consensus="true" submissionType="IETF" xml:lang="en" updates="6532" version="3">
  <!-- xml2rfc v2v3 conversion 3.35.0 -->
  <front>
    <title>SMTPUTF8 Email Addresses</title>
    <seriesInfo name="Internet-Draft" value="draft-ietf-mailmaint-smtputf8-syntax-07"/>
    <author initials="A." surname="Gulbrandsen" fullname="Arnt Gulbrandsen">
      <organization>ICANN</organization>
      <address>
        <postal>
          <street>6 Rond Point Schumann, Bd. 1</street>
          <city>Brussels</city>
          <code>1040</code>
          <country>Belgium</country>
        </postal>
        <email>arnt@gulbrandsen.priv.no</email>
      </address>
    </author>
    <author initials="J." surname="Yao" fullname="Jiankang Yao">
      <organization>CNNIC</organization>
      <address>
        <postal>
          <street>No.4 South 4th Zhongguancun Street</street>
          <city>Beijing</city>
          <code>100190</code>
          <country>China</country>
        </postal>
        <email>yaojk@cnnic.cn</email>
      </address>
    </author>
    <date year="2026" month="November" day="16"/>
    <area>Applications and Real-Time</area>
    <workgroup>mailmaint</workgroup>
    <keyword>email</keyword>
    <abstract>
      <?line 66?>

<t>This document updates the email address syntax to include the
addresses in active use, include the addresses likely to be used based
on what writing systems are used together, and exclude addresses that
pose risks when recipient software renders or processes them.</t>
    </abstract>
    <note removeInRFC="true">
      <name>Discussion Venues</name>
      <t>Discussion of this document takes place on the
    Mail Maintenance Working Group mailing list (mailmaint@ietf.org),
    which is archived at <eref target="https://mailarchive.ietf.org/arch/browse/mailmaint/"/>.</t>
      <t>Source for this draft and an issue tracker can be found at
    <eref target="https://github.com/arnt/mailmaint-smtputf8"/>.</t>
    </note>
  </front>
  <middle>
    <?line 73?>

<section anchor="introduction">
      <name>Introduction</name>
      <t><xref target="RFC6531"/> extends SMTP and <xref target="RFC6532"/> extends message syntax to
support non-ASCII both in localparts and domain parts. In addition,
some email software supports Unicode in domain parts by using encoded
domain parts in the SMTP transaction ("RCPT TO:<eref target="mailto:info@xn--dmi-0na.fo">info@xn--dmi-0na.fo</eref>")
and presenting the Unicode version (dømi.fo in this case) in the user
interface.</t>
      <t>The email address syntax extension in <xref target="RFC6532"/> allows almost all
UTF-8 strings as localparts. While this certainly allows everything
users want to use, it is also flexible enough to allow many things
that users and implementers find surprising and sometimes worrying.
For example, the domain extracted by code may not match that shown to
users on-screen.</t>
      <t>This document defines rules that allow the addresses currently used
and the addresses that users and implementers have asked for. It
disallows addresses that cause confusing rendering, including many
instances of homographic rendering. It does not try to disallow
anything that is already disallowed by IDNA (see <xref target="RFC5891"/>) or
by common registry policies (see <xref target="IDN-TABLES"/>).</t>
    </section>
    <section anchor="requirements-language">
      <name>Requirements Language</name>
      <t>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"/> <xref target="RFC8174"/> when, and only when, they
appear in all capitals, as shown here.</t>
      <?line -18?>

</section>
    <section anchor="terminology">
      <name>Terminology</name>
      <t>Script, in this document, refers to the Unicode script property (see
<xref target="UAX24"/>). Each code point is assigned to one script ("a" is Latin),
except that some are assigned to "Common" or a few other special
values. "Latin" and "Cyrillic" are examples of scripts.</t>
      <t>Latin refers to those code points that have the script property "Latin"
in Unicode. Orléans in France and Münster in Germany both have Latin
names in this document. It also refers to combinations of those code
points and combining characters, and to strings that contain no code
points from other scripts.</t>
      <t>Han, Cyrillic etc. refer to those code points that have the respective
script property in Unicode, as well as to strings that contain no code
points from other scripts.</t>
      <t>ASCII refers to the first 128 code points within Unicode, which
includes the letters A-Z but not É or Ü. It also refers to strings
that contain only ASCII code points.</t>
      <t>Non-ASCII refers to Unicode code points except the first 128, and also
to strings that contain at least one such code point.</t>
      <t>By way of example, the address info@dømi.fo is Latin and non-ASCII,
its localpart is Latin and ASCII, and its domain part is Latin and
non-ASCII. 中国 is a Han string in this document, but 阿Q正传 is
neither a Latin string nor a Han string, because it contains a Latin Q
and three Han code points.</t>
      <t>The term A-label is defined in <xref target="RFC5890"/> section 2.3.2.1.</t>
      <t>PRECIS is described in <xref target="RFC8264"/>, and the IdentifierClass in section
4.2 of that document.</t>
    </section>
    <section anchor="rules">
      <name>Rules</name>
      <t>The following four rules apply to the
<xref target="I-D.ietf-emailcore-rfc5322bis"/> mailbox production, as indirectly
extended by <xref target="RFC6532"/>.</t>
      <ol spacing="normal" type="1"><li>
          <t>An atom in an address <bcp14>MUST NOT</bcp14> be an A-label (e.g. xn--dmi-0na).</t>
        </li>
        <li>
          <t>An address <bcp14>MUST</bcp14> contain only code points that the PRECIS
IdentifierClass treats as valid, and the U+0020 space. Where the
IdentifierClass requires a contextual rule, the address <bcp14>MUST</bcp14> satisfy
that rule (defined in <xref target="RFC8264"/> and described in depth in
<xref target="RFC5892"/> Appendix A).</t>
        </li>
        <li>
          <t>An address <bcp14>MUST NOT</bcp14> contain more than one script, when ASCII is
disregarded. Three groups of scripts are permitted: Han, Hiragana and Katakana, Han and Hangul, and finally Han and Bopomofo. (For example: In the word
Orléans, Orl and ans are ASCII and é is non-ASCII. Disregarding ASCII
leaves a single é, necessarily a single script, so the word contains
only one script. Another example: まり子 is Hiragana and Han, which
count as one.)</t>
        </li>
        <li>
          <t>An address <bcp14>MUST</bcp14> be in the Unicode NFC form (see <xref target="UAX15"/>).</t>
        </li>
      </ol>
      <t>These rules do not affect rules in other documents. Most notably, the
domain-name production in an in email addresses is almost always also
a domain names on the public internet, which implies that the rules
specified by <xref target="RFC952"/>, <xref target="RFC5891"/> and others affect email
addresses. Domain registries often have policies regarding which names
may be registered.</t>
      <t>These rules constrain how to generate email addresses in email
messages. This document does not require receivers to reject, alter
or normalize non-conforming addresses.</t>
    </section>
    <section anchor="examples">
      <name>Examples</name>
      <t>example@example.com is permitted, because 1) it does not contain any
A-label, 2) it consists entirely of permissible code points, 3) it
contains no non-ASCII code points at all and 4) it is in NFC form.</t>
      <t>The address dømi@dømi.fo is permitted, because 1) it does not contain
any A-label, 2) the IdentifierClass permits every code point in it, 3)
it consists entirely of 'Latin' and 'Common' code points and 4) it is
in NFC form.</t>
      <t>The address U+200E '@' U+200F '.' U+200E is not permitted, because 2)
the IdentifierClass disallows U+200E and U+200F as ignorable code
points.</t>
      <t>The address 'admin' U+3164 '@example.com' is not permitted for the
same reason. U+3164 HANGUL FILLER renders as nothing at all, so the
address looks exactly like admin@example.com.</t>
      <t>The address まり子@まり子.日本 is permitted, because 1) it contains no
A-label, 2) the IdentifierClass permits every code point in it, 3)
Hiragana and Han count as one script and 4) it is in NFC form.</t>
      <t>阿Q正传@阿Q正传.example is permitted because it contains ASCII and Han,
dømi@dømi.fo is permitted because it contains ASCII and Latin, but
阿Q正传@dømi.fo is not, because it contains both Han (阿) and Latin
non-ASCII (ø), and 지훈@まり子.日本 is not because contains both
Hangul and Hiragana.</t>
      <t>example@-example-.example.com is permitted by the rules above.
However, since <xref target="RFC952"/> and its successors prohibit both of the
hyphens, that email address is effectively not permitted on the
internet.</t>
    </section>
    <section anchor="old-stored-messages">
      <name>Old stored messages</name>
      <t>This section is informative.</t>
      <t>A mailstore may contain old messages that do not conform to the rules
of this document, or indeed any RFC. Two typical examples may be To:
info@xn--dmi-0na.fo and To: =?ISO-8859-1?Q?info@d=F8mi.fo?=. A more
confusing example is "ali" U+202E "moc.elpmaxe@kravdraa.ec", which could
be rendered as alice.aardvark@example.com (U+202E changes display
direction). It is advisable to be careful about how to display an
address to users if that address does not conform to the rules in this
document.</t>
    </section>
    <section anchor="relationships-to-other-rfcs">
      <name>Relationships to other RFCs</name>
      <t>This section is informative.</t>
      <t>This document does not update <xref target="RFC6531"/>. This is because the ABNF in
<xref target="RFC6531"/> permits everything this document needs, and the
restrictions in this document are not needed within SMTP. (For
example, while a human recipient might be confused by a homograph
attack or a hard-to-read A-label, a receiving SMTP server can hardly
be.)</t>
      <t>However, a program that acts as an SMTP client is almost inevitably
affected. This document requires such program to ensure that the
addresses used in the message (To, Cc etc) are normalised. In a large
majority of cases, the addresses in To/Cc are also used in RCPT
TO. Whether this document updates <xref target="RFC6531"/> formally or merely
affects all implementations is a good question.</t>
      <t>If it updatesthe document, then this document should perhaps say
something like "the SMTP server <bcp14>MAY</bcp14> normalize addresses when looking
up a destination to perform delivery, but is not required to".</t>
    </section>
    <section anchor="IANA">
      <name>IANA Considerations</name>
      <t>This document does not require any actions from the IANA.</t>
    </section>
    <section anchor="SECURITY">
      <name>Security Considerations</name>
      <t>When a program renders a non-ASCII email address string on-screen or
stores it as a string (e.g. as part of a line of text in a system log
file), the address eventually shown to a human may not be as desired.
One possible way to diminish the risk is to replace impermissible code
points with U+FFFD, REPLACEMENT CHARACTER. There are also other
options. Note that changing an entire email message in this way risks
invalidating signatures such as DKIM.</t>
      <t>The rules in this document permit a number of code points that can
make an address difficult to cut and paste.</t>
      <t><xref target="RFC5321"/> section 4.1.2 advises those who define mailboxes to avoid
case-sensitive localparts, and <xref target="RFC6530"/> section 10.1 advises them to
support other normalization forms of the same localpart. <xref target="RFC8264"/>
section 5.2.3 discusses some options for case mapping. When processing
addresses in remote domains, one cannot be sure which conversion rules
apply. Implementers may want to consider unusual cases such as the
Turkish dotless ı.</t>
    </section>
  </middle>
  <back>
    <references anchor="sec-combined-references">
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>
        <reference anchor="I-D.ietf-emailcore-rfc5322bis">
          <front>
            <title>Internet Message Format</title>
            <author fullname="Pete Resnick" initials="P." surname="Resnick">
              <organization>Episteme Technology Consulting LLC</organization>
            </author>
            <date day="13" month="June" year="2024"/>
            <abstract>
              <t>   This document specifies the Internet Message Format (IMF), a syntax
   for text messages that are sent between computer users, within the
   framework of "electronic mail" messages.  This specification is a
   revision of Request For Comments (RFC) 5322, itself a revision of
   Request For Comments (RFC) 2822, all of which supersede Request For
   Comments (RFC) 822, "Standard for the Format of ARPA Internet Text
   Messages", updating it to reflect current practice and incorporating
   incremental changes that were specified in other RFCs.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-emailcore-rfc5322bis-12"/>
        </reference>
        <reference anchor="RFC5890">
          <front>
            <title>Internationalized Domain Names for Applications (IDNA): Definitions and Document Framework</title>
            <author fullname="J. Klensin" initials="J." surname="Klensin"/>
            <date month="August" year="2010"/>
            <abstract>
              <t>This document is one of a collection that, together, describe the protocol and usage context for a revision of Internationalized Domain Names for Applications (IDNA), superseding the earlier version. It describes the document collection and provides definitions and other material that are common to the set. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5890"/>
          <seriesInfo name="DOI" value="10.17487/RFC5890"/>
        </reference>
        <reference anchor="RFC5892">
          <front>
            <title>The Unicode Code Points and Internationalized Domain Names for Applications (IDNA)</title>
            <author fullname="P. Faltstrom" initials="P." role="editor" surname="Faltstrom"/>
            <date month="August" year="2010"/>
            <abstract>
              <t>This document specifies rules for deciding whether a code point, considered in isolation or in context, is a candidate for inclusion in an Internationalized Domain Name (IDN).</t>
              <t>It is part of the specification of Internationalizing Domain Names in Applications 2008 (IDNA2008). [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5892"/>
          <seriesInfo name="DOI" value="10.17487/RFC5892"/>
        </reference>
        <reference anchor="RFC6531">
          <front>
            <title>SMTP Extension for Internationalized Email</title>
            <author fullname="J. Yao" initials="J." surname="Yao"/>
            <author fullname="W. Mao" initials="W." surname="Mao"/>
            <date month="February" year="2012"/>
            <abstract>
              <t>This document specifies an SMTP extension for transport and delivery of email messages with internationalized email addresses or header information. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6531"/>
          <seriesInfo name="DOI" value="10.17487/RFC6531"/>
        </reference>
        <reference anchor="RFC6532">
          <front>
            <title>Internationalized Email Headers</title>
            <author fullname="A. Yang" initials="A." surname="Yang"/>
            <author fullname="S. Steele" initials="S." surname="Steele"/>
            <author fullname="N. Freed" initials="N." surname="Freed"/>
            <date month="February" year="2012"/>
            <abstract>
              <t>Internet mail was originally limited to 7-bit ASCII. MIME added support for the use of 8-bit character sets in body parts, and also defined an encoded-word construct so other character sets could be used in certain header field values. However, full internationalization of electronic mail requires additional enhancements to allow the use of Unicode, including characters outside the ASCII repertoire, in mail addresses as well as direct use of Unicode in header fields like "From:", "To:", and "Subject:", without requiring the use of complex encoded-word constructs. This document specifies an enhancement to the Internet Message Format and to MIME that allows use of Unicode in mail addresses and most header field content.</t>
              <t>This specification updates Section 6.4 of RFC 2045 to eliminate the restriction prohibiting the use of non-identity content-transfer- encodings on subtypes of "message/". [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6532"/>
          <seriesInfo name="DOI" value="10.17487/RFC6532"/>
        </reference>
        <reference anchor="RFC8264">
          <front>
            <title>PRECIS Framework: Preparation, Enforcement, and Comparison of Internationalized Strings in Application Protocols</title>
            <author fullname="P. Saint-Andre" initials="P." surname="Saint-Andre"/>
            <author fullname="M. Blanchet" initials="M." surname="Blanchet"/>
            <date month="October" year="2017"/>
            <abstract>
              <t>Application protocols using Unicode code points in protocol strings need to properly handle such strings in order to enforce internationalization rules for strings placed in various protocol slots (such as addresses and identifiers) and to perform valid comparison operations (e.g., for purposes of authentication or authorization). This document defines a framework enabling application protocols to perform the preparation, enforcement, and comparison of internationalized strings ("PRECIS") in a way that depends on the properties of Unicode code points and thus is more agile with respect to versions of Unicode. As a result, this framework provides a more sustainable approach to the handling of internationalized strings than the previous framework, known as Stringprep (RFC 3454). This document obsoletes RFC 7564.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8264"/>
          <seriesInfo name="DOI" value="10.17487/RFC8264"/>
        </reference>
        <reference anchor="UAX15" target="https://www.unicode.org/reports/tr15">
          <front>
            <title>Unicode Normalization Forms</title>
            <author initials="K." surname="Whistler" fullname="Ken Whistler">
              <organization/>
            </author>
            <date year="2026" month="August" day="12"/>
          </front>
        </reference>
        <reference anchor="UAX24" target="https://unicode.org/reports/tr24">
          <front>
            <title>Unicode Script Property</title>
            <author initials="K." surname="Whistler" fullname="Ken Whistler">
              <organization/>
            </author>
            <date year="2026" month="August" day="28"/>
          </front>
        </reference>
        <reference anchor="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>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="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>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>
      </references>
      <references anchor="sec-informative-references">
        <name>Informative References</name>
        <reference anchor="RFC952">
          <front>
            <title>DoD Internet host table specification</title>
            <author fullname="K. Harrenstien" initials="K." surname="Harrenstien"/>
            <author fullname="M.K. Stahl" initials="M.K." surname="Stahl"/>
            <author fullname="E.J. Feinler" initials="E.J." surname="Feinler"/>
            <date month="October" year="1985"/>
            <abstract>
              <t>This RFC is the official specification of the format of the Internet Host Table. This edition of the specification includes minor revisions to RFC-810 which brings it up to date.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="952"/>
          <seriesInfo name="DOI" value="10.17487/RFC952"/>
        </reference>
        <reference anchor="RFC5321">
          <front>
            <title>Simple Mail Transfer Protocol</title>
            <author fullname="J. Klensin" initials="J." surname="Klensin"/>
            <date month="October" year="2008"/>
            <abstract>
              <t>This document is a specification of the basic protocol for Internet electronic mail transport. It consolidates, updates, and clarifies several previous documents, making all or parts of most of them obsolete. It covers the SMTP extension mechanisms and best practices for the contemporary Internet, but does not provide details about particular extensions. Although SMTP was designed as a mail transport and delivery protocol, this specification also contains information that is important to its use as a "mail submission" protocol for "split-UA" (User Agent) mail reading systems and mobile environments. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5321"/>
          <seriesInfo name="DOI" value="10.17487/RFC5321"/>
        </reference>
        <reference anchor="RFC5891">
          <front>
            <title>Internationalized Domain Names in Applications (IDNA): Protocol</title>
            <author fullname="J. Klensin" initials="J." surname="Klensin"/>
            <date month="August" year="2010"/>
            <abstract>
              <t>This document is the revised protocol definition for Internationalized Domain Names (IDNs). The rationale for changes, the relationship to the older specification, and important terminology are provided in other documents. This document specifies the protocol mechanism, called Internationalized Domain Names in Applications (IDNA), for registering and looking up IDNs in a way that does not require changes to the DNS itself. IDNA is only meant for processing domain names, not free text. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5891"/>
          <seriesInfo name="DOI" value="10.17487/RFC5891"/>
        </reference>
        <reference anchor="RFC6530">
          <front>
            <title>Overview and Framework for Internationalized Email</title>
            <author fullname="J. Klensin" initials="J." surname="Klensin"/>
            <author fullname="Y. Ko" initials="Y." surname="Ko"/>
            <date month="February" year="2012"/>
            <abstract>
              <t>Full use of electronic mail throughout the world requires that (subject to other constraints) people be able to use close variations on their own names (written correctly in their own languages and scripts) as mailbox names in email addresses. This document introduces a series of specifications that define mechanisms and protocol extensions needed to fully support internationalized email addresses. These changes include an SMTP extension and extension of email header syntax to accommodate UTF-8 data. The document set also includes discussion of key assumptions and issues in deploying fully internationalized email. This document is a replacement for RFC 4952; it reflects additional issues identified since that document was published. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6530"/>
          <seriesInfo name="DOI" value="10.17487/RFC6530"/>
        </reference>
        <reference anchor="IDN-TABLES" target="https://www.iana.org/domains/idn-tables">
          <front>
            <title>Repository of IDN Practices</title>
            <author>
              <organization>IANA</organization>
            </author>
            <date>n.d.</date>
          </front>
        </reference>
      </references>
    </references>
    <?line 283?>

<section anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>The authors wish to thank John C. Klensin,
Daniel Eggert, Andrew Gallagher, Jeffrey Stedfast, Pete Resnick,
Narendra Singh Bisht, Collin Anderson
(your name here, please)</t>
      <t>(Wow, the ack section is already outdated)</t>
      <t>Dømi.fo and 例子.中国 are reserved by nic.fo and CNNIC for use in
examples and documentation.</t>
      <t>阿Q正传 is a famous Chinese novella, 阿Q is the main character.</t>
    </section>
    <section anchor="instructions-to-the-rfc-editor">
      <name>Instructions to the RFC editor</name>
      <t>Please remove the Open Issues section.</t>
      <t>This document uses the form U+0020 to refer to Unicode code points.
Please change that to the form most commonly used in newish RFCs — or
leave it if there is no dominant form. I'm too lazy to count today.</t>
    </section>
    <section anchor="testing">
      <name>Testing</name>
      <t>This is a set of test addresses in JSON format.</t>
      <t>Below is a verbatim copy of
https://github.com/arnt/mailmaint-smtputf8/blob/main/tests.json as it was
on (date here). It contains a number of strange and unusual code points, so
cutting and pasting this may not work. Rather, it is recommended to
either use the rfcstrip tool or download the tests using a command
such as curl
https://raw.githubusercontent.com/arnt/mailmaint-smtputf8/main/tests.json
&gt; tests.json.</t>
      <t>Note to IETF reviewers: The tests will be included here shortly before
publication (and after IETF Last Call).</t>
    </section>
    <section anchor="open-issues">
      <name>Open issues</name>
      <ol spacing="normal" type="1"><li>
          <t>Update 6531?</t>
        </li>
      </ol>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA61a328kx3F+77+is34gae/Ocfd4Zx4h6W5vj9RR4pEncglF
DoKgd6Z3d46z0+PpGe6thQPsPOXHSx4CJID9YCAIAgHRQ9704DhALn9JLAsI
kPwP+aq65xfJO9tIBEncne0fVdVVX31VPYPBQNhCpdGfqcSk+kAWealFnOX8
yRaj3d1HuyMRquJA2iISZRapQtsD+fDB/ZGw5WwVWxubtNhkmHx8OD0SKtfq
QPbGWZbEmIcfrcQG8lyrZDCNV7on1osDuVJxgv/SQojIhKlaYX6Uq3kxiHUx
H9Q/D+yqyMpivj+wm7RQrwe7PxSiiIsE4y9eTF9eTo/25SENl+MoyrW12opE
pdhCp+JqfSCkHEhNA4Qqi6XJD8RAuv3GeVrIj8tklkNAi+FSmhwTjyfj01N8
sUWuNTR/KM8NNHhpII+8CJflSqVpXz6NAjnEsDAuNgfyKexldWLpgYmw+nB3
b5e/lGmR0wCdLOJyhUcszYFU2P7Jotk+yPL4OkhNLd8nsUqvoIr8QplKtsnp
6fGkJdupCfbkhYFmcg///Whp0sWiVGlYpvKCxzQS6vhVnC5aAu4OH3VEnCzj
VDUCbpR5dfUkTNM4DMJUiNTkK5zotSajHg+eBXxUPDg0uR7k8xBuMZrFlgac
H00e7D/abT6O/Ef4zrD5WD3dHz3co4+X4z8ePqAPUhYqX5COy6LI7MG9e+v1
OighDKQPYIx7uc5MXth7RT584CY4v7h0Y2AbyJvEP2EvlEf4ZnkY+fCBHO2O
Hg529wfDET+snEPyPwP/V/qj+FSn8vNlbLF+7oQc7d0t5N0CjvbuEvAizOOs
kC9zk+m82Nwh3Gj/DxVOxOm8fU4w7aMHlZFh7mFzIK1T4GM6fnY6mI6fnhxe
vNv+cEnFukWG4tPei6N0UKhZom1bw3NobuPC5Btp5rQwlFRhEYd+2LsUcvE3
Ph0LMRgMpJrBzzFPiCn0k0CKcqURhB6HZLHUzlmlcsEvHUrIwsg4DZMSRsYY
oSpowFNJclxrWVrdbw+SzaAkvtLJhhaZ8bhIzhT+L+BF66Uq5DqPC0QSNrOF
XgHfcj+sMDDYUud9hjz92i3eLFxgtoBltMxje2WxGo4u12GcxaSWNfNiTYvl
Oo10bmEOmeUmrCbrVeDssoqjKNFCfE8eI3JNVIbk4kJ8+aWPrzdvsHuBVSyj
JItT/Thq/bjC0mqhG7MB1DNyWpmadDC+mBwfy5kBsMBuiQlVkik4NC/nHEDy
gwBykJoxidEX1qyqc6lV8uva2vkxt72EnG1gQ7KqTun3SHR+xQc6I1YGLpFa
xSrL7d755OVUTs8OPiDHf/I6HQyiVTzYhZvOzUe9HUGyZrA/DEyr0yqVCNew
MS8Svf1mFWO82waeFuK8d6pNcbQ5wqrQ+VyFOiBnfIfbsVl5SUxt21sliVnD
bsnK2IK+CSSuwT7BOITCD7Zl3oCiOdFeEiADzAB39GtoSL3BT0ByEgxOpOA6
8FXn0IWMaR9r5DzRr2MEJgxqysWShvASyL3pRvIKVpBHSrcOGSpeZYmmEKMH
8xhPbJkjL/HB0AA62gJZHNuaPN/gcSCArNBc0dQ+G8yfHKxBwUvhs+Gcg503
cKwCf4twydEg7dKsU3I8JwS8zoZIW2lwM+YjDXmwb14mPpK8Ot3YDcsc0VMk
G45IPv3ugPdpvFQABmWvIDJAFF5diCi21eF1lwgVFoFa6dy5rYtZfKpQhR6S
qeE6xLEQxYSFS7Myi1xlyzhsptBO0BQjyDrIxXRY1c7QwZ2325ePFyQr2tQj
nIWBsmO5bbV2nkcA/+bNDjBEsPlXK0NYs0CewPqZAT2LsaGf0GA/5gSELOf6
x2Wcs2msPAENKQEUzvev9IaOH/jRe3F5Me313V95esafzw8/uzw+P3xGny+e
j09O6g/Cj7h4fnZ58qz51MycnL14cXj6zE3GU9l5JHovxl/0HLr2zl5Oj89O
xye9OmprXyHAcejNYYvwJy9UVkQa3hXP8AVznk5e/vsvh3vQ/o9gr9Fw+AiR
6r7sD3+4hy+Ez243QxHovsKdNkJlmVY5p5MkgS9kcYGg61MgO49GFiCo+P6f
kGX+9EB+MAuz4d5H/gEp3HlY2azzkG12+8mtyc6Idzy6Y5vamp3nNyzdlXf8
Red7ZffWww8eJ4hNORjuP/5IkPNMdb6KU5OYxUYIR3P6t46pD3ecU9jhqNqw
bB0tyjwtYhdFamPSRd4pDxXQg4dmzMkpJFCHLFJOwTireo3tnurRzyfgQ+lO
XyAlazx2yENZijylPbc34UDpUepVcq7X0lBClzZDllaJuFZJqYHQPV6x5zxx
ssnjBPHU4+U8FHK0OzEsHIHHdxQ2DB+VEh5VGIHIGDeN4DcEmFR2CuRZnrz9
CrmQLHuUE8SwPC/e/gqIo9k7P8ZBENxzEufFeR1BzNHeOhHGIU4ejaBAjhnK
AlfJQaVGcOEFpz3dKAKpcKkY9XPrIgdLVFnO4SbKRcoOqeksMs/NqrJ1bbTn
CvFWWVfqIgycYL+PAYHVODOieuKmLRsbcsCuNUJY2f+TpI4qdf15HudI9sPR
fkfKdUxg3giwRiZYCk9EHaVNdMHpaDz4kZyVBSeFt39JLvn2F3cdkZdadKRm
xHJitbaHqKc1s2tWqEKvLWgdKy1N3JHS9uJd1sLHRCsM5zAsO5GK3Z8CRhVX
BR3KUBEpJnENHfORy7vWjLQv4qLFl7qj3AiX2gvbppidcaJeLZDffvP1b3/+
r4wiEh7n1boDrugs/uvv/+2z777+h29/9UtMEKmO2RGUX9lPTRk9mrUwVTu+
ENeGsvWkzzxLAe3hOd3jooQLb1jBGxI10wnJ6bhQVLNMKrSRrqx2pHgU3A9G
wRCTXwLUjy/clFbm40lUcb9544MUmxxHRJHnsc4nieKjqBYUe8HIhb4qGqxg
kkBkzMk4N0RFSPu5KXNP05AmXSFFVRhYxvuaBlCAns7Ma4pUX9NwgIKHgomE
IHXCFS6O8LQINoQZBnJM3ofg5COuXarKt0QH8Lgy47YOwLta9QLRnpFbpD2z
E0+34IYM54wsbtqvAEkrmNojacRRY+jLH+zujnaRUqiaANfXuatSby6QOwZG
jkJCQPVSJWzYbsywmBauZOcbhwE0BlXNDS9xB+6Kt7Y3RAhzqvBE5UtUsYxB
cGD213JMdrl/2y5k0co2K8MqqLSVe/uuunVIg1ABWQX7VDkOL5BTdvZFbsqs
nSc5f2bEHQCA0YFk/H8e52qhUsWCf6oKdYUvfY4UevKcqGnirAt9Qcc29W9P
TQa6PTeB3G4VKQdUrZIBicOKKon2KZ06eEudIE50evL2KwqhFmQ8q5Qhf+dn
AqB3zWdF1QDM//arvkw11e4K+WvT/FCZx5paiBoTBHtZY0Qyu0s1tey/+dmv
f/Pnf/Xbr/+GROrYhq3l0gm39Mj1sFSwIxDAt86PyXGHd50eTajsWVU1Abfi
XDmAAKemBcd0ZDghqfkcIemfUXywmBU6gCK9oFIXI9Us2bDD+op+QNyjFeI+
XKlgbNfUtGqrYkbScHWtUBWoOw5jnBJZOSOOwHw/1YU3BJd3sW4FK8srmM4h
0hocefRgRGDYKp0c7yetbKWs7yNXAsIPnCS+rIqZ9AGgHAupa6zGVZxQLLig
Ynim/VxgQHTDzvAJ6n5h+SVVuUYudKpzVejbdvKmE76dYynAOrVzVVp6SKGe
k46vffLP9SsohwhKIIZAnKS+carZ5anENUTnF82WDP6HnugK4Z3zif8bhATC
tonkJv8NdygF1vLUpAFlsgfmvhzt+DRpYRjwEIBiTv044ASvCLpObY0WFvfl
fZoj6tSamlYDqw3armvAR7u347sl2L9yfZ9vq0BhItKhI7+3SlS1y7ZKd6VY
t5rv6XQqGsRDQVqJd1lii7nDFmuy5YqWra6mLRXFu1W8/MFod/dQbj3Zch+P
5FawVT2NnUp3KD3aEXcp1HRL/AokhV+XEvkCrqWqwxMdjlMJtKWQj1MS4f7w
4R4EaznV1i2JSCXGFkuggoxrTRpUc5+PTz++PJFHxycnh+d1U1XxEtxQcd5Q
QXEV2KCW5or4ryLKwd1gyUK1RbkhdY3KT+pPwXd/94/f/eKf3+s1LYcV/w/O
cjMdyHYeqErK9/h+Q26fNB8Dr3VHkTsJbZMwKRWJ90TP75jOvs18uy1SeyWc
4N2kmgtdUn0bM3ea1RrCL7fffrPj+MJ//9NP/+fnf3HnkZGXVet3FheOcDg1
vb2DBgIH/sMgeBcYUsqpM5FUM3OtA/HcrOlc+0QSQt1KSXUlg1KKyISBByN3
LuMZtGZlmZhrsdxk4Fu271Jdtz2N7TVnMGB+srkRQS6BiipzMrSfJRFKF7C6
qLoisL4fW9UYsavV/E0TVcDM3nkS93lr3pw0a1QVRAWUzDZ8tewSMyvTKboM
9TEiTf07ICrMguS2xpRNFqMAbLotPp1OzYG44yaAzYjf5IePjy/OBvv7Dx4N
ho8/e+zqzQ+P9tmzHn8InsRsVjSN3Zb795AVe4xno0PZW5kw0Em2Uq/1k6tc
XUe5UoEOexX3QPAlkZhV1zncgQTexGD9CnzgWuVXnYy57RcOQaTJWADTLFEb
4YofGH2Hi39iRdE1gJZw1HU5Q9DVOfnkzKBE9XTBT4fmNbC5WwJ4UOyLuTrR
tbLXrUOpKmHRLf104ppCyzjjlR0BxAH9Tld5Bzlxt3qydYnleQz+rUKRhBo/
PT2qyxV/29UBx6pb3t4lhQfZugYT0Bp8LXRdrTv7xyQRTcKx+ZYNXT65SkLU
vYs139QoyS8FtK7yVvFiWfDRsB+5qFdN91+oolDhlWszLuENg8IMqKvfcAbl
WRrpwvdeODloh8NOeQaq4RmT+xo7FCEDll/5ww1d+amc6DJMWLSGVaM6vI6Z
nwtHcF1p1rZEXYNyJ6de3oCL2NIVfcWNK1bW1pcW1f3i9tT05YRbeDveukwx
Le1Id4cyoctmcOJXJo8LZjh0B2c7la5zxam5h5W4cUttsGo7ugcU0zMuqNkT
izuvjNtOwz5J9SJOYaWJWXk7WCaJ9dWQb35yg2hhTCR/XMJ98Ay+fDyn9ONX
d5dfFXIVVP92pbBLwgTy1qVC1FhEN9+oscMy0ejV15z+uF+Mv2gR8sYSXF0T
U+GbwAyiRSSU69TSCWETDuVIJ0T1N65/FXcKAWrP9jic6dJdTohpRlRksMJf
fo+evnlnwFbVBAGz8rHE3VGmL5jKK1/osOQzvbX6xeHk8vx4+gV2+Jy0afy3
5motGn/jxtV12ur7Qrrn4uRj6TwUF+JuiGv04Ak3AeFYcDa6raBUo18zfVL+
Kh/2XIg5Inqn22FBeKXUfIGrVPeVdcxXd5rUXeI2W8yl3FlK9MyXKtTxZEQG
iYzt0kFrbK/oNLgAA1Aj68PhbtQ3otU0Rt45Ojp61pfnhy9PxpPDF4enUzl5
Pj4fT6aH5xS41Eiq44LhWJiMjR3IU1P4aOX04u5zfUXhTVsFawWHJDW/p4CE
yi0s5d56AItXRVmDArR+9unxC0+IOxmj8RmHz3Se5WoGr6b4vtlLA7ABAK50
u3kXxfN5HJYJ33CHpWOvmcJhBf51B3qnpdX73AuGwcglSOYbdEmwXhrfMq06
jJrtrq5NHAnCmYGle3t+L6S5h+93XptoN1iHu8GwtYdetd+ccHkw7bx8RIHo
b0/Aw6lUqbcJ2s05Ue3wIBgF9ymFhyVHO19W+cPkmoekhjZZxtfHHD7+VRHC
gw5g5npFh+/f2OlzLQBbe6dlGK8IS1q9EuHYGLdvAdDtO3Ly9+qVg9BHtCzT
0lJzkjG7dgvKC9MyvyKXj0yR0IH+x7/4d1hmSH8ED+PwKjXrREcL7hv5sorf
DyK/t0vHRVR6JT8xy1SC/32a0Gmhwnim0lgn8nCx0DkAd5xC67X8GIGqFvwa
ziegvbneyAuktjm8pi9fapjiXNs0Dq/64lQR0uRKXsBqS/kU22HMxCRACFoO
CptUbG+oo81tK4qxvszohkMj9W5/btYeKpDMW4SnuqIHH6PMEGHss6p8Ia/6
9td/TfWGv3pw7/ww4DNRoDfu/EB+4Y9PnCudVNSE172E4+JL+WzUuZ2gC0y1
MqXlF/uosZSi1oBt+nyLweCz5JBIm1s7lwyo81R6RPdUED4qdUTvdAnxkvVn
x/K3bWcZHPDY2lLXvO8W0St9tLgmo++CF6a50rvjFiqo9nKk2PMN0yzDRMa9
3eDf+SCXTzV7DpFR+Z8//VtKDtyf5aqXozDXLhVSWCBpQjyugeXxFgWzAR/5
yca5eMm+HqlN4G62KckuvG5sZKsLl0xs0WUqn1ycnTqSwTdfmt5W4RmIshmO
bIXVM+I6onrFbgGcL2dUDdyj10Pv3X4P9t4sMTN6nt6jDW3wCh7KvZUCYUkN
ZLnNNJpUdAVD68KpQV9qLZJByYvq6G131KwRwNuievGHMLdm1VXOW5v8KpDn
yr3z5joKIK04DXdJA1T0F2QVd8/nIaXljGycEO+KkE4To9zNCGvkXwNTfKp0
VVfBCWhEUlsqV+vAWYsqGr4fQWHyPsPdsJn4SDZf+Fq04HKK3mKGEtexXiP6
D+S0lmsdgxRy25zvaiM2MRGCnNpEMz2nutH1oR3qb/Ntwpyu4nnVE7oWnQCd
3Bs2HDMxxwxfX126+ofI6WMh/hfR3uZ+nC0AAA==

-->

</rfc>
