<?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.1.2) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-atwood-jmap-updates-00" category="std" consensus="true" submissionType="IETF" updates="8620, 9425" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.35.0 -->
  <front>
    <title abbrev="JMAP Updates">Updates to JMAP: Localized Display Text, Text Handling, URIs, and Problem Details</title>
    <seriesInfo name="Internet-Draft" value="draft-atwood-jmap-updates-00"/>
    <author fullname="Mark Atwood">
      <organization>Review Commit, LLC</organization>
      <address>
        <postal>
          <city>Seattle</city>
          <region>WA</region>
          <country>US</country>
        </postal>
        <email>mark@reviewcommit.com</email>
      </address>
    </author>
    <date year="2026" month="November" day="15"/>
    <abstract>
      <?line 99?>

<t>JMAP (RFC 8620) carries all data as UTF-8 I-JSON, lets a client name a
collation for sorting, and lets a server localize user-visible strings
from the request's Accept-Language header. It has no way to store or
return display text, such as the name of a mailbox, address book, or
quota, in more than one language, and no way to say which language a
stored string is in. This document defines the
<tt>urn:ietf:params:jmap:i18n</tt> capability, which adds <tt>locale</tt> and
<tt>localizations</tt> properties, modelled on JSCalendar (RFC 8984), to the
display text of existing JMAP data types, and a <tt>language</tt> argument
with which a client asks for one language. For clients that use that
argument, this document updates RFC 9425, which selects the Quota
description by Accept-Language. It also updates RFC 8620 with guidance for all JMAP specifications on text profiles, Unicode
normalization, truncation, and the use of display text, and asks that
URI-valued properties follow RFC 3986 and that every JMAP HTTP
resource report errors as RFC 9457 problem details.</t>
    </abstract>
  </front>
  <middle>
    <?line 117?>

<section anchor="introduction">
      <name>Introduction</name>
      <section anchor="existing">
        <name>What JMAP Already Provides</name>
        <t>JMAP <xref target="RFC8620"/> already settles several internationalization
questions, and this document does not change them:</t>
        <ul spacing="normal">
          <li>
            <t><strong>Encoding.</strong> Everything exchanged, except binary upload and
download, is I-JSON <xref target="RFC7493"/> encoded in UTF-8 <xref target="RFC3629"/>
(<xref target="RFC8620"/> Section 1.5). A JMAP specification does not need to say
again that a string is valid UTF-8.</t>
          </li>
          <li>
            <t><strong>Server-chosen strings.</strong> When a server returns a custom string to
be shown to the user, it chooses the localization from the request's
Accept-Language header (<xref target="RFC9110"/> Section 12.5.4) and labels the
response with Content-Language (<xref target="RFC8620"/> Section 3.8). The Quota <tt>description</tt> of <xref target="RFC9425"/>
applies the same rule to a data property.</t>
          </li>
          <li>
            <t><strong>Collation.</strong> A <tt>/query</tt> Comparator names a collation from the
registry of <xref target="RFC4790"/>, and the server lists the ones it supports in
the <tt>collationAlgorithms</tt> property of the <tt>urn:ietf:params:jmap:core</tt>
capability (<xref target="RFC8620"/> Sections 2 and 5.5). The default collation
is Unicode-aware, for example "i;unicode-casemap" <xref target="RFC5051"/>.</t>
          </li>
          <li>
            <t><strong>Content.</strong> Email content carries its own charset and
Content-Language, which <xref target="RFC8621"/> exposes on each body part.
JSCalendar <xref target="RFC8984"/> and JSContact <xref target="RFC9553"/> objects carry a
language and per-language localizations of their own.</t>
          </li>
        </ul>
      </section>
      <section anchor="gaps">
        <name>What Is Missing</name>
        <ul spacing="normal">
          <li>
            <t><strong>Display text has one value and no language.</strong> The name of a
Mailbox, an AddressBook, a Calendar, or a Principal is a single
string. A shared address book used by French and German speakers can
have only one name, and nothing says which language that name is in.
BCP 18 <xref target="RFC2277"/> asks that a protocol that transfers text be able
to carry the language of that text (Section 4.2).</t>
          </li>
          <li>
            <t><strong>Content-Language describes a whole response.</strong> One HTTP response
can carry objects in several languages, and a response sent over a
WebSocket <xref target="RFC8887"/> has no header at all.</t>
          </li>
          <li>
            <t><strong>Text handling is unstated.</strong> JMAP specifications do not say
whether servers normalize text, where a server may cut a string it
shortens, or whether display text may carry meaning.</t>
          </li>
          <li>
            <t><strong>URIs and errors are uneven.</strong> <xref target="RFC8620"/> asks for problem
details, citing <xref target="RFC7807"/>, which <xref target="RFC9457"/> obsoletes, on errors
from the API, upload, and download resources, but not from the
Session resource, the event source, or resources that extensions
add. Properties whose values are URIs are defined one by one, with
no common rule for their syntax or for non-ASCII characters.</t>
          </li>
        </ul>
      </section>
      <section anchor="this-document">
        <name>This Document</name>
        <t><xref target="capability"/> defines the <tt>urn:ietf:params:jmap:i18n</tt> capability.
<xref target="localization"/> defines the <tt>locale</tt> and <tt>localizations</tt> properties
and the <tt>language</tt> argument, and <xref target="applicability"/> lists the
properties of existing data types that they apply to. For clients
that opt in, this updates how <xref target="RFC9425"/> selects the Quota
<tt>description</tt> (<xref target="quotas"/>). Future specifications can adopt them by
listing their own localizable properties (<xref target="new-specs"/>).</t>
        <t>This brings JMAP display text in line with BCP 18 <xref target="RFC2277"/>. The
<tt>localizations</tt> map follows the language-map pattern that
<xref target="STRING-META"/> recommends for JSON formats that carry more than one
language version of a field. This document does not add the
per-string direction metadata that <xref target="STRING-META"/> also recommends;
see <xref target="confusables"/>.</t>
        <t><xref target="text-handling"/> and <xref target="uris-problems"/> update <xref target="RFC8620"/> with
guidance on text, URIs, and errors that applies to every JMAP
specification, whether or not the capability is in use. They add no
properties and no arguments.</t>
      </section>
      <section anchor="conventions-used-in-this-document">
        <name>Conventions Used in This Document</name>
        <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" 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>
        <t>Type signatures, examples, and property descriptions follow
<xref target="RFC8620"/> Section 1.</t>
        <dl>
          <dt>Display text:</dt>
          <dd>
            <t>A string intended to be shown to a person and not interpreted by
software, such as a name, a description, or a label.</t>
          </dd>
          <dt>Localizable property:</dt>
          <dd>
            <t>A property of a data type whose value is display text and that this
document, or a specification that adopts it, lists as localizable.</t>
          </dd>
          <dt>Language tag:</dt>
          <dd>
            <t>A language tag as defined in <xref target="RFC5646"/>.</t>
          </dd>
        </dl>
      </section>
    </section>
    <section anchor="capability">
      <name>Capability</name>
      <t>A server that supports this document advertises the
<tt>urn:ietf:params:jmap:i18n</tt> capability in the <tt>capabilities</tt> property
of the JMAP Session resource (<xref target="RFC8620"/> Section 2). Its value is an
empty object.</t>
      <t>The same capability appears in the <tt>accountCapabilities</tt> of each
account for which the server supports localizations. Its value there is
also an empty object.</t>
      <t>A client that wants the properties and arguments of this document
includes <tt>urn:ietf:params:jmap:i18n</tt> in the <tt>using</tt> property of the
Request. When the capability is not in <tt>using</tt>, the server behaves
as if this document did not exist: it neither returns nor accepts
<tt>locale</tt> and <tt>localizations</tt>, and it rejects the <tt>language</tt> argument
with <tt>invalidArguments</tt>, as it would any unknown argument (<xref target="RFC8620"/>
Section 3.9). The same applies to an account whose
<tt>accountCapabilities</tt> does not include <tt>urn:ietf:params:jmap:i18n</tt>,
even when the capability is in <tt>using</tt>: a <tt>/set</tt> that names <tt>locale</tt> or
<tt>localizations</tt> is rejected with an <tt>invalidProperties</tt> SetError, and a
<tt>language</tt> argument with <tt>invalidArguments</tt>.</t>
      <t>Example Session excerpt:</t>
      <sourcecode type="json"><![CDATA[
{
  "capabilities": {
    "urn:ietf:params:jmap:core": {
      "collationAlgorithms": [ "i;unicode-casemap" ]
    },
    "urn:ietf:params:jmap:mail": {},
    "urn:ietf:params:jmap:i18n": {}
  },
  "accounts": {
    "a1": {
      "name": "jane@example.com",
      "isPersonal": true,
      "isReadOnly": false,
      "accountCapabilities": {
        "urn:ietf:params:jmap:mail": {},
        "urn:ietf:params:jmap:i18n": {}
      }
    }
  }
}
]]></sourcecode>
      <t>This document does not define an account-level language preference.
Text that a server produces when no request is in progress, such as
the text of a push notification, has no Accept-Language or <tt>language</tt>
argument to go by; choosing its language is left to a specification of
account settings.</t>
    </section>
    <section anchor="localization">
      <name>Localized Display Text</name>
      <section anchor="properties">
        <name>The locale and localizations Properties</name>
        <t>A data type that has at least one localizable property gains two
properties when <tt>urn:ietf:params:jmap:i18n</tt> is in <tt>using</tt>:</t>
        <dl>
          <dt><tt>locale</tt>: <tt>String|null</tt> (default: null)</dt>
          <dd>
            <t>The language tag of the values of the object's localizable
properties. Null means the language is unknown. This has the
meaning of <tt>locale</tt> in <xref target="RFC8984"/> Section 4.2.8.</t>
          </dd>
          <dt><tt>localizations</tt>: <tt>String[PatchObject]|null</tt> (default: null)</dt>
          <dd>
            <t>A map from a language tag to a PatchObject (<xref target="RFC8984"/> Section
1.4.9) that, applied to the object, gives its localizable properties
in that language. This has the meaning of <tt>localizations</tt> in
<xref target="RFC8984"/> Section 4.6.1, with the restrictions below.</t>
          </dd>
        </dl>
        <t>The restrictions on <tt>localizations</tt> are:</t>
        <ul spacing="normal">
          <li>
            <t>Each key of a PatchObject is the name of a localizable property of
the data type, and its value is of that property's type.</t>
          </li>
          <li>
            <t>A PatchObject need not cover every localizable property; a property
it omits keeps the base value in that language.</t>
          </li>
          <li>
            <t>A null value is allowed only for a property whose type allows null,
and means that the property has no value in that language; for
example, <tt>{"description": null}</tt> says there is no description in
that language.</t>
          </li>
          <li>
            <t>Language tags are case-insensitive (<xref target="RFC5646"/> Section 2.1.1). No
two keys of <tt>localizations</tt> may differ only in case, and no key may
equal <tt>locale</tt>, ignoring case. Servers SHOULD store tags in the
canonical case that <xref target="RFC5646"/> Section 2.1.1 recommends.</t>
          </li>
        </ul>
        <t>The values of the localizable properties on the object itself are the
base values. Rules that the defining specification places on a
localizable property, such as a length limit, a non-empty value, or
uniqueness among siblings, apply to the base value. A server SHOULD
apply the same length and syntax limits to localized values. Uniqueness
rules apply only to base values unless the defining specification says
otherwise.</t>
        <t>A server rejects a <tt>/set</tt> create or update whose <tt>localizations</tt>
breaks these restrictions, or has a key that is not a language tag,
with an <tt>invalidProperties</tt> SetError naming <tt>localizations</tt>. This
differs from <xref target="RFC8984"/> Section 4.6.1, under which a recipient ignores
an invalid patch: a JMAP server can report the error to the client
that sent it. A server MAY limit the number of
localizations it stores per object and reject more with the same
error.</t>
        <t>When an update changes the base value of a localizable property, the
existing localized values of that property no longer translate the new
base value. For each language whose PatchObject the update does not
set, neither by setting <tt>localizations</tt> as a whole, nor the key for
that language, nor that property inside it, the server SHOULD remove
the property from that PatchObject, and remove the PatchObject if it is
left empty, as part of the same update. This keeps a client that does
not use this capability, or that updates only some languages, from
leaving stale translations behind when it renames an object. An
update that changes only <tt>locale</tt>, and no base value, removes nothing.
When the server removes anything, it includes <tt>localizations</tt> in the
object it returns in <tt>updated</tt> (<xref target="RFC8620"/> Section 5.3) to clients
that have the capability in <tt>using</tt>. The value returned is the whole
of <tt>localizations</tt> after the removal, not a patch.</t>
        <t>For a server-set localizable property, such as Quota <tt>name</tt>, the server
populates <tt>locale</tt> and <tt>localizations</tt> itself. A server MAY also
populate them for objects it creates on the user's behalf, such as the
default Mailboxes of a new account.</t>
      </section>
      <section anchor="language-argument">
        <name>The language Argument</name>
        <t>When <tt>urn:ietf:params:jmap:i18n</tt> is in <tt>using</tt>, the standard <tt>/get</tt>,
<tt>/query</tt>, and <tt>/queryChanges</tt> methods (<xref target="RFC8620"/> Sections 5.1, 5.5,
and 5.6) of a data type with localizable properties take one
additional argument:</t>
        <dl>
          <dt><tt>language</tt>: <tt>String[]|null</tt> (default: null)</dt>
          <dd>
            <t>A list of language ranges (<xref target="RFC4647"/> Section 2.1), most preferred
first. When null, objects are returned and compared as stored.</t>
          </dd>
        </dl>
        <section anchor="in-get">
          <name>In /get</name>
          <t>When <tt>language</tt> is non-null, for each returned object the server:</t>
          <ol spacing="normal" type="1"><li>
              <t>Forms the set of available language tags: the keys of
<tt>localizations</tt>, plus the object's <tt>locale</tt> when it is non-null.</t>
            </li>
            <li>
              <t>Chooses one tag by the Lookup scheme of <xref target="RFC4647"/> Section 3.4,
trying the ranges of <tt>language</tt> in order. When no range matches,
it chooses the object's <tt>locale</tt>, which may be null.</t>
            </li>
            <li>
              <t>Returns the localizable properties with the PatchObject for the
chosen tag applied, when the chosen tag is a key of
<tt>localizations</tt>, and with their base values otherwise.</t>
            </li>
            <li>
              <t>Sets <tt>locale</tt> in the returned object to the chosen tag.</t>
            </li>
            <li>
              <t>Returns <tt>localizations</tt> as null.</t>
            </li>
          </ol>
          <t>The view returns <tt>localizations</tt> as null because the chosen tag would
otherwise be both the <tt>locale</tt> and a key of <tt>localizations</tt>, which
<xref target="properties"/> does not allow. A client that wants every language
omits <tt>language</tt>.</t>
          <t>Lookup removes subtags from the end of a range but never adds them: the
range "de" matches a key "de" and not a key "de-CH" (<xref target="RFC4647"/>
Section 3.4). A client SHOULD therefore include a range for each
language it accepts in its general form, for example
<tt>[ "de-CH", "de", "en" ]</tt>. Lookup skips a range "<em>" that other ranges
follow, and a final "</em>" selects the default, which here is the base
values (<xref target="RFC4647"/> Section 3.4).</t>
          <t>The returned object is then a view in one language, not the stored
object. Its <tt>state</tt> and the <tt>/changes</tt> state are those of the stored
object; choosing a different language does not change them.</t>
          <t>When <tt>urn:ietf:params:jmap:i18n</tt> is in <tt>using</tt>, the server MUST NOT
let the Accept-Language header of the request change the result of
<tt>/get</tt> or <tt>/query</tt> for any localizable property; it applies a language
only when the client passes <tt>language</tt>. A client that caches objects
by id and state would otherwise hold a mix of languages and could not
tell. For the Quota <tt>description</tt>, this replaces the selection by
Accept-Language in <xref target="RFC9425"/> Section 4.1 for clients that opt in
(<xref target="quotas"/>). <xref target="RFC8620"/> Section 3.8 still applies to custom strings
that are not properties of a data type, such as the <tt>title</tt> and
<tt>detail</tt> of a problem details object (<xref target="problems"/>).</t>
          <t>A client that edits an object it obtained through <tt>language</tt> SHOULD
send only the properties it means to change. Writing a localized value
back to a base property replaces the base value, writing back the
returned <tt>locale</tt> changes the base language, and writing back the
returned null <tt>localizations</tt> removes every localization.</t>
        </section>
        <section anchor="in-query">
          <name>In /query</name>
          <t>When <tt>language</tt> is non-null, a <tt>/query</tt> that sorts on, or filters on,
a localizable property compares the value that <tt>/get</tt> with the same
<tt>language</tt> would return, not the base value. When the Comparator names
no <tt>collation</tt>, the server MAY choose one suited to the language
chosen for each object, as <xref target="RFC8620"/> Section 5.5 already allows it to
do from Accept-Language.</t>
        </section>
        <section anchor="in-querychanges">
          <name>In /queryChanges</name>
          <t>The <tt>language</tt> argument of <tt>/queryChanges</tt> has the same meaning as in
<tt>/query</tt>. The <tt>queryState</tt> of a <tt>/query</tt> result reflects the <tt>language</tt>
it was computed with. When the <tt>language</tt> of a <tt>/queryChanges</tt> differs
from that of the <tt>/query</tt> that produced <tt>sinceQueryState</tt>, the server
returns a <tt>cannotCalculateChanges</tt> error (<xref target="RFC8620"/> Section 5.6).</t>
        </section>
      </section>
      <section anchor="websocket">
        <name>Language of Responses over WebSocket</name>
        <t>A Request sent over a WebSocket (<xref target="RFC8887"/> Section 4.3.2) has no Accept-Language
header of its own. A server SHOULD treat the Accept-Language header of
the WebSocket opening handshake as the Accept-Language of every Request
on that connection, for the purposes of <xref target="RFC8620"/> Section 3.8.</t>
        <t>A Response sent over a WebSocket has no Content-Language header. The
display text in it is labelled by the <tt>locale</tt> of each object
(<xref target="properties"/>), which serves both transports. This document defines
no response-level label: the custom strings of <xref target="RFC8620"/> Section 3.8
that a Response might carry, such as an error <tt>description</tt>, are
non-localized (<xref target="RFC8620"/> Sections 3.6.2 and 5.3).</t>
      </section>
    </section>
    <section anchor="applicability">
      <name>Applicability to Existing Data Types</name>
      <t>When <tt>urn:ietf:params:jmap:i18n</tt> is in <tt>using</tt>, the following data
types gain <tt>locale</tt> and <tt>localizations</tt>, and accept the <tt>language</tt>
argument on <tt>/get</tt> and <tt>/query</tt>. Each table lists the localizable
properties.</t>
      <section anchor="mail">
        <name>JMAP Mail</name>
        <table>
          <thead>
            <tr>
              <th align="left">Data type</th>
              <th align="left">Localizable properties</th>
              <th align="left">Defined in</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">Mailbox</td>
              <td align="left">
                <tt>name</tt></td>
              <td align="left">
                <xref target="RFC8621"/> Section 2</td>
            </tr>
          </tbody>
        </table>
        <t>A Mailbox <tt>name</tt> is a Net-Unicode string <xref target="RFC5198"/> (<xref target="RFC8621"/>
Section 2); localized names SHOULD meet the same rule. The rule that
sibling Mailboxes have distinct names applies to base names only, so
two siblings can share a localized name; a client that shows localized
names MAY add the base name to tell them apart.
Clients that today show a translated name for a Mailbox with a <tt>role</tt>
can continue to do so; <tt>localizations</tt> lets a user or server give names
to Mailboxes that have no role.</t>
        <t>Email content is not affected. Body parts already carry <tt>charset</tt> and
<tt>language</tt> (<xref target="RFC8621"/> Section 4.1.4).</t>
        <t>Identity is not listed. Its <tt>name</tt> is the sender's own name as other
people see it in messages, so choosing it by the reader's <tt>language</tt>
is the wrong choice, and its signatures are message content, one of
them HTML. VacationResponse (Section 8 of <xref target="RFC8621"/>) is not listed
either: a vacation reply in several languages would be chosen by the
language of each incoming message, not by a client's <tt>language</tt>, and
is left to a future specification.</t>
      </section>
      <section anchor="quotas">
        <name>JMAP Quotas</name>
        <table>
          <thead>
            <tr>
              <th align="left">Data type</th>
              <th align="left">Localizable properties</th>
              <th align="left">Defined in</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">Quota</td>
              <td align="left">
                <tt>name</tt>, <tt>description</tt></td>
              <td align="left">
                <xref target="RFC9425"/> Section 4.1</td>
            </tr>
          </tbody>
        </table>
        <t>Both properties are server-set. When the capability is not in
<tt>using</tt>, the server selects <tt>description</tt> from Accept-Language as
<xref target="RFC9425"/> Section 4.1 describes. When it is in <tt>using</tt>, this
document updates <xref target="RFC9425"/>: with <tt>language</tt> null, the server returns
the base values with their <tt>locale</tt> and all <tt>localizations</tt>, and with
<tt>language</tt> set, it selects as <xref target="language-argument"/> describes.</t>
      </section>
      <section anchor="contacts">
        <name>JMAP Contacts</name>
        <table>
          <thead>
            <tr>
              <th align="left">Data type</th>
              <th align="left">Localizable properties</th>
              <th align="left">Defined in</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">AddressBook</td>
              <td align="left">
                <tt>name</tt>, <tt>description</tt></td>
              <td align="left">
                <xref target="RFC9610"/> Section 2</td>
            </tr>
          </tbody>
        </table>
        <t>A ContactCard is a JSContact Card <xref target="RFC9553"/>, which has its own
<tt>language</tt> and <tt>localizations</tt> (Sections 2.1.5 and 2.7.1 of
<xref target="RFC9553"/>). This document does not add properties to it, and the
<tt>language</tt> argument does not apply to <tt>ContactCard/get</tt>.</t>
      </section>
      <section anchor="sharing">
        <name>JMAP Sharing</name>
        <table>
          <thead>
            <tr>
              <th align="left">Data type</th>
              <th align="left">Localizable properties</th>
              <th align="left">Defined in</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">Principal</td>
              <td align="left">
                <tt>name</tt>, <tt>description</tt></td>
              <td align="left">
                <xref target="RFC9670"/> Section 2</td>
            </tr>
          </tbody>
        </table>
        <t>A ShareNotification <tt>name</tt> records the name of an object at the time
of a change (<xref target="RFC9670"/> Section 3). It is not localizable. A server
SHOULD fill it with the base value.</t>
      </section>
      <section anchor="calendars">
        <name>JMAP Calendars</name>
        <t>JMAP for Calendars <xref target="JMAP-CALENDARS"/> is not yet published. When it
is, the following apply:</t>
        <table>
          <thead>
            <tr>
              <th align="left">Data type</th>
              <th align="left">Localizable properties</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">Calendar</td>
              <td align="left">
                <tt>name</tt>, <tt>description</tt></td>
            </tr>
          </tbody>
        </table>
        <t>ParticipantIdentity is not listed, for the reason Identity is not
(<xref target="mail"/>).</t>
        <t>CalendarEvent objects are JSCalendar objects <xref target="RFC8984"/> and already
have <tt>locale</tt> and <tt>localizations</tt>. The <tt>language</tt> argument does not
apply to <tt>CalendarEvent/get</tt>.</t>
      </section>
      <section anchor="new-specs">
        <name>New Specifications</name>
        <t>A specification for a new JMAP data type that has display text can
adopt this document by listing that type's localizable properties and
requiring <tt>urn:ietf:params:jmap:i18n</tt> in <tt>using</tt> for them. A data type
whose objects are JSCalendar or JSContact objects uses their own
<tt>localizations</tt> and does not adopt this document.</t>
      </section>
    </section>
    <section anchor="text-handling">
      <name>Text Handling in JMAP</name>
      <t>This section updates <xref target="RFC8620"/>. It applies to every JMAP
specification and implementation, whether or not
<tt>urn:ietf:params:jmap:i18n</tt> is in use, and changes nothing on the
wire.</t>
      <section anchor="encoding">
        <name>Encoding</name>
        <t><xref target="RFC8620"/> Section 1.5 makes every string UTF-8. Specifications
built on JMAP SHOULD cite that section instead of restating it. A
property that carries binary data or ciphertext as a string says how
it is encoded, for example base64url, and is not text for the purposes
of this section.</t>
      </section>
      <section anchor="profiles">
        <name>Text Profiles</name>
        <t>Display text SHOULD NOT contain:</t>
        <ul spacing="normal">
          <li>
            <t>the control characters U+0000 to U+001F and U+007F to U+009F,
except that multi-line display text, such as a description, uses
U+000A LINE FEED to end lines;</t>
          </li>
          <li>
            <t>U+2028 LINE SEPARATOR or U+2029 PARAGRAPH SEPARATOR;</t>
          </li>
          <li>
            <t>the noncharacters U+FFFE and U+FFFF; or</t>
          </li>
          <li>
            <t>a leading U+FEFF used as a byte order mark.</t>
          </li>
        </ul>
        <t>A line ends with LF alone, not CR LF. These are the rules of
one-dimensional and two-dimensional Modern Network Unicode (<xref target="MNU"/>
Sections 2 and 3), stated here so that this document does not depend
on that one. A specification MAY require a stricter profile for a
property, as <xref target="RFC8621"/> does for Mailbox names with Net-Unicode
<xref target="RFC5198"/>. A server MAY reject display text that breaks these rules
with an <tt>invalidProperties</tt> SetError.</t>
        <t><xref target="RFC9610"/> Section 5 and <xref target="RFC9670"/> Section 5 already let a server
restrict the characters of otherwise unconstrained String fields,
starting from the PRECIS FreeformClass (<xref target="RFC8264"/> Section 4.3), and
strip or replace what falls outside that set or reject it. This
section gives the same latitude, with the same choices, to display
text in every JMAP specification, so that a server does not need
different rules for free-text fields of different specifications. A
server that changes a value returns the changed property in the
<tt>/set</tt> response (<xref target="RFC8620"/> Section 5.3).</t>
      </section>
      <section anchor="normalization">
        <name>Normalization</name>
        <t>A server SHOULD NOT normalize text that it stores and returns, unless
the defining specification requires a normalization form, as
Net-Unicode <xref target="RFC5198"/> does for Mailbox names.
Normalization changes the bytes of text that may be signed, encrypted,
hashed, or compared with an earlier version, and it is not always
reversible.</t>
        <t>Clients SHOULD send display text in Normalization Form C (NFC), as
<xref target="RFC5198"/> and <xref target="MNU"/> recommend. A new specification that compares
display text, for example to enforce a uniqueness rule, SHOULD say how;
comparing code point sequences is the simplest choice. This document
does not change the comparisons of existing specifications.</t>
      </section>
      <section anchor="no-meaning">
        <name>Display Text Carries No Meaning</name>
        <t>Servers and clients SHOULD NOT give display text meaning: they should
not decide behaviour by matching a name or description, in any
language, against a fixed string. Meaning belongs in an enumerated or
structured property. The Mailbox <tt>role</tt> of <xref target="RFC8621"/> is the model: a
client finds the inbox by its role, not by a name of "Inbox".</t>
      </section>
      <section anchor="lengths">
        <name>Length Limits and Truncation</name>
        <t>Length limits on strings in JMAP specifications are counted in octets
of UTF-8, as <xref target="RFC9610"/> and <xref target="JMAP-CALENDARS"/> do. New specifications
SHOULD state limits in octets.</t>
        <t>When a server shortens text, for example to produce a preview such as
the Email <tt>preview</tt> of <xref target="RFC8621"/>, a notification body, or a push
payload, it SHOULD cut at an extended grapheme cluster boundary
(<xref target="UAX29"/>), and never splits a code point. In particular it never
separates the two halves of a UTF-16 surrogate pair in an
implementation that holds strings as UTF-16, since the result would not
be valid I-JSON.</t>
      </section>
      <section anchor="collation">
        <name>Collation and Search</name>
        <t><xref target="RFC8620"/> Section 5.5 already defines collation for sorting.
Specifications that define a text filter on display text SHOULD
compare using the collation the server would use to sort that
property, so that a case-insensitive sort gives a case-insensitive
filter. Tokenization and stemming for text search depend on
the language and are implementation-defined; a server MAY use <tt>locale</tt>
to choose them.</t>
      </section>
      <section anchor="time">
        <name>Dates and Times</name>
        <t>Instants on the wire are UTCDate (<xref target="RFC8620"/> Section 1.4) and carry
no locale. A property that holds a wall-clock or recurring time SHOULD
carry a time zone identifier from the IANA Time Zone Database, as the
Principal <tt>timeZone</tt> of <xref target="RFC9670"/> does and as <xref target="RFC8984"/> Section
1.4.8 recommends for TimeZoneId. Formatting dates, times, and numbers for display is the client's
business.</t>
      </section>
    </section>
    <section anchor="uris-problems">
      <name>URIs and Problem Details in JMAP</name>
      <t>This section updates <xref target="RFC8620"/>. Like <xref target="text-handling"/>, it applies
to every JMAP specification and implementation, whether or not
<tt>urn:ietf:params:jmap:i18n</tt> is in use.</t>
      <section anchor="uris">
        <name>URIs</name>
        <t>A property, argument, or Session member whose value is a URI or URL
SHOULD hold a URI as defined in <xref target="RFC3986"/> Section 3. Unless its
defining specification allows a relative reference, it SHOULD be a URI
and not a relative reference (<xref target="RFC3986"/> Section 4.2). A URI Template (<xref target="RFC6570"/>), such as
the <tt>downloadUrl</tt> of the Session, SHOULD expand to such a URI.</t>
        <t>URIs in JMAP are ASCII. A client or server that holds an
Internationalized Resource Identifier (<xref target="RFC3987"/>), for example one a
user typed, SHOULD map it to a URI (<xref target="RFC3987"/> Section 3.1) before
sending it, and a client MAY convert a URI back to an IRI for display
(<xref target="RFC3987"/> Section 3.2). Characters outside ASCII in a path, query,
or fragment are therefore sent as percent-encoded UTF-8. A domain name
SHOULD be sent in its A-label form, which <xref target="RFC3987"/> Section 3.1
permits, because many URI consumers do not accept a percent-encoded
host.</t>
        <t>A server compares URIs that identify things, such as capability URIs,
as exact strings (<xref target="RFC3986"/> Section 6.2.1) unless the defining
specification names another comparison. A specification that defines
a URI-valued property SHOULD cite <xref target="RFC3986"/> instead of restating its
syntax.</t>
      </section>
      <section anchor="problems">
        <name>Problem Details</name>
        <t>Where <xref target="RFC8620"/> cites <xref target="RFC7807"/> for problem details (Sections 3.6.1,
6.1, and 6.2 of <xref target="RFC8620"/>), the reference is to <xref target="RFC9457"/>, which
obsoletes it. The problem types and members that <xref target="RFC8620"/> defines are
unchanged.</t>
        <t>Every HTTP resource of a JMAP server SHOULD return a problem details
object (<xref target="RFC9457"/>) as the body of an error response with a 4xx or 5xx
status code. This includes the resources that <xref target="RFC8620"/> does not
cover: the Session resource, the event source (<xref target="RFC8620"/> Section
7.3), the WebSocket opening handshake (<xref target="RFC8887"/>), and any HTTP
resource that an extension adds. A specification that defines a new
HTTP resource for JMAP SHOULD say which problem types it returns and
SHOULD register the types it defines in the "JMAP Error Codes"
registry, which gives them the <tt>urn:ietf:params:jmap:error:</tt> prefix in
problem details (<xref target="RFC8620"/> Section 9.5).</t>
        <t>The <tt>title</tt> and <tt>detail</tt> members are display text. A server MAY
localize them using Accept-Language (<xref target="RFC9457"/> Sections 3 and
3.1.3), and SHOULD label the response with Content-Language when it
does (<xref target="RFC8620"/> Section 3.8). Clients act on <tt>type</tt> and the HTTP
status code, never on <tt>title</tt> or <tt>detail</tt> (<xref target="no-meaning"/>).</t>
      </section>
    </section>
    <section anchor="security">
      <name>Security Considerations</name>
      <section anchor="confusables">
        <name>Confusable and Bidirectional Text</name>
        <t>Display text from other users, such as the name of a shared address
book or of a Principal, can imitate other text. Characters from
different scripts can look alike (<xref target="UTS39"/>), and bidirectional
formatting characters can reorder what is shown (<xref target="UAX9"/>). Clients
SHOULD isolate display text from other users when they place it in
surrounding text, for example with U+2068 FIRST STRONG ISOLATE and
U+2069 POP DIRECTIONAL ISOLATE, or the HTML <tt>bdi</tt> element. Clients MAY
apply the confusable detection of <xref target="UTS39"/> to names they show next to
each other. This document carries the language of display text but
not its base direction. When a client knows no direction, it SHOULD
use the first strong directional character, as <xref target="STRING-META"/>
recommends, and not derive the direction from the language tag
alone. Review of <xref target="RFC9425"/> asked for the direction of display text
to be established (<xref target="GENART-QUOTAS"/>); carrying it is left for future
work. Deployments that want enforcement can apply the PRECIS
Nickname profile <xref target="RFC8266"/> to names of people and the
IdentifierClass of <xref target="RFC8264"/> to identifiers.</t>
      </section>
      <section anchor="different-text">
        <name>Different Text for Different Readers</name>
        <t>Localizations let the owner of a shared object show each language a
different text. A localization need not be a translation of the base
value: a shared address book could be named "Team contacts" in English
and something unrelated in another language. Readers who use different
languages can be told different things about the same object. Clients
that let a user act on a shared object, for example by accepting a
share or granting rights, SHOULD show the base value and its <tt>locale</tt>
next to the localized value when they differ.</t>
      </section>
      <section anchor="resources">
        <name>Resource Use</name>
        <t>Each localization adds storage and response size. Servers limit the
number and size of localizations (<xref target="properties"/>) as they limit other
input.</t>
      </section>
      <section anchor="language-privacy">
        <name>Language Preferences</name>
        <t>A user's language preference is identifying information. The
<tt>language</tt> argument adds nothing beyond what Accept-Language already
reveals to the same server.</t>
      </section>
    </section>
    <section anchor="privacy">
      <name>Privacy Considerations</name>
      <t>Localizations of a shared object are visible to everyone who can read
the object. A user who adds a localization reveals the languages they
use to those readers.</t>
    </section>
    <section anchor="iana">
      <name>IANA Considerations</name>
      <section anchor="jmap-capability-registration">
        <name>JMAP Capability Registration</name>
        <t>IANA is requested to register the following entry in the "JMAP
Capabilities" registry established by <xref target="RFC8620"/>:</t>
        <dl>
          <dt>Capability Name:</dt>
          <dd>
            <t><tt>urn:ietf:params:jmap:i18n</tt></t>
          </dd>
          <dt>Intended Use:</dt>
          <dd>
            <t>common</t>
          </dd>
          <dt>Change Controller:</dt>
          <dd>
            <t>IETF</t>
          </dd>
          <dt>Specification document:</dt>
          <dd>
            <t>This document.</t>
          </dd>
          <dt>Security and Privacy Considerations:</dt>
          <dd>
            <t><xref target="security"/> and <xref target="privacy"/> of this document.</t>
          </dd>
        </dl>
      </section>
    </section>
  </middle>
  <back>
    <references anchor="sec-combined-references">
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>
        <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="RFC3629">
          <front>
            <title>UTF-8, a transformation format of ISO 10646</title>
            <author fullname="F. Yergeau" initials="F." surname="Yergeau"/>
            <date month="November" year="2003"/>
            <abstract>
              <t>ISO/IEC 10646-1 defines a large character set called the Universal Character Set (UCS) which encompasses most of the world's writing systems. The originally proposed encodings of the UCS, however, were not compatible with many current applications and protocols, and this has led to the development of UTF-8, the object of this memo. UTF-8 has the characteristic of preserving the full US-ASCII range, providing compatibility with file systems, parsers and other software that rely on US-ASCII values but are transparent to other values. This memo obsoletes and replaces RFC 2279.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="63"/>
          <seriesInfo name="RFC" value="3629"/>
          <seriesInfo name="DOI" value="10.17487/RFC3629"/>
        </reference>
        <reference anchor="RFC3986">
          <front>
            <title>Uniform Resource Identifier (URI): Generic Syntax</title>
            <author fullname="T. Berners-Lee" initials="T." surname="Berners-Lee"/>
            <author fullname="R. Fielding" initials="R." surname="Fielding"/>
            <author fullname="L. Masinter" initials="L." surname="Masinter"/>
            <date month="January" year="2005"/>
            <abstract>
              <t>A Uniform Resource Identifier (URI) is a compact sequence of characters that identifies an abstract or physical resource. This specification defines the generic URI syntax and a process for resolving URI references that might be in relative form, along with guidelines and security considerations for the use of URIs on the Internet. The URI syntax defines a grammar that is a superset of all valid URIs, allowing an implementation to parse the common components of a URI reference without knowing the scheme-specific requirements of every possible identifier. This specification does not define a generative grammar for URIs; that task is performed by the individual specifications of each URI scheme. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="66"/>
          <seriesInfo name="RFC" value="3986"/>
          <seriesInfo name="DOI" value="10.17487/RFC3986"/>
        </reference>
        <reference anchor="RFC4647">
          <front>
            <title>Matching of Language Tags</title>
            <author fullname="A. Phillips" initials="A." role="editor" surname="Phillips"/>
            <author fullname="M. Davis" initials="M." role="editor" surname="Davis"/>
            <date month="September" year="2006"/>
            <abstract>
              <t>This document describes a syntax, called a "language-range", for specifying items in a user's list of language preferences. It also describes different mechanisms for comparing and matching these to language tags. Two kinds of matching mechanisms, filtering and lookup, are defined. Filtering produces a (potentially empty) set of language tags, whereas lookup produces a single language tag. Possible applications include language negotiation or content selection. This document, in combination with RFC 4646, replaces RFC 3066, which replaced RFC 1766. 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="47"/>
          <seriesInfo name="RFC" value="4647"/>
          <seriesInfo name="DOI" value="10.17487/RFC4647"/>
        </reference>
        <reference anchor="RFC5646">
          <front>
            <title>Tags for Identifying Languages</title>
            <author fullname="A. Phillips" initials="A." role="editor" surname="Phillips"/>
            <author fullname="M. Davis" initials="M." role="editor" surname="Davis"/>
            <date month="September" year="2009"/>
            <abstract>
              <t>This document describes the structure, content, construction, and semantics of language tags for use in cases where it is desirable to indicate the language used in an information object. It also describes how to register values for use in language tags and the creation of user-defined extensions for private interchange. 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="47"/>
          <seriesInfo name="RFC" value="5646"/>
          <seriesInfo name="DOI" value="10.17487/RFC5646"/>
        </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>
        <reference anchor="RFC8620">
          <front>
            <title>The JSON Meta Application Protocol (JMAP)</title>
            <author fullname="N. Jenkins" initials="N." surname="Jenkins"/>
            <author fullname="C. Newman" initials="C." surname="Newman"/>
            <date month="July" year="2019"/>
            <abstract>
              <t>This document specifies a protocol for clients to efficiently query, fetch, and modify JSON-based data objects, with support for push notification of changes and fast resynchronisation and for out-of- band binary data upload/download.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8620"/>
          <seriesInfo name="DOI" value="10.17487/RFC8620"/>
        </reference>
        <reference anchor="RFC8621">
          <front>
            <title>The JSON Meta Application Protocol (JMAP) for Mail</title>
            <author fullname="N. Jenkins" initials="N." surname="Jenkins"/>
            <author fullname="C. Newman" initials="C." surname="Newman"/>
            <date month="August" year="2019"/>
            <abstract>
              <t>This document specifies a data model for synchronising email data with a server using the JSON Meta Application Protocol (JMAP). Clients can use this to efficiently search, access, organise, and send messages, and to get push notifications for fast resynchronisation when new messages are delivered or a change is made in another client.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8621"/>
          <seriesInfo name="DOI" value="10.17487/RFC8621"/>
        </reference>
        <reference anchor="RFC8887">
          <front>
            <title>A JSON Meta Application Protocol (JMAP) Subprotocol for WebSocket</title>
            <author fullname="K. Murchison" initials="K." surname="Murchison"/>
            <date month="August" year="2020"/>
            <abstract>
              <t>This document defines a binding for the JSON Meta Application Protocol (JMAP) over a WebSocket transport layer. The WebSocket binding for JMAP provides higher performance than the current HTTP binding for JMAP.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8887"/>
          <seriesInfo name="DOI" value="10.17487/RFC8887"/>
        </reference>
        <reference anchor="RFC8984">
          <front>
            <title>JSCalendar: A JSON Representation of Calendar Data</title>
            <author fullname="N. Jenkins" initials="N." surname="Jenkins"/>
            <author fullname="R. Stepanek" initials="R." surname="Stepanek"/>
            <date month="July" year="2021"/>
            <abstract>
              <t>This specification defines a data model and JSON representation of calendar data that can be used for storage and data exchange in a calendaring and scheduling environment. It aims to be an alternative and, over time, successor to the widely deployed iCalendar data format. It also aims to be unambiguous, extendable, and simple to process. In contrast to the jCal format, which is also based on JSON, JSCalendar is not a direct mapping from iCalendar but defines the data model independently and expands semantics where appropriate.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8984"/>
          <seriesInfo name="DOI" value="10.17487/RFC8984"/>
        </reference>
        <reference anchor="RFC9110">
          <front>
            <title>HTTP Semantics</title>
            <author fullname="R. Fielding" initials="R." role="editor" surname="Fielding"/>
            <author fullname="M. Nottingham" initials="M." role="editor" surname="Nottingham"/>
            <author fullname="J. Reschke" initials="J." role="editor" surname="Reschke"/>
            <date month="June" year="2022"/>
            <abstract>
              <t>The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. This document describes the overall architecture of HTTP, establishes common terminology, and defines aspects of the protocol that are shared by all versions. In this definition are core protocol elements, extensibility mechanisms, and the "http" and "https" Uniform Resource Identifier (URI) schemes.</t>
              <t>This document updates RFC 3864 and obsoletes RFCs 2818, 7231, 7232, 7233, 7235, 7538, 7615, 7694, and portions of 7230.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="97"/>
          <seriesInfo name="RFC" value="9110"/>
          <seriesInfo name="DOI" value="10.17487/RFC9110"/>
        </reference>
        <reference anchor="RFC9425">
          <front>
            <title>JSON Meta Application Protocol (JMAP) for Quotas</title>
            <author fullname="R. Cordier" initials="R." role="editor" surname="Cordier"/>
            <date month="June" year="2023"/>
            <abstract>
              <t>This document specifies a data model for handling quotas on accounts with a server using the JSON Meta Application Protocol (JMAP).</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9425"/>
          <seriesInfo name="DOI" value="10.17487/RFC9425"/>
        </reference>
        <reference anchor="RFC9457">
          <front>
            <title>Problem Details for HTTP APIs</title>
            <author fullname="M. Nottingham" initials="M." surname="Nottingham"/>
            <author fullname="E. Wilde" initials="E." surname="Wilde"/>
            <author fullname="S. Dalal" initials="S." surname="Dalal"/>
            <date month="July" year="2023"/>
            <abstract>
              <t>This document defines a "problem detail" to carry machine-readable details of errors in HTTP response content to avoid the need to define new error response formats for HTTP APIs.</t>
              <t>This document obsoletes RFC 7807.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9457"/>
          <seriesInfo name="DOI" value="10.17487/RFC9457"/>
        </reference>
        <reference anchor="RFC9610">
          <front>
            <title>JSON Meta Application Protocol (JMAP) for Contacts</title>
            <author fullname="N. Jenkins" initials="N." role="editor" surname="Jenkins"/>
            <date month="December" year="2024"/>
            <abstract>
              <t>This document specifies a data model for synchronising contact data with a server using the JSON Meta Application Protocol (JMAP).</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9610"/>
          <seriesInfo name="DOI" value="10.17487/RFC9610"/>
        </reference>
        <reference anchor="RFC9670">
          <front>
            <title>JSON Meta Application Protocol (JMAP) Sharing</title>
            <author fullname="N. Jenkins" initials="N." role="editor" surname="Jenkins"/>
            <date month="November" year="2024"/>
            <abstract>
              <t>This document specifies a data model for sharing data between users using the JSON Meta Application Protocol (JMAP). Future documents can reference this document when defining data types to support a consistent model of sharing.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9670"/>
          <seriesInfo name="DOI" value="10.17487/RFC9670"/>
        </reference>
        <reference anchor="UAX29" target="https://www.unicode.org/reports/tr29/">
          <front>
            <title>Unicode Standard Annex #29: Unicode Text Segmentation</title>
            <author>
              <organization>The Unicode Consortium</organization>
            </author>
            <date>n.d.</date>
          </front>
        </reference>
      </references>
      <references anchor="sec-informative-references">
        <name>Informative References</name>
        <reference anchor="MNU">
          <front>
            <title>Modern Network Unicode</title>
            <author fullname="Carsten Bormann">
              <organization/>
            </author>
            <date year="2026" month="September" day="02"/>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-bormann-dispatch-modern-network-unicode-09"/>
        </reference>
        <reference anchor="RFC2277">
          <front>
            <title>IETF Policy on Character Sets and Languages</title>
            <author fullname="H. Alvestrand" initials="H." surname="Alvestrand"/>
            <date month="January" year="1998"/>
            <abstract>
              <t>This document is the current policies being applied by the Internet Engineering Steering Group (IESG) towards the standardization efforts in the Internet Engineering Task Force (IETF) in order to help Internet protocols fulfill these requirements. 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="18"/>
          <seriesInfo name="RFC" value="2277"/>
          <seriesInfo name="DOI" value="10.17487/RFC2277"/>
        </reference>
        <reference anchor="RFC4790">
          <front>
            <title>Internet Application Protocol Collation Registry</title>
            <author fullname="C. Newman" initials="C." surname="Newman"/>
            <author fullname="M. Duerst" initials="M." surname="Duerst"/>
            <author fullname="A. Gulbrandsen" initials="A." surname="Gulbrandsen"/>
            <date month="March" year="2007"/>
            <abstract>
              <t>Many Internet application protocols include string-based lookup, searching, or sorting operations. However, the problem space for searching and sorting international strings is large, not fully explored, and is outside the area of expertise for the Internet Engineering Task Force (IETF). Rather than attempt to solve such a large problem, this specification creates an abstraction framework so that application protocols can precisely identify a comparison function, and the repertoire of comparison functions can be extended in the future. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="4790"/>
          <seriesInfo name="DOI" value="10.17487/RFC4790"/>
        </reference>
        <reference anchor="RFC5051">
          <front>
            <title>i;unicode-casemap - Simple Unicode Collation Algorithm</title>
            <author fullname="M. Crispin" initials="M." surname="Crispin"/>
            <date month="October" year="2007"/>
            <abstract>
              <t>This document describes "i;unicode-casemap", a simple case-insensitive collation for Unicode strings. It provides equality, substring, and ordering operations. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5051"/>
          <seriesInfo name="DOI" value="10.17487/RFC5051"/>
        </reference>
        <reference anchor="RFC5198">
          <front>
            <title>Unicode Format for Network Interchange</title>
            <author fullname="J. Klensin" initials="J." surname="Klensin"/>
            <author fullname="M. Padlipsky" initials="M." surname="Padlipsky"/>
            <date month="March" year="2008"/>
            <abstract>
              <t>The Internet today is in need of a standardized form for the transmission of internationalized "text" information, paralleling the specifications for the use of ASCII that date from the early days of the ARPANET. This document specifies that format, using UTF-8 with normalization and specific line-ending sequences. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5198"/>
          <seriesInfo name="DOI" value="10.17487/RFC5198"/>
        </reference>
        <reference anchor="RFC6570">
          <front>
            <title>URI Template</title>
            <author fullname="J. Gregorio" initials="J." surname="Gregorio"/>
            <author fullname="R. Fielding" initials="R." surname="Fielding"/>
            <author fullname="M. Hadley" initials="M." surname="Hadley"/>
            <author fullname="M. Nottingham" initials="M." surname="Nottingham"/>
            <author fullname="D. Orchard" initials="D." surname="Orchard"/>
            <date month="March" year="2012"/>
            <abstract>
              <t>A URI Template is a compact sequence of characters for describing a range of Uniform Resource Identifiers through variable expansion. This specification defines the URI Template syntax and the process for expanding a URI Template into a URI reference, along with guidelines for the use of URI Templates on the Internet. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6570"/>
          <seriesInfo name="DOI" value="10.17487/RFC6570"/>
        </reference>
        <reference anchor="RFC7807">
          <front>
            <title>Problem Details for HTTP APIs</title>
            <author fullname="M. Nottingham" initials="M." surname="Nottingham"/>
            <author fullname="E. Wilde" initials="E." surname="Wilde"/>
            <date month="March" year="2016"/>
            <abstract>
              <t>This document defines a "problem detail" as a way to carry machine- readable details of errors in a HTTP response to avoid the need to define new error response formats for HTTP APIs.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7807"/>
          <seriesInfo name="DOI" value="10.17487/RFC7807"/>
        </reference>
        <reference anchor="RFC7493">
          <front>
            <title>The I-JSON Message Format</title>
            <author fullname="T. Bray" initials="T." role="editor" surname="Bray"/>
            <date month="March" year="2015"/>
            <abstract>
              <t>I-JSON (short for "Internet JSON") is a restricted profile of JSON designed to maximize interoperability and increase confidence that software can process it successfully with predictable results.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7493"/>
          <seriesInfo name="DOI" value="10.17487/RFC7493"/>
        </reference>
        <reference anchor="RFC3987">
          <front>
            <title>Internationalized Resource Identifiers (IRIs)</title>
            <author fullname="M. Duerst" initials="M." surname="Duerst"/>
            <author fullname="M. Suignard" initials="M." surname="Suignard"/>
            <date month="January" year="2005"/>
            <abstract>
              <t>This document defines a new protocol element, the Internationalized Resource Identifier (IRI), as a complement of the Uniform Resource Identifier (URI). An IRI is a sequence of characters from the Universal Character Set (Unicode/ISO 10646). A mapping from IRIs to URIs is defined, which means that IRIs can be used instead of URIs, where appropriate, to identify resources.</t>
              <t>The approach of defining a new protocol element was chosen instead of extending or changing the definition of URIs. This was done in order to allow a clear distinction and to avoid incompatibilities with existing software. Guidelines are provided for the use and deployment of IRIs in various protocols, formats, and software components that currently deal with URIs.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="3987"/>
          <seriesInfo name="DOI" value="10.17487/RFC3987"/>
        </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="RFC8266">
          <front>
            <title>Preparation, Enforcement, and Comparison of Internationalized Strings Representing Nicknames</title>
            <author fullname="P. Saint-Andre" initials="P." surname="Saint-Andre"/>
            <date month="October" year="2017"/>
            <abstract>
              <t>This document describes methods for handling Unicode strings representing memorable, human-friendly names (called "nicknames", "display names", or "petnames") for people, devices, accounts, websites, and other entities. This document obsoletes RFC 7700.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8266"/>
          <seriesInfo name="DOI" value="10.17487/RFC8266"/>
        </reference>
        <reference anchor="RFC9553">
          <front>
            <title>JSContact: A JSON Representation of Contact Data</title>
            <author fullname="R. Stepanek" initials="R." surname="Stepanek"/>
            <author fullname="M. Loffredo" initials="M." surname="Loffredo"/>
            <date month="May" year="2024"/>
            <abstract>
              <t>This specification defines a data model and JavaScript Object Notation (JSON) representation of contact card information that can be used for data storage and exchange in address book or directory applications. It aims to be an alternative to the vCard data format and to be unambiguous, extendable, and simple to process. In contrast to the JSON-based jCard format, it is not a direct mapping from the vCard data model and expands semantics where appropriate. Two additional specifications define new vCard elements and how to convert between JSContact and vCard.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9553"/>
          <seriesInfo name="DOI" value="10.17487/RFC9553"/>
        </reference>
        <reference anchor="JMAP-CALENDARS">
          <front>
            <title>JMAP for Calendars</title>
            <author fullname="Neil Jenkins">
              <organization/>
            </author>
            <author fullname="Michael Douglass">
              <organization/>
            </author>
            <date year="2026" month="October" day="14"/>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-jmap-calendars-33"/>
        </reference>
        <reference anchor="UAX9" target="https://www.unicode.org/reports/tr9/">
          <front>
            <title>Unicode Standard Annex #9: Unicode Bidirectional Algorithm</title>
            <author>
              <organization>The Unicode Consortium</organization>
            </author>
            <date>n.d.</date>
          </front>
        </reference>
        <reference anchor="GENART-QUOTAS" target="https://mailarchive.ietf.org/arch/msg/jmap/7D_qXgNy2hyLK9MdiedC8u5mdkI/">
          <front>
            <title>Genart last call review of draft-ietf-jmap-quotas-06</title>
            <author fullname="Thomas Fossati">
              <organization/>
            </author>
            <date year="2022" month="November" day="10"/>
          </front>
        </reference>
        <reference anchor="STRING-META" target="https://www.w3.org/TR/string-meta/">
          <front>
            <title>Strings on the Web: Language and Direction Metadata</title>
            <author fullname="Richard Ishida">
              <organization/>
            </author>
            <author fullname="Addison Phillips">
              <organization/>
            </author>
            <date year="2026" month="July" day="16"/>
          </front>
          <seriesInfo name="W3C" value="First Public Working Draft"/>
        </reference>
        <reference anchor="UTS39" target="https://www.unicode.org/reports/tr39/">
          <front>
            <title>Unicode Technical Standard #39: Unicode Security Mechanisms</title>
            <author>
              <organization>The Unicode Consortium</organization>
            </author>
            <date>n.d.</date>
          </front>
        </reference>
      </references>
    </references>
    <?line 743?>

<section anchor="examples">
      <name>Examples</name>
      <section anchor="storing-a-localized-address-book-name">
        <name>Storing a Localized Address Book Name</name>
        <sourcecode type="json"><![CDATA[
[[ "AddressBook/set", {
  "accountId": "a1",
  "update": {
    "ab1": {
      "locale": "en",
      "localizations": {
        "fr": { "name": "Contacts du groupe" },
        "de": { "name": "Team-Kontakte" }
      }
    }
  }
}, "0" ]]
]]></sourcecode>
      </section>
      <section anchor="reading-it-in-one-language">
        <name>Reading It in One Language</name>
        <t>Request, with <tt>urn:ietf:params:jmap:i18n</tt> in <tt>using</tt>:</t>
        <sourcecode type="json"><![CDATA[
[[ "AddressBook/get", {
  "accountId": "a1",
  "ids": [ "ab1" ],
  "properties": [ "name", "locale" ],
  "language": [ "fr-CH", "de" ]
}, "0" ]]
]]></sourcecode>
        <t>The range "fr-CH" does not match, so Lookup tries its truncation "fr",
which does. Response:</t>
        <sourcecode type="json"><![CDATA[
[[ "AddressBook/get", {
  "accountId": "a1",
  "state": "s42",
  "list": [ {
    "id": "ab1",
    "name": "Contacts du groupe",
    "locale": "fr"
  } ],
  "notFound": []
}, "0" ]]
]]></sourcecode>
      </section>
    </section>
    <section anchor="upstream">
      <name>Relationship to Upstream JMAP Specifications</name>
      <t><xref target="text-handling"/> and <xref target="uris-problems"/> update <xref target="RFC8620"/> and would
fit in a revision of it. The capability and properties of <xref target="localization"/> could move into
a revision of <xref target="RFC8620"/>, with each data type's specification taking
its rows of <xref target="applicability"/>, at which point this document would be
obsoleted.</t>
    </section>
    <section anchor="acknowledgements">
      <name>Acknowledgements</name>
      <t>The <tt>locale</tt> and <tt>localizations</tt> properties are those of JSCalendar
<xref target="RFC8984"/> by Neil Jenkins and Robert Stepanek. <xref target="text-handling"/>
relies on Modern Network Unicode <xref target="MNU"/> by Carsten Bormann.</t>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA7U9a1fbSJbf61fUIR86zNpOeAacL+sm0M0sIQyQ7d3t02cs
22VQI0selRzioZnfvvdVL9km2d3ZOWc6xpZKt27d90vdblc1eVOYvt76PJ9k
jbG6qfSfPw6u+vqiGmdF/ncz0R9yOy+ypb41X5sO/Vf/nJWTIi/vOvrz9bnt
aPhTX9XVqDAz/cE0WV7YLZWNRrX50qf1tKyvJtW4zGbwxEmdTZtu1jxW1aT7
+yybdxd8SfftWzWGD3dVvexr20yUXYxmubV5VTbLOdx6fnp7puTqvj463H3b
0cf7uwdK5fO6r5t6YZvdt2+P3+4qZRuA7a9ZUZVw4xIAsLOsbv76t0VFN5eV
mud9/WtTjTvaVnVTmynsxy5n+OE3pbJFc1/VfaV1F/6v9XRRFLyBj1n9oAcE
P/1S1XdZmf89awDOvr42X3LzqE+q2SwHrF1cnNBF47yBTd2YrAG00ze1uaMb
fhnwBdWibHDjn2/obzMDZPY1AP3wrzWtOaYle/CPUmVVz+CBXwwCeH12sruz
cywf9w53/cfjo0P5uH+4/04+Hhzuu2+Pdt7tu4+AzfBxx308OnK3HR0fuWuP
d3bctYh+//HAXXt8GC44fEcfPw/+g+HS2pNemY+ridE3eFRZPdGDsjRf9Su4
TrvfiOpuzN3MlA1heIuWCKeD/+viGfT17b3x951UJZ5qvpjxI7P6zjR9fd80
c9t/8+bx8bG34Et7cO+b2szhavumqXeP3wA5ldMYwR8vP6eQf4T76lJfGqAC
IAZ56HrQAuGcZLVtTKl/xLXLkq6wps6Nxee5O87LBtY2TfcDMorjlxHf050A
T2bN+L47IxC6JYPQlc103x7TMsgifb37dvcQvukCPzCV7L5zJ7T/7tid0MHb
A3fcBzvHR/Lx8OCdu+Dd0Vt327v9471AXJ40dg/3w0dHXMcHB3QtioHuyeDi
9PLD4PomRSSJCMA14KYwSAT2W0i8NHmh/2zKh7y0a37+mI/vM1PoD9Xirsis
/R8hOTfNlEXS2IHT3dtrI3TnbXdnnyn6Owk6oucf80lemzFSclboQQHCLm/u
Z//fVA1ErfVPp5eD69vuXz5/uh20zuEnU4J01ICxRsPeC80iR1fTFdSgBM1A
WB9+66Ru76tZZvVZZS1wUorF3e7ODiBy7S5Q8GX1+B6Yr4ePpa3gF29m9u4N
wvDm3Ye//u0/7i6Xu/fLi387/jjJzeTkaHEwmzyc40Zvbq/PL3/qfjy9HaTb
vGlqUF5WV6VuAK2/mBHou6y8W2R3hnTZB3c4+iNoMwA3+9Yur5Hg4KjP7X0+
ydZcMJgAz8KCV/d5UeTzTRT5y95JX5/lICH01WJU5GP9C/A1QKuJRFe4+l13
53AjETzuEdJur99Y2nF3BrtBzHy+vdnbQLS3ZnwPH4EqPfm+2oso98aMF0Cr
S8AM7LjM7WwDr/7zqHYPZXG329XZCPaRjRulSGC8BulC6n8biLVGTGqkWTwu
DRT3+fase6TPu3+++XTZ0YVp4Gc9LnJQIRrPRGdqXBUFqRMSPgQdGjVIAnI9
nNAXU+tCrCG9gC+6X3Kbg62jGatWTetqRpRUm78tjG1+sHowHpt50/VUdW8y
ENQ9fd7oe4CtrPQjmFRgbdmmqg0gS9WmWYAymYi11ZC1ZRfje9wLLk4wAydm
GlljVH0FQCeT2lirR1X10MFFiCs7Oi/1DJdt4ISAyg1wNMPBe4ueDv883gPt
+isAKwTSRHancwvL9eAk4QNYbwtUwXpipnlpCC41BLD7yKH9eVZnM9tH3uzn
O0flEM5lno3yAuilI88BkK0eEj7NEKFRQ0EuHYQd6nldzQ2chAFDDNVbUQAw
cER/vnHaQU4eLJHtDu4CoYjxhlgyX3OLp8nmJ9EEWo9irGYAgmwYgKjvaFfq
EWSwA9NRSmYfLFFHjMYeiLNarkAkZA0SBn1QbjWALEGZGKyoEsladQixpgBZ
w0f8Fzw+NTF2XOdzosvRsk1KRENZYatkRWQDTfDfLUAAlWNDQCM/EALs3Izz
KfA1IZkkHyIKcD3NC8SKcCmblO40OmhMl2P5jIhDKHGrqBESSiWsIq4ICeAW
dL9kxQJOLhwnQFQU1SPBizapLAjIM8BjSwb059vbK+AFWy3qMTIUCgFt6rqq
LTICY+/gHS5L7saE3Y0eS4hZPpmAYa1eoWqvq8mCpfjTqzz68xl+f6V/wQfT
IwdFDdy5RA/mSw7Ih8sd9TyLqHl6Etv4+Rlwypdbg0a8hX8BepCXORkTGet0
QaAieYAod+hLuKgyKApA1wKf3iH9mFkfNqL/9KfTEk4DAOj96U/6FLEDdwIx
m6986aSDH4Es9CgHlb0EWiiqbEL8BAqieizxzw4yLwtA3gHabbADg4vD0YCY
YCFJP6LH8PwMt7+Od3sjinCnd7Dd04M11BS2URpYlKUKLJPdZXnJ55tFwgTI
Ip/wc3u01RsSsd3xfWXBKhaZivv+5R7+9iKY5SPJcPDvQODKkk0FzxqBML6H
XYs0IDENu0fMVrAsc1csZ/SqzIZl1kttQQi6OzFCdnsHvf1tVhbZyBQsDdGj
s3M4cMPsCFoPjP1ozbXY3esdbfdIW5II0MNIBgyR2RgCEBt0Qtl8XuSyK4tq
oV6AOoK9ZyzphOeWjOATp+UQqQM9fAMbrpdDdE5RYoO0J91CqA0KUfCj2EUF
ZC89HOg1PD8HgeCUJFzFMFWoGwD7djEnJQ6UBuvgL0P/BG/0BpFPT6Cr1qqU
MailIawTlMpaZFq9S5AdEMUiTkFbZYuiCbuDRYASReR1s8esBs2I8tJ8zWZz
QOVW/t65UuPMghM+3+Kto5f0/OzwSkdLLIoqGdanL7w1ksPOkSjRNARpIdzZ
pginCNxWdpBDv86JbOEgTAa/jSoQOICLpoeeVFCEfA8oQpRLsGf4CVYHE0kI
Bnwv+KUa/U4qBuFaarROi9jaBdR3/ReJMpbzyGvcRi+IzXMLHpa1yH5Pr+6y
uX1mqfUhVsJo56DSJD3g7A6vQQFpt7FRg/61N2tKNJfRsvmRDJvM+4Vo5MCf
V8D543yOQpeMNACEwiksElBMWUA5CKPYQEKhMEGFelaDALwniH4y6E+jPMse
TI0YQtq4z74gDRdLgh9BdHYTS2GQb7ZtNpGco92wwQTL/HhypXdEuKLPjWfk
NKQmJm0qIEn+Gwzb0k4RBkIeCLRsRHsCruZzIxHmHkcHg7fhxa+dGNnv7W4n
tBnEDguUEXH5431VGC+n8Cg+wT5R8/ovic1KebKjHxDnTtk5QLw95aWeRQ6o
UB7gmYJvdVONH4wQJAaSAA1iAot4RWwUBcN9y5TD4UVE5aK0DVg5E4RynSUz
qUj1sMp5vDeApVoEEj6DjRkjRgr8DlaxVykzINXxIlZP6GCBIqkBd5Zoza2Y
mJd0H2FmZsAFAooj2DEWSthw5go8a1ECwkjwJiaEMyrFikGdzXZMB0OExFdP
EnJBQRsJCDR+iKUtnGGD+EcZQQ+EVbxWG1ydd8Qo4BNyNoF2thXcOYK9I/Ii
WX9jKNDqr+rQargHwLF8U9VhEbHfviLC8DxQOU0mPbSlnNX3iIqdpQDjhPFU
G/EiJsRlI2K2DilNWASoAwOdCAmqNsQVCyK7BPn2FWHA78qq7A5uTs7PScaC
3INTZzlF/soHZ2k9vULLq+ssLxBXT09BjQA+I4dmg/ZpOzQ9WCIWlu1FIhdH
b3ZxlNOha/wRPrinJ9L24wCr17Mqsq1jlyd4OyIk7s2SbAb0+RLfRdHvFdiR
eSkOi/MqwJyKrY41fkpqpIAq5pjQ8zOo3bMFWGumzawoUrIJPg5NXThzVQjI
Xst4BYQOdrQ/WL40j11ckJ6gFJ3wiCM57OTFPAqyCkSIGGGrkpgMgxXXE85Z
nBSbiNsu/jDPGjTw2cF5eoqiS4Cd2iC5go5iviaTm4PHcgYiL2KvXHlpjsIK
uY68+2luismKw+1sbOAuPnpQ2iK1fChRzyRaxY9sw0hOYwD0vbLGwEVgtUwX
FvFt0bKBrSECu04Ii2Xx9LSogYNEYMGVQiiJXCPm9Q6oOJlxkkgkI2tAZ8RW
kf+nEorpePlLvE5kE5t/pGpRr9NxLgk5mNIJZCNmh2MpEQ6gHVGiEU1+tuwJ
JQIDqcvoB1jysarhTLc+fr653erwv/ryE32+Pv3L5/Pr0w/4+ebnwcWF/8BX
KPjj0+cL+R0/hTtPPn38eHr5gW+Gb3Xrq4+D/9wilKmtT1e3558uBxdbmtyp
mCpQiAL6wFgg53MOPhIaPdZre9oZUf++Yurf2QEnTw5t5x3ajYBice7J5OE/
ncgwYGTCEhhHALznDdBQR8ED2NtCdYqcCKIGjLA7cH6B6W3HmdFy6N66j+SF
Cwao9b6mUrEp2Vd9NOlER6NhM2FHM3b7MrRjMcIqllqCkhFaB7aaNmzqu7Ba
5oy7GDSxMcmnA0AuVuXRkgGKvZYsCN1Y4SGFJmLJhzzwIMlVH4usp4emjjWz
CcpL9CU6IvgB7khGIoTeBs3uGLIi+obJgRUtnCR7MYf7h8TrwAqBm55eRSpR
qYEzkwgM78q1KHDyBTnN/o9igUzI6Ay6r4BVgxeoxAskod42SNb7z2D26vPG
BqSDHW9m88bZrj1maPKVIziYwK2HJxtT/vUkAQs1K/hgSn4k+c4GWeT7evQk
GiUGqiHbEw6dxDBogBZ8AxdxJHQ/ZqXo2pYw85KMXYDoLBT4RMUC41cvnYLb
6gKdphXPW11zNKTHwZdVccuM5W7vxCgYGfSbLEqHvAUa8ADzJJkofQwNlCYn
we7COiXSP4VfrHrJdmKRAgvU5ndvj2wM5g7zkuJNA4c1vJ9CE4/VosB42RJM
9IcSZYi7M6EwFSI0xxJNICKKlBfaNEIaxPlqPRl5DS7H9NIpdRRa3CSK16s8
wX8fA9lvrGmGwf+MoutVvWLhwO2MOJAGhCGA3iEp2OxDYKzmFHW1uHdqDYb1
BgwDLZ9KGMUxL8Yq6znIcfWPf/zjdxDS6glk31bM/lt9/UR5oa2NsR9/Cd66
GkaCn39dG7j5jW567rywPIZvcPkXL8KjoYuUrLYlBx0Bn+3EUOJ5wN9bv2el
+VdRili5sdVxV+T2irRWho9v6oWJfrkG9/gTqGT4ZQpCI/y0hr6ip37nHr9v
n4Q55f77rJ7xBMX2XjVOWc9EHNEtgJBDtADEjZkaDL+A3iJX34WHWYTMKUZP
PiNQflm54KxQPfx8h+Ecr8AVMofL+IABsLD3CEdkP0qkoR3YBWETKNqnbJCb
78CqWL7nuDGHBGwAH8AozLRhcyPV1dXUKwhMDFAMG/Xr+joq0LWJ7yguq4Tf
OFqWRuIih/rpVdAJpKeD6UHoxD3DP4XBND6lrdaYMBqj8yC/HhNzmfD+ovpI
xI/yorqvh5xV/6NcFAV4gxJz7Wv8e1txKjixS0TLS2BA/mJ1+ENi4gDhBRB7
+hIWpMBL6qNxsIhEuThP95kLyUuYBh/ihaOzhSR6GoXQekc91Racfn+/XmHd
zScC87eNmx2wK4lxlSzdNZFOtIbTNgkUAPJObx80Dh1oR7TNxGU3GEkdfZd/
kSjzeqcZw9xiRYbMZYyaVcREmgKhWI+hw94OB2okgYKWuYTewWauHsXaSn6A
G9tPAFOcsl2nGOFGX4uYOMZN3s58r6VkYD1OLng+cEZCZBC6gKm7C0gMr8TI
3SB5JiWxKClHQUx2Tdc9970OiRbENPDaDB/5YMyc4R5lwQ9onwM9F8klslnR
ITLihlH2NuyRfQri8YzjE3gvSnLcqeMGjvWEu0T6rQfhPT4DFhC91NHDp63I
Ddpian4ecrjbma+4XpyglsxOa2uxS8KxPtTGXZA4GCfEgjqhe/ZEgh3f2+nt
gJ11iUk9kE1IFnYddWIIdpJPpxgaQHTlJT3B1zcgOc0oJgwaJCs823c0uKkV
OZJ4fU/fSKhYHHQuxyCo2VLmQHjFJTF4i4utbAA+CrAIG6QCbkN4S0qRKqH7
xppiyu49gBDoCMTf9aKI4nqscikpkagj0DRjXjZT64g39oELU94BLxc5lapm
FFRl54SeSYUlYFSBJi4xl5LNKnxcPsLokO34wGKL5CkLw2qdcavkQmdCy2Px
wCSoSxCQTV14rem2/dkDoGrCAK9Gh4+RgIAi0AIFwvkCdpCiVYUk/Qiuay/y
dZ1X4e3qcW0wygXcKPEu5sQWPaoRXEapHWNTwUeOPWlkokk6N/GjUs3QUd9j
j6MsxP20ns9iXTFHWFY8L8juRYl5F1fpAhSbz8n1JN6goLQWGDSVmaKfwckX
xhLGcaU0g9IDBJlQAHuxHFimXFDeRKTwcfCffMws2BezEXLwVKXGDqaOkREt
xnQcUyCh8PFwGNUrIKQmRTDASXLRQOlOi8slVsTxRmVCHq3ykfQ2Ha6oEcpp
Aj9gmAQzeAU+lLZmHlXMDBh0p1SuP3MmpFj1UOUCw+1MagVE2PHO8mjpjMtV
ZeoTex3ypRuJX6KMT8Sz+zneBMjlHDzSvEkcehGJtZmBJlSJYpGMEawRwd+R
I8LLaZ1ElU/xVIFGyYAm8UKuOCa1nWwkscAIEDuFdWmWhEYQNQr5h0uucptU
mbm9uTQGCQhbzUycskTwAZDsC4mGBi1ud3pixdznsBWyhinUIPURpQvX6EEp
HQgS3Rcyo6cFXSPKKNBBR9BjXS65p3ygxUsgviArueaHylhCaGfFSiOC9XrD
x1PISicIJ8P1MbOD3t42ZZfjVBClvtshB2/wcwCEWYgfhEFF5i6iPbVGVWfT
xtRiKcLWsqIj0o9EC7DsGYc+uQwI6yReVlhSIYNHkgSg1LyaLwo69BeTb6xc
WzIJg3J+Ac5OUdGfy3w3ogi8psYKox+IUrJimhRqKlduIvUMLDUylAjOLe4F
f89JAxc/Qc/QZZ2cX/osYu27HTNBiyvgHb65A1XWUa7yhwlT/jph0h1i8ui+
mtgNNTUHqDcOegcdxbU1h9srYW+UxxvMmyZ7oKoglU0muVS9u92RF+l88eBn
veRcYSAcH++xVzP7MejY5JKaZdtYSWobCT/UBstwplhkLXFOsqX9YaPZ5akb
dzumQinOrHBxLB0gFhlqRK07nhAjIw1fdnndqRP9ftEqyHumQcDBDumImRR1
GQ5pfMEieMRlbCnYvpPuln2f1RjpvFjY1J/2LOGEWgRiT+329IlUymHAAB3V
EZtqF1X1sJhrOwaWMKECLEXxXm+fgkpNvZRkrjsRkgcBLSBAa6qD/sUFeKjw
cYaSAAQzrtEq2lvZgKuGQA9gZDTDvwd2sQi+F4xsbzHEiklKC/DRUoJISRP2
uDtRDDb8mDtrbgP2kWbcs/I6sU0jo3MfnY/GJhEJlpItKqlaz++pg7DdNXYA
o4R9D+zeqF++FLA4zliXJrukCHmwkhHZo0oQmAhYh4tVRNBJqaenKF71HKWy
0ZFFObya+BCvWwhHsWMdCInSckSXTlvaxYicNl8AYzCfiQKKKYxKXQxVJWEB
OlXa0rHzz+D4bjkqlP3QVy6X6L/qnvy8lYiZKEGwvx1tRowncpunaK66sL+D
yEmFUAUAlC8ZECQF3PEdODxYbYWVBEmBohr+6qDpEKTwX1Nu6d9ARTuOfcjJ
dJIN/mmL8Vtx1oW4U3EO1pVwgasEz8Ir41oPEb+O7VwYwBnUSgh7reglnLhg
UErVvATW9xKN5u0+BZftZ3mrnN2F+bQhVYQNffnp8M3Y6TD6RfzmyhpvWMaL
RMHdTGIIeGD+GNZVZff+lxpYDAwpGgCTkze1oc5YoHVB7/B89CjRogB5w7qc
AtiujpdCReWmIFUeKi2yiKNcqj/y2cAgs9YkfNZiznFGDCKKUoGKyFlDMt45
pxYkBliESFez/GusrK3oVLwWPZzGgLgi/8iXFqX1z1KYBA4nBzUYs4XQ2Gip
2uh0oV2pXArO7w7hKunb4NonlVYvbSjRhm3mIC+j3F9Sii4mNFIfkk9anJXF
0cm4rWdIHVjSCsNVgENJZ6QtDo5zXpM8lSqc7ZXMsZmg5PCuCsUlQTZS/r+5
r6vF3X2skiU2Y42r/2jlnOF2iS5WQpCgvGuuUcza/jF4vOMHDnGT0vP+YnJ2
sTv0KEvxjSiPnZzwKmbFhU+bmTavQMqtrfScwkjjulQdH2w6YqxvWHVZYECO
dVD6X8pHpnmBpYj4p9oQtRaj0oYkCK8jDJ5GNyIgmMl4k0FMxqEG71G2C/zB
a44K8FsyCpwgtrtIENtF3oSEgxcbYh54i9ZlIoCW17uYB75dRsLWGPmp1KRi
Td3ubWodgfgmrEHWpaDR6Gi5MS61QcEEl9/IqAXBHRi7sUP644Z1CTGcP1AR
t6C5gx6M8oVYPgAr4gkuXCI9QnsEaLysh1CidCoEUVzbQ0JQkgwFTgCNMjZ/
CdAmXm/oixmOsxLo4SQrxuTG+gdyfG5DEOBwm73RkBudgnHJxdyWC7mjIu5X
j2Zk6TNlHqVcJC76jq5+Hdd8Bym819vd3pCYVUETSvPEShgZnAyTfUONUrAq
wAEcR1SAJY32Hl1RoZGVtPBU5ILsS7kirHFVlgx/xzkMer6opUljuklh9BhH
q5XxEXCCiJWCfdcxettubsyd+0YVagX3NCRGuVQsCXeq16kBvh06D2uUhGzU
Y/iLKpg2tHoqysbzTnxWH57PvmiqB1/AiKjIgJRZfncv1bFRTkJK2tt2AMhL
hRI4qJ31wYq93mHPNQHtEX3rQVxEjXLt1MV4P6BevqVq6adXaa31/87qY6va
FWIrLsSmZrhvFzaxA9AWOEHelU4/RBEckGeUQm04UuC7sOIUepRAJ26naD4G
qGDPWBgCW/2DMUGxnD9c3ULbhYaLQi3hH+qPbrfr/w8rSMgLLuP4HHyI25p8
SAZuBc5wV8u15FZfmqbrOsal4pNzbTvHR7DC62g5Far/3keWCMdqRVjMjJjc
vk2OhT83zGEltySyomgdxUAnRB1jV1MV2XykavlbNJhwbozCVKXLiFF2hPqP
EgMJ73jfCmVj8aoN1yheleKRXOYdHkaqGNidY5MZ94KdxJZsU01AROCS8BSf
jOAHSzrZIZwzTXpYV0CMihp9QPzk5YIeA8rZVu9XLCfpiMfAJ5o4IpSxBkGs
C7g1IDFEk1FwVFSomnbJuSwYKEMsR+vpH12Tm/VGA1fND6WBzvWLe/X6eh1x
gZnPbuf5BGu8Q90icgY+h3xIT3KsSjEh9gN36/FsAAnVqLmpsJINS+UpDg8U
ZS1nEWwVlwk5KVyT3P7BJgaDhMhrzJzCPfk4KlEIhdPkOsj6Dk0dMsdYpc30
z7cfL3r63zPOY3oh6hvAjmLRC0jZTveuOI+E6bwvsgaZ5su1rV1iao58VIh3
GAIWTs8An1SUlRTY2SyFqx21J9jgsvaklGq6plskklPkE6J0FhftnyOr2NP8
w2cS0naWPza6kCC6fkSVGRfm1ibKX3yjeFatCxG4iEsKxDobGcveNoHmm/wE
hLxZ1U85DeFKZxJE6/WlrDMwGbs7SYaKLE6V+h02Dnmm8cFVNyzESGN2plwn
5n4FGeRVrGZDnqN9BiKRxlckk7F8/CcRStSL+k1yOUx6xEXPCWgnmIshJRfa
dOm7qFfXh9ky3z6c1N6uyWe9Dn3PIPkO6Jrd3jsgB5Aa0dLbL/YUxcmaijLB
El5bW/obbnXFH8Nok2ShREdzA+Kbe4Utf/onHUxoA/7msbxbcywIlrmMykWd
VsASnnrSqj3zARVxPpp8RunOzMXpXq971B41JngpHPVteL9GiakyxdhS3gTP
P/LpIzJ3I6moXUM+uzEVyQgt2Ho6cwvAEjiWYBTNcbyQvUeFKLICZHLbgKXj
7X/vaan4cHyP+sazUeoKlH2OJ1g265V18LZArWJzT+sy9G3IfKVAmHvkKbWr
xum8qGXefd1unReTQ5HN8pKhLtGDF7hCRVwRgxTxxaV51Ddpc+TTq9DgSBVJ
SckSG3CYQ04H2jhDq9VnhI3srtMy5nlQyqHlEikZlvhhU/0oKWqMRufEvt9o
K3EtJXJiM6RwD6biapdNZ1JHItFds5AUIPeFrnQycFOzl2ArWyWvL5lWiUDy
NJdXaYej1LNb4dlEK7JryUN3vt2wyEYdZmj8pMJ2D+OLPVK+oZHFrwt9usED
XHugHvNaRIIbE4Mja+Qj9Tavnd+iZ9mDj3yKb8VzWFqkqEaLvCBnk8U3y6dx
7qpdHKLyEng0ozwblrxlDVvCcPDKhzl98ytiTobVEFVgID6fA164L86GLnyq
NwU3RrH5ItNq0gEdKBsP9xd1IXY0kwEt1Y7PKNcoJWBL8QVeeiXjj7iknj4+
p62HOjRukkUOXjzVLJNxV+FQoSJqPdef/+Ut/A8pBD/tnBFw+PHdmfvy+KxD
Rbfi5wN2ZouiybvUrbx++lerPREZA4e44bMG+uL88lSfnZ5+ILrEvgEM17wH
GD//y+7b3SO+4Ob0anA9uP10jXinH441fvPT9eDq5/Dre9laWZXJrs7Ozk5l
L/Dx7D2WhHapdDQj8oOvT8/OeMIGATxaUtHkhKYs1A8UCKMdUos0qbgLwE5B
Pf94dCfX8AWJVusSeOylU40DXNadgMKlIQNYO4K2yWOVfLd+Gieq5Y+Xn0O0
wI2H2dvucNpqwjlNW2nfmLm2tWUOoPuAIABEGjxhfnTcWVwaoWbEnxuyxSJc
hYKmKGi+4/LieI3z0jkaQLiKoiIqCoe0ipikOjJRBARtWp2KSP2uYtOeiJKW
VXsgDeGr1k6I9mOmMwshasaFVBh4ugLGDMnCBbB5ifP9yN7jIiDuhbcdHONL
s/lCfv/q+vTk/AZnuWB6fXaCUz5dPGD3MK15xaNGVYZQzHl8BaWjQDIDcqbg
nwAsi4ZqIEXANXyZZNCkvNbJPe678FElTKc0i4nppEkbcfQtjaiTM1EughtN
PGt1vDs69E1RyXgtFRLWzBxIMFNAQpdlH+GLp7O569IZDCic475ep2KypKzP
uqPCWWNxnSh7BFwa7Ue+bCwvFFsnHimHZk78d9xoHMnadHILgxqqgrnOlADt
SLm3ajaXewtPUr93AgvXVYBDHUcd43Djep7sqXRLSYZy2UiZsIdbKpUwzkOD
28pxvZyjcQu2JhrglDH0NWaOMU1Wg7VRu9kQvu/Vhc2KRyxirw39zo3gLhzo
ehlQG7RTBynkWHGmT/Try7OT7Y6PLMjmmctJeIauBhQ5aIWu6VR3GU2VarFY
bZOKgi/GKCCjngKk5Y6HG24F9f9e8YLUq4EHM69y6q7DmzCX7IJ3ZG9RvQTy
W8vLVWvKOQRSnMeaDk5psQpRb9K2dyKGzGWlP0pqEem5K3lGIGbXT0LmW3oe
SNcULk2HCfGtlEeh8C1WXbHGGaNAorbqvFpQ9TeVKHHqnR3TOjUNcFRDuVRR
hpza/Bqq7vnqh3r2PPTYr1VyswvSXAk4q0kngoKHaxdjDMwFCcC+j4/bU/y4
FXJ0x0KjO/s4ZJUD3sCZ4lLnJd6MxSOAm1oq1iVe6NztrXO8aEtSk9wpcsHt
IYjZWz+WEutl6We03C6iThaq1HUJKWf5t+bRUGMSFuRyhKECtdSQvUhmcdDQ
ogCZIVac6knVI38uXVz5jiIsjRGQ/EN8p4IPAMrUqfVMI7lgKgrhkcxxByzH
1YfyU/tAuKUninLgMDmZN4Eds2qeLWVapDd3aSpWQyTxVcZt3NXZnGpAx8XC
olkzAsSB87ZEH5zGulNqkSrmqNAOaDznmbueeXuY2p+T078ocLKIFOWBRqJC
BZGhmE25z4ovrnIGT2PnELYMRskdYnOe5TyWpFSpsyXecIVK0J29jALeOexo
SqTHBVWPvgppZGQyJc/LdHNi3DhE3NaNwfHTFF+Urzf4WnHZg5sJtXbUcE+1
YgDc4CBd1OLOUCkJEvNk1S8REYnl6K7wNjwoCtnyPqnIs6KHc+4rKq73VsdK
ox5dzibP6q+KwQO5UD0Y9/oDKQkzM0oKkD+GIFvGH1vSsCEVl5bIcAvT8p67
MrrkfeAUtHQXNsRoVFO5yhUp1UOpTcREoiKfkYOH8To4r3OcJ1c2vo7/kYx1
nEp2e4I3bZp+KpM+KSGlSulQIx8gdXWZ9jL9CFZldwxXPbAlOQbipSMCMPzh
8TxG/u7vmOfJKbw1Rb3vLd3zweWAdqH/Cy/BQNyIWx253SBEQYe4EF4UjQxl
A52UII/oXdcXprDb+Kg9xOpWVjufcGl61rjpYmTUIl6F36mNi29yRCpawOV/
1AgpFFQ9hWX8pLzWS0OiCE06bep7IjQX+QMab63hVZ2oAFIlkRv9/xO5Yfqj
HfIuyMKNvD4/3Q1WdQMyZoYa4VqTgzJchhz26wunTqSmEn9YM9gHxyonBRfg
BlMzJEhitcE6lsIs7AMs6F0X2g9piFUCTqTEx6pQE716g3BPCwwaSwmcgkDf
GsBx4DN8vwTpjVifDd2wws8110Lil4IqbyWar3OKAlRyK64OuCfEOzJCvqbx
gFEha0hdx/xaqvN0fDMg9dqNHDoPXOn3946gjtU0MmemKD2OEc+JhxRHAeSS
6UQUxGtER7WzDTjGUnEqxuRQmivNFtipSA9nl9WNrOULLkt9Dn9GHKg2PAaP
4iTywcXv5SmKqFOxL+u+o6m0pKPIvczuwrgxX9BueTw6tmiOsXLJTZWWkOIA
hM4Mi17QpFOBiLgnlOvbB12qIRI/LJpyuYocHHiHJlTHtyvMsOYZcYBxA7Rb
/TBQKaLJ2qApYK8m7vb1NZhENexk8lmjNOf2ZheEi1K5NM8O5xzB0Y8bb2is
pf3DHvYfretJbkWOXYshF+gHD2U1zBQZCVYRGbRmrS+TkG0M1YaIrVXcgc2y
qy2UKTjq5PAvFCyLdSQ+xMbzSuPJpr54+XVSnLXTUdSIjNSNpVppwdh2R2w0
J1VyCrpH809da4kfgypBGuOfy1VXPByBtVPo2xfAnWmGVWWLUoIdWKZCKsKN
w2URQHZo3ALtm2PprQ0rxdqqiqd7MNDbruyQpjlzTpHL3NKR4Zne/0oTTg++
fsXIV7OwZEOLZ+t7QcWOjQexJttz2SgaZNGPhegL413X2j/qHcXQvlVVGdd7
iiuAPJqO9GczswwzY6kj52Uq58yXSo+E5mxG+YnwLouUBqKmWAwC+oPDoebS
mOovdM+TVix+MRE33p/ACdgt5YahO3HlY4FsrK03EeiU+0PqP8y/Yg3ICnus
szqPcYK5FD+HLgHtuwQcZdMs3cg5SMPCrrde2lrZU2gXlcR0GtVREsZA+roQ
qsM1i20hwJem3Uu3IUdhXhh970JXlAAsYbtwIqHDhygo4oSOuJh0JSOGi0UZ
LzgrNsRknrkA1L+4Bt9DA1K+9mlXK788u9mgMg6VHp++qUlmN8UjU1v5IjLb
WYajKWA3vcMlHVCuaEB5VcsIHGfRd6iWEEMHNIOCVuUDjjQ4NbNH4V6KBnEV
YoGrwtkzb9JbfzxnjuKNqWmw76MAPc954DTOo0yu4IGb7PMfU1WJnJ3jLFBa
ZOBNXkKL7z1a8qgSLq5T5OIv2PpZDYQQiWHy6vBIn51f39ziK54+Xf6kz28+
XQxuKUOl6PdjffXpSn84vz494eGp7hIZEGCokk4PR5N8qA3b/IEIkWnCsJJw
2MitQrWksAShqJtYe7sQ3iPQ51dqdOA6bNx3u/rG5UQTJ7j1WhVsW6RYIBpL
VA7iz6znXo8hpiEOvuLhPO6KyHhXrr2Tmp7RYKniucFZlMOUoFcyOVgFx9AP
wgdc1LnMCggDiL3TGvcrK0rz9dw7EdO3WeAsdOADl7QNS7VQoXjcKxotUreC
NJi8ywyI8T076FKR6WoMKUdCJYYKU4M9sGzmRbWchdpZ7Dp1kWk5nVIHEuBk
k7rMxw/EwS6j59JNhzERAOBSNOoqqIL/wGkqb+1wogrrrfwVPurs+PnW5bTD
V9dUYoqiy7M9pX+ew7Ralm2u3xA41tSJ3BHzhGg1HUuSRbLEKZPkzSl+QBZ5
hNHcDOephbbQ/oqg4zcxjF1hKWJsorduTTbTrmqP5hyflnd4yuRs4vQOrn9Y
lORyssPrTOUw2szhBdxoihD5jahQ04oHO8IwWDGJcmRs7OtsBO5QSOC5ptOT
eEIGZzbJzRNl1UJqq1BhKe4IRe0V14XD73eAN/quxgYIG5IfeCJp9ZevFPYR
L5EucZW/a8GLBCtvj+nJ+7KfYdWnV95sBJKh3oHkhKlFGlNtLi4XXu4ADwoz
s/wgHyWDfOi00NLAds+EEts9KKIQl7IG11rn5XzRtLqRrrwXYOPRGHMQPtmY
xxTLKI41QyYpKiMOHRcAyQs9q9INgF+t4qLdu4qbkVlWNAkGTn6lEFcqxjAH
lxXWHQiRDptfZHhcMairdkfYQ8q1a/gUica9dc4FsTDegJTOSjqbUOjEz6dh
CsXfaT9ZesIe5EhU84EoCRJz/zQXs3PQjuKQK5vIszJ7jssTvZd8zZYyv3BH
0d3UxUudVdxbmBjhoerQ4CtwExtcJbNOwxuJYnUAnBbZl32lIlgu8R2Mqv9S
CZuiCBClOoBH8GJ+AQWsw4nDEy73KXBah7yEOA3fe93ep3GXaS2aNz857LmO
JPC2pydvjbp8kyOT55WJz/LSM4wB4QHJ1F1+fxl/5JO5aXjiXRZNI5WiZk1V
zYieMJv311/1VlTzjMn+rQ6Nl3WTZ88nONU226E5tlscjY1m4I6SIbgstPAG
U4bBt4l4SKfXTmv8O0zP9ZXdkwWIzWoxN1s6HmI7Men1qE26/4Y3PTR46box
th299XZL//Ybj7MlAcmVTOcUnML34fieRDcUW+o7vq8Msr8Zn3ffwGc+kVnG
iEj9G30XhCf/RHvteOTKVY6V+ZppHeZD6N/ae751Q1rchaHQhLLMlBOSWRKN
f51VeB8gnVNHsReMt/Z8U9//Ye+ULcUv7P4uf4PlqrQfoa6crx/tCC29RCZy
RaBAABnPX9AFez1DbwOXX8EPkoTMA7vP51S9N7fYezqTqEO7enchPz//n16h
QX0RVAMw5X6jjF7C614P4sJc8RD7ctKaNbDyYhq2t2guW16CV5KuGT1eSJws
Ql+7C7q1FZrJ8I20itP3j/LI1ltqOpg/lnAM1W2kdXWutchH8CbcpTlGP6Yw
kzsyw33n93e9Syed+xHKi1Wc8QItEb87mpa8rkYYUb9pzDwrzUNvNYsEOr6Q
MZ0bygxdoQys33rBd0/9N97rC2tpfwAA

-->

</rfc>
