No Description
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

xep-0032.xml 11KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153
  1. <?xml version='1.0' encoding='UTF-8'?>
  2. <!DOCTYPE xep SYSTEM 'xep.dtd' [
  3. <!ENTITY % ents SYSTEM "xep.ent">
  4. %ents;
  5. ]>
  6. <?xml-stylesheet type='text/xsl' href='xep.xsl'?>
  7. <xep>
  8. <header>
  9. <title>Jabber URI Scheme</title>
  10. <abstract>A URI scheme for Jabber communications.</abstract>
  11. &LEGALNOTICE;
  12. <number>0032</number>
  13. <status>Retracted</status>
  14. <type>Standards Track</type>
  15. <sig>Standards</sig>
  16. <dependencies/>
  17. <supersedes/>
  18. <supersededby><spec>RFC 5122</spec></supersededby>
  19. <shortname>N/A</shortname>
  20. &stpeter;
  21. &pgmillard;
  22. <revision>
  23. <version>0.4</version>
  24. <date>2003-09-02</date>
  25. <initials>psa</initials>
  26. <remark>Retracted the document, since it is superseded by draft-ietf-xmpp-uri, an Internet-Draft produced by the IETF's XMPP WG.</remark>
  27. </revision>
  28. <revision>
  29. <version>0.3</version>
  30. <date>2002-10-16</date>
  31. <initials>psa</initials>
  32. <remark>Changed 'jabber:' scheme to 'xmpp:' scheme; further specified use cases; removed references to official Jabber namespaces.</remark>
  33. </revision>
  34. <revision>
  35. <version>0.2</version>
  36. <date>2002-05-10</date>
  37. <initials>psa</initials>
  38. <remark>Added information about syntax, allowable characters, and potential conflict with official Jabber namespaces.</remark>
  39. </revision>
  40. <revision>
  41. <version>0.1</version>
  42. <date>2002-05-08</date>
  43. <initials>psa</initials>
  44. <remark>Initial version.</remark>
  45. </revision>
  46. </header>
  47. <section1 topic='Introduction'>
  48. <p><em>Note: This document has been superseded by &rfc5122;.</em></p>
  49. <p>It is widely acknowledged that it would be good to be able to express a Jabber Identifier (JID) (see &xep0029;) as a Uniform Resource Identifier (see &rfc3986;). In addition, there would be value in being able to interact with a JID through a URI scheme (e.g., by sending a message or a presence update).</p>
  50. <p>Although XMPP enables a wide range of functionality, the authors propose that a Jabber URI scheme needs to support only a limited subset of the possible Jabber functionality. In particular, we see the following as core functions that need to be supported:</p>
  51. <ul>
  52. <li>Sending of basic messages</li>
  53. <li>Sending of basic presence</li>
  54. <li>Sending of subscription requests</li>
  55. </ul>
  56. </section1>
  57. <section1 topic='Syntax'>
  58. <p>The syntactic components of a Jabber URI are as follows:</p>
  59. <code>&lt;xmpp&gt;:[&lt;node-identifier&gt;@]&lt;domain-identifier&gt;[?&lt;query&gt;]</code>
  60. <p>This scheme is similar to the mailto URI scheme <note>The mailto URI scheme is described in RFC 2368: <link url='http://www.ietf.org/rfc/rfc2368.txt'>http://www.ietf.org/rfc/rfc2368.txt</link>.</note>. One similarity is that a Jabber URI is, in the terminology of RFC 3986, not hierarchical but opaque. A URI that is hierarchical in nature uses the slash ("/") character in order to separate hierarchical components, as is familiar from HTTP and FTP URIs. By contrast, an opaque URI such as a mailto URI contains only the scheme (e.g., 'mailto'), a colon, an address (e.g., 'user@host'), and an optional query component.</p>
  61. <p>Per the JID definition in XEP-0029, the node identifier is optional (i.e., a mere domain identifier is a valid JID). However, the proposed Jabber URI scheme forbids the inclusion of a resource identifier in the JID, even though XEP-0029 defines this as valid. This is partly because the authors see no compelling reason to include a resource identifier in the Jabber URI scheme, and also because including a resource would necessitate the inclusion of a slash character in an opaque URI, which is contrary to RFC 3986. Finally, the query component is optional.</p>
  62. </section1>
  63. <section1 topic='URI Characters and Escape Sequences'>
  64. <p>RFC 3986 limits the characters included in a URI to US-ASCII characters, and further defines a number of US-ASCII characters as reserved or otherwise excluded. Reserved characters are special characters used as delimiters withing URIs and whose usage is limited to their reserved purpose as defined in RFC 3986 or a specific URI scheme. Excluded characters are control characters, spaces, and other common (non-URI-specific) delimiters such as angle brackets, double quotes, the number sign, and the percent sign. Reserved characters must be escaped if their usage in a specific context would conflict with their reserved purpose, and excluded characters must always be escaped. The set of disallowed charaacters for any specific URI component consists of the reserved and excluded characters for that component. These are defined below for each component of a Jabber URI.</p>
  65. <section2 topic='Scheme Component'>
  66. <p>The scheme component for a Jabber URI is 'xmpp'. This component is delimited from the remainder of the URI by a colon character (':').</p>
  67. </section2>
  68. <section2 topic='Node Identifier Component'>
  69. <p>The node identifier component of a Jabber URI is equivalent to the "userinfo" component of a generic URI. Section 2.3 of XEP-0029 stipulates that a node identifier may contain any Unicode character higher than #x20 with the exception of the following:</p>
  70. <code>#x22 (") | #x26 (&amp;) | #x27 (') | #x2F (/) |
  71. #x3A (:) | #x3C (&lt;) | #x3E (&gt;) | #x40 (@) |
  72. #x7F (del) | #xFFFE (BOM) | #xFFFF (BOM)</code>
  73. <p>In addition, Section 2.2 of RFC 3986 stipulates that the following additional characters are reserved:</p>
  74. <code>#x24 ($) | #x2B (+) | #x2C (,) | #x3B (;) | #x3D (=) | #x3F (?)</code>
  75. <p>Section 2.4.3 of RFC 3986 further stipulates that the following characters are excluded from URIs in their unescaped form:</p>
  76. <code>#x23 (#) | #x25 (%)</code>
  77. <p>Finally, because the generic URI syntax does not provide a way to specify a character encoding other than US-ASCII (see Section 2.1 of RFC 3986), the characters in the node identifier component of a Jabber URI must contain only US-ASCII characters.</p>
  78. <p>Therefore, in order to ensure that a Jabber URI containing a node identifier is a valid URI, the characters disallowed by RFC 3986 (reserved, excluded, and non-ASCII characters) must be escaped in the node identifier component of a Jabber URI.</p>
  79. </section2>
  80. <section2 topic='Domain Identifier Component'>
  81. <p>A domain identifier is a standard DNS hostname as specified in RFC 952 <note><link url='http://www.ietf.org/rfc/rfc952.txt'>http://www.ietf.org/rfc/rfc952.txt</link></note>.</p>
  82. </section2>
  83. <section2 topic='Query Component'>
  84. <p>The query component of a Jabber URI may contain any US-ASCII character higher than #x20 with the exception of the following:</p>
  85. <code>#x22 (") | #x23 (#) | #x24 ($) | #x25 (%) |
  86. #x26 (&amp;) | #x27 (') | #x2B (+) | #x2C (,) |
  87. #x2F (/) | #x3A (:) | #x3B (;) | #x3C (&lt;) |
  88. #x3D (=) | #x3E (&gt;) | #x3F (?) | #x40 (@) |
  89. #x7F (del) | #xFFFE (BOM) | #xFFFF (BOM)</code>
  90. </section2>
  91. </section1>
  92. <section1 topic='Use Cases'>
  93. <p>Thus the most basic Jabber URI is user@host (sometimes referred to as a "bare JID") prepended by 'xmpp:', as shown in the following example.</p>
  94. <code>
  95. xmpp:user@host
  96. </code>
  97. <p>A URI containing bare JID and no query component should trigger an application to present a user with an appropriate interface to complete an action such as sending a message, sending presence, or managing a subscription. In order to make this possible, some basic queries must be included in the protocol.</p>
  98. <p>The authors propose three allowable query types in a Jabber URI: message, presence, and subscribe <note>These query types are URI queries as defined in RFC 3986 and are not to be confused with the &lt;query/&gt; element often included as the child of an &lt;iq/&gt; element in XMPP.</note>. These three basic URIs are described below by way of use cases.</p>
  99. <section2 topic='Sending a Message'>
  100. <p>If no parameters are passed along with the message query type, an application should present a user with an appropriate interface to complete the sending of a message.</p>
  101. <example caption='Invoking an Interface to Send a Message to a JID'>
  102. xmpp:user@host?message
  103. </example>
  104. <p>The query component may include parameters that further specify the message to be sent to the intended recipient. The following parameters are allowed:</p>
  105. <ul>
  106. <li>body</li>
  107. <li>subject</li>
  108. <li>thread (for conversation tracking)</li>
  109. </ul>
  110. <example caption='Sending a Message with a Subject, Body, and Thread'>
  111. xmpp:user@host?message&amp;subject=hi&amp;body=Hello%20World&amp;thread=abc123
  112. </example>
  113. </section2>
  114. <section2 topic='Sending Presence'>
  115. <p>If no parameters are passed along with the presence query type, an application should present a user with an appropriate interface to complete the act of sending presence.</p>
  116. <example caption='Invoking an Interface to Send Presence to a JID'>
  117. xmpp:user@host?presence
  118. </example>
  119. <p>The query component may include parameters that further specify the presence to be sent to the intended recipient (e.g., a user-defined status message). The following parameters are allowed:</p>
  120. <ul>
  121. <li>type ('unavailable'; if not specified, the sender is defined to be online and available)</li>
  122. <li>show (one of 'away', 'xa', 'dnd', or 'chat')</li>
  123. <li>status (user-defined status message)</li>
  124. <li>priority (a non-negative integer, with zero as the lowest priority)</li>
  125. </ul>
  126. <example caption='Sending a Specific Presence'>
  127. xmpp:user@host?presence&amp;show=dnd&amp;status=taking%20a%20nap
  128. </example>
  129. </section2>
  130. <section2 topic="Managing Subscriptions">
  131. <p>If no parameters are passed along with the subscribe query type, an application should present a user with an appropriate interface to complete the subscription request.</p>
  132. <example caption='Invoking an Interface to Send a Subscription Request to a JID'>
  133. xmpp:user@host?subscribe
  134. </example>
  135. <p>The query component may include parameters that further specify the subscription request to be sent to the intended recipient. Only the 'type' parameter is deemed useful in the limited Jabber URI spec, with valid values of 'subscribe', 'subscribed', 'unsubscribe', or 'unsubscribed'.</p>
  136. <example caption='Sending a Subscription Request'>
  137. xmpp:user@host?subscribe&amp;type=subscribe
  138. </example>
  139. <example caption='Accepting a Subscription Request'>
  140. xmpp:user@host?subscribe&amp;type=subscribed
  141. </example>
  142. <example caption="Unsubscribing from Another User's Presence">
  143. xmpp:user@host?subscribe&amp;type=unsubscribe
  144. </example>
  145. <example caption="Cancelling Another User's Subscription to Your Presence">
  146. xmpp:user@host?subscribe&amp;type=unsubscribed
  147. </example>
  148. </section2>
  149. </section1>
  150. <section1 topic='Author Note' anchor='authornote'>
  151. <p>Peter Millard, co-author of this specification from version 0.1 through version 0.4, died on April 26, 2006.</p>
  152. </section1>
  153. </xep>