<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE xep SYSTEM 'xep.dtd' [
  <!ENTITY % ents SYSTEM 'xep.ent'>
%ents;
]>
<?xml-stylesheet type='text/xsl' href='xep.xsl'?>
<xep>
<header>
  <title>JID Prep</title>
  <abstract>This specification defines a way for an XMPP client to request an XMPP server to prep and normalize a given JID.</abstract>
  &LEGALNOTICE;
  <number>0328</number>
  <status>Experimental</status>
  <type>Standards Track</type>
  <sig>Standards</sig>
  <dependencies>
    <spec>XMPP Core</spec>
    <spec>XMPP IM</spec>
    <spec>XEP-0030</spec>
  </dependencies>
  <supersedes/>
  <supersededby/>
  <shortname>NOT_YET_ASSIGNED</shortname>
  <author>
    <firstname>Lance</firstname>
    <surname>Stout</surname>
    <email>lance@lance.im</email>
    <jid>lance@lance.im</jid>
  </author>
  <revision>
    <version>0.1</version>
    <date>2013-05-28</date>
    <initials>psa</initials>
    <remark><p>Initial published version approved by the XMPP Council.</p></remark>
  </revision>
  <revision>
    <version>0.0.2</version>
    <date>2013-05-21</date>
    <initials>lance</initials>
    <remark><p>Incorporated feedback.</p></remark>
  </revision>
  <revision>
    <version>0.0.1</version>
    <date>2013-05-08</date>
    <initials>lance</initials>
    <remark><p>Initial version.</p></remark>
  </revision>
</header>
<section1 topic='Introduction' anchor='intro'>
  <p>In order to properly compare and match JIDs, a normalization and prepping step is required by &rfc6122;. The responsibility for such normalization is split between the server and client, where the server is expected to prep any JID slots that it recognizes, particulary those related to stanza routing and roster items. However, the server can not prep JID slots that it does not understand, and so those are left for the client to process.</p>
  <p>In some environments (in particular, browser based environments), a client does not have access to the various Unicode and internationalization libraries necessary to properly prep and normalize a JID. For those situations, this protocol defines a way for a client to ask a server to normalize a JID on its behalf.</p>
</section1>
<section1 topic='Discovering support' anchor='disco'>
  <p>If a server supports JID prep queries, it MUST specify the 'urn:xmpp:jidprep:0' feature in its service discovery information features as specified in &xep0030; and the Entity Capabilities profile specified in &xep0115;.</p>
  <example caption='Client checks for support by the server'><![CDATA[
<iq type="get"
    to="capulet.lit"
    from="juliet@capulet.lit/balcony"
    id="info1">
  <query xmlns="http://jabber.org/protocol/disco#info"/>
</iq>]]></example>
  <example caption='Server advertises support for JID prep queries'><![CDATA[
<iq type="result"
    to="juliet@capulet.lit/balcony"
    from="capulet.lit"
    id="info1">
  <query xmlns="http://jabber.org/protocol/disco#info">
    ...
    <feature var="urn:xmpp:jidprep:0"/>
    ...
  </query>
</iq>]]></example>
  <p>The JID prep service MAY be supported through the use of an external component (&xep0114;); in which case, the component MUST return an identity of "component/jidprep" in addition to the "urn:xmpp:jidprep:0" feature.</p>
  <example caption='Server component advertises support for JID prep queries'><![CDATA[
<iq type="result"
    to="juliet@capulet.lit/balcony"
    from="jidprep.capulet.lit"
    id="info2">
  <query xmlns="http://jabber.org/protocol/disco#info">
    <identity category="component" type="jidprep" />
    ...
    <feature var="urn:xmpp:jidprep:0" />
  </query>
</iq>]]></example>
</section1>
<section1 topic='Use Cases' anchor='usecases'>
  <p>In order to request prepping for a JID, the client sends an &IQ; stanza of type "get" to the server, containing a &lt;jid/&gt; element qualified by the 'urn:xmpp:jidprep:0' namespace and whose XML character data is the JID in question:</p>
  <example caption='Client requests the server to prep and normalize a JID'><![CDATA[
<iq type="get"
    to="capulet.lit"
    id="prep1">
  <jid xmlns="urn:xmpp:jidprep:0">ROMeo@montague.lit/orchard</jid>
</iq>
]]></example>
  <p>The server MUST return either an IQ-result or an IQ-error. When returning an IQ-result, the server sends an &IQ; staza of type='result' containing a &lt;jid/&gt; element qualifed by the 'urn:xmpp:jidprep:0' namespace and whose XML character data MUST be the prepped and normalized version of the requested JID:</p>
  <example caption='Server responds with the prepped JID'><![CDATA[
<iq type="result"
    to="juliet@capulet.lit/balcony"
    from="capulet.lit"
    id="prep1">
  <jid xmlns="urn:xmpp:jidprep:0">romeo@montague.lit/orchard</jid>
</iq>
]]></example>
  <p>If an IQ-error is returned, then it SHOULD specify an error condition of &lt;jid-malformed/&gt; if the given JID could not be processed to a normalized form:</p>
  <example caption='Server responds with an error for an invalid JID'><![CDATA[
<iq type="error"
    to="juliet@capulet.lit/balcony"
    from="capulet.lit"
    id="prep1">
  <jid xmlns="urn:xmpp:jidprep:0">romeo@@montague.lit/orchard</jid>
  <error type="modify">
    <jid-malformed xmlns="urn:ietf:params:xml:ns:xmpp-stanzas" />
  </error>
</iq>
]]></example>
</section1>
<section1 topic="Implementation Notes" anchor='impl'>
  <p>If a client has the ability to perform the prepping and normalization process itself, it SHOULD NOT make a JID prep request to the server.</p>
  <p>Upon a successful response, the client SHOULD cache the result, mapping the original JID to the normalized version.</p>
  <p>In order to reduce the number of queries made by clients, the server MUST enforce normalization rules for any JID slots understood by the server (e.g. the to and from attributes, roster item JIDs, etc).<note>This requirement is intended to be subsumed by the requirements introduced in &rfc6122bis;</note></p>
</section1>
<section1 topic='Security Considerations' anchor='security'>
  <p>As the process for normalizing a JID can be resource intensive, there is a possibility for denial of service attacks. A server MAY rate limit the number of requests to prevent such attacks. Likewise, the server MAY only respond to requests from users that are local to the server.</p>
</section1>
<section1 topic='IANA Considerations' anchor='iana'>
  <p>This document requires no interaction with &IANA;.</p>
</section1>
<section1 topic='XMPP Registrar Considerations' anchor='registrar'>
  <section2 topic='Protocol Namespaces' anchor='ns'>
    <p>The &REGISTRAR; includes 'urn:xmpp:jidprep:0' in its registry of protocol namespaces (see &NAMESPACES;).</p>
    <ul>
      <li>urn:xmpp:jidprep:0</li>
    </ul>
  </section2>
  <section2 topic='Protocol Versioning' anchor='registrar-versioning'>
    &NSVER;
  </section2>
  <section2 topic='Service Discovery Category/Type' anchor='registrar-disco'>
    <p>The &REGISTRAR; includes a category of "component" in its registry of Service Discovery identities (see &DISCOCATEGORIES;); as a result of this document, the Registrar includes a type of "jidprep" to that category.</p>
    <p>The registry submission is as follows:</p>
    <code><![CDATA[
    <category>
      <name>component</name>
      <type>
        <name>jidprep</name>
        <desc>
          A server component that offers a JID prepping 
          and normalization service to constrained clients.
        </desc>
        <doc>XEP-0328</doc>
      </type>
    </category>
]]></code>
  </section2>
</section1>
<section1 topic='XML Schema' anchor='schema'>
  <code><![CDATA[
<?xml version='1.0' encoding='UTF-8'?>

<xs:schema
    xmlns:xs='http://www.w3.org/2001/XMLSchema'
    targetNamespace='urn:xmpp:jidprep:0'
    xmlns='urn:xmpp:jidprep:0'
    elementFormDefault='qualified'>

  <xs:annotation>
    <xs:documentation>
      The protocol documented by this schema is defined in
      XEP-xxxx: http://www.xmpp.org/extensions/xep-xxxx.html
    </xs:documentation>
  </xs:annotation>

  <xs:element name='jid'>
    <xs:complexType>
      <xs:simpleContent />
    </xs:complexType>
  </xs:element>

</xs:schema>
]]></code>
</section1>
</xep>
