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-0183.xml 14KB

  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>Jingle Telepathy Transport</title>
  10. <abstract>This document defines a telepathic transport method for establishing Extra-Sensory Perception (ESP) streams.</abstract>
  12. <number>0183</number>
  13. <status>Active</status>
  14. <type>Humorous</type>
  15. <sig>Standards</sig>
  16. <approver>Council</approver>
  17. <dependencies>
  18. <spec>XMPP Core</spec>
  19. <spec>XEP-0166</spec>
  20. </dependencies>
  21. <supersedes/>
  22. <supersededby/>
  23. <shortname>telepathy</shortname>
  24. &stpeter;
  25. <revision>
  26. <version>1.0</version>
  27. <date>2006-04-01</date>
  28. <initials>psa</initials>
  29. <remark><p>April Fools!</p></remark>
  30. </revision>
  31. </header>
  32. <section1 topic='Introduction' anchor='intro'>
  33. <p>&xep0166; defines a framework for negotiating and managing out-of-band multimedia sessions over XMPP. In order to provide a flexible framework, the base Jingle specification defines neither data transport methods nor media (session) types, leaving that up to separate specifications.</p>
  34. <p>Typical peer-to-peer session types include voice chat (see &xep0167;) and video chat (see &xep0180;). But Jingle can go farther. Indeed, why not support not only physical multimedia sessions (limited to the five physical senses) but also psychical multimedia sessions (which go beyond the basic physical senses to include advanced, extra-sensory perception)? The media (or medium) may be different, but the underlying principles are the same: fostering freedom of conversation by connecting people (e.g., through mind-reading and s&#233;ances) and even applications such as accessing information from the future (e.g., in clairvoyance and precognition). Indeed, the ability to communicate with the spirit world will push Jabber/XMPP technologies into a new age of real-time communications (light years ahead of traditional IM and VoIP systems). Beyond Internet telephony, our innovations in Internet telepathy will give new meaning to the term "voice chat" as users are able to hear voices from the past, present, or future.</p>
  35. <p>Unfortunately, these advanced session types cannot be supported using existing transport mechanisms such as &xep0176;, &xep0177;, and &xep0179;. Therefore, this document defines a new Jingle transport method for establishing and managing Extra-Sensory Perception (ESP) streams: the "telepathy" method.</p>
  36. </section1>
  37. <section1 topic='Requirements' anchor='reqs'>
  38. <p>The Jingle telepathy transport method is designed to meet the following requirements:</p>
  39. <ol>
  40. <li>Make it possible to establish and manage extra-sensory perception (ESP) streams between two XMPP entities.</li>
  41. <li>Make it relatively easy to implement support in standard Jabber/XMPP clients.</li>
  42. <li>Where communication with non-XMPP (indeed, non-material) entities is needed, push as much complexity as possible onto gateways between this world and the spirit world.</li>
  43. </ol>
  44. <p>Note: Whether or not an ESP stream can be established depends on the user's native telepathic abilities as well as acquired telepathic skills such as grounding, centering, pinging, pulse-sending, broadcasting, scanning, probing, suggestion, and projection. <note>For a good introduction to telepathic skills, see <cite>The Telepathy Manual</cite> located at &lt;<link url=''></link>&gt;.</note> Your mileage may vary.</p>
  45. </section1>
  46. <section1 topic='Protocol Description' anchor='protocol'>
  47. <section2 topic='Transport Initiation' anchor='protocol-initiate'>
  48. <p>In order for the initiating entity in a Jingle exchange to start the negotiation, it MUST send a Jingle "session-initiate" stanza as described in <cite>XEP-0166</cite>. This stanza MUST include at least one transport method. If the initiating entity wishes to negotiate the telepathy transport, it MUST include a &TRANSPORT; child element qualified by the '' namespace.</p>
  49. <p>This &TRANSPORT; element MUST include one and only one &CANDIDATE; element per channel specifying the parameters that the initiator believes will be most likely to succeed for that channel. (Note: You have to believe.) This is not necessarily the initiator's preferred address for spiritual communication, but instead is the "address most likely to succeed", i.e., the address that is assumed to be reachable by the vast majority of target entities. (Establishing direct spiritual communication is hard enough as it is.) Here is an example:</p>
  50. <example caption="Initiation Example"><![CDATA[
  51. <iq from='' to='' id='jingle1' type='set'>
  52. <jingle xmlns=''
  53. action='session-initiate'
  54. initiator=''
  55. sid='a73sjjvkla37jfea'>
  56. <description xmlns='urn:xmpp:example'/>
  57. <transport xmlns=''>
  58. <candidate name='ihearvoices' generation='0' plane='9' pulse='80'
  59. psi-sig='yellow happy bright open no-shields'
  60. sign='Pisces' time='present'/>
  61. </transport>
  62. </jingle>
  63. </iq>
  64. ]]></example>
  65. <p>The attributes of the &lt;candidate/&gt; element are as follows:</p>
  66. <ul>
  67. <li>The 'generation' attribute is an index, starting at 0, that enables the parties to keep track of updates to the candidate throughout the life of the session.</li>
  68. <li>The 'name' attribute specifies a unique name for the channel.</li>
  69. <li>The 'plane' attribute is used for diagnostics; it is an index, starting at 1, referencing which astral plane this candidate is on for a given peer.</li>
  70. <li>The 'pulse' attribute specifies the initiator's heart rate at the moment; this helps establish communications through pulse-sending of informational messages in time with the beat of your heart.</li>
  71. <li>The 'psi-sig' attribute is the initiator's Psi Signature or "energy fingerprint"; because scanning people for their psi-sig can take time and is often a challenge, advertising one's psi-sig ahead of time makes it easier to establish a spiritual connection. The format of the 'psi-sig' attribute is a space-delimited set of descriptive words, often including colors, feelings, and emotions characterizing the person's energy state at the moment. Note: A person's psi-sig can change from moment to moment; therefore, it is advisable to also advertise it using &xep0163;.</li>
  72. <li>The 'sign' attribute represents the initiator's Zodiac sign; including this value obviates the need for asking "what's your sign?"</li>
  73. <li>The 'time' attribute is used for diagnostics; the allowable values are "past", "present", and "future".</li>
  74. </ul>
  75. </section2>
  76. <section2 topic='Receiver Response' anchor='protocol-response'>
  77. <p>As described in <cite>XEP-0166</cite>, to provisionally accept the session initiation request, the receiver returns an IQ-result:</p>
  78. <example caption="Receiver Provisionally Accepts the Session Request"><![CDATA[
  79. <iq type='result' from='' to='' id='jingle1'/>
  80. ]]></example>
  81. <p>To definitively accept the telepathy transport method, the receiver MUST send a &JINGLE; element with an action of 'transport-accept', specifying the transport method desired.</p>
  82. <example caption="Receiver Accepts the Telepathy Transport Method"><![CDATA[
  83. <iq type='set' from='' to='' id='jingle2'>
  84. <jingle xmlns=''
  85. action='transport-accept'
  86. initiator=''
  87. sid='a73sjjvkla37jfea'>
  88. <transport xmlns=''>
  89. <candidate name='ihearvoices'/>
  90. </transport>
  91. </jingle>
  92. </iq>
  93. ]]></example>
  94. <p>The initiating entity then acknowledges the receiver's acceptance:</p>
  95. <example caption="Initiating Entity Acknowledges Definitive Acceptance"><![CDATA[
  96. <iq from='' to='' id='jingle2' type='result'/>
  97. ]]></example>
  98. <p>Now the initiating entity and receiver can begin sending appropriate psychical media over the negotiated ESP stream.</p>
  99. <p>In the event that the receiver cannot establish a channel, it SHOULD terminate the session (see <cite>XEP-0176</cite> or <cite>XEP-0177</cite> for examples).</p>
  100. </section2>
  101. <section2 topic='Informational Messages' anchor='protocol-info'>
  102. <p>Because the informational message payloads specific to the telepathy transport method cannot be tied down to the arbitrary conventions of XML syntax, a &lt;message/&gt; element qualified by the '' namespace may include any character data that either party feels like communicating.</p>
  103. </section2>
  104. </section1>
  105. <section1 topic='Deployment Notes' anchor='deploy'>
  106. <p>This specification applies exclusively to Jabber/XMPP clients and places no additional requirements on Jabber/XMPP servers. However, service administrators may wish to deploy a gateway to the spirit world in order to ease the channel negotiation process. How to develop such gateways is an inexact science (but it <em>is</em> a science!) and therefore is outside the scope of this document.</p>
  107. </section1>
  108. <section1 topic='Security Considerations' anchor='security'>
  109. <p>To the author's knowledge, no channel encryption technologies exist for direct spiritual connections. Although this vulnerability can be mitigated through speaking in tongues and the use of various alternative languages such as Runic and Mumbo-Jumbo, the result is only security through obscurity, not channel encryption as those familiar with the merely material world understand it. If only benighted materialist scientists and technologists would recognize the validity of psychical experience and extra-sensory perception, progress in applying encryption principles to psychical channeling and the exchange of pure spiritual energy would rapidly ensue.</p>
  110. </section1>
  111. <section1 topic='IANA Considerations' anchor='iana'>
  112. <p>This document requires no interaction with &IANA;.</p>
  113. </section1>
  114. <section1 topic='XMPP Registrar Considerations' anchor='registrar'>
  115. <section2 topic='Protocol Namespaces' anchor='registrar-ns'>
  116. <p>The &REGISTRAR; shall include '' and '' in its registry of protocol namespaces.</p>
  117. </section2>
  118. <section2 topic='Jingle Transport Methods' anchor='registrar-transports'>
  119. <p>The XMPP Registrar shall include "" in its registry of Jingle transport methods. The registry submission is as follows:</p>
  120. <code><![CDATA[
  121. <transport>
  122. <name>telepathy</name>
  123. <desc>
  124. A method for the negotiation of Extra-Sensory Perception (ESP) streams.
  125. </desc>
  126. <doc>XEP-0183</doc>
  127. </transport>
  128. ]]></code>
  129. </section2>
  130. </section1>
  131. <section1 topic='XML Schemas' anchor='schema'>
  132. <section2 topic='Transport Method' anchor='schema-transport'>
  133. <code><![CDATA[
  134. <?xml version='1.0' encoding='UTF-8'?>
  135. <xs:schema
  136. xmlns:xs=''
  137. targetNamespace=''
  138. xmlns=''
  139. elementFormDefault='qualified'>
  140. <xs:element name='transport'>
  141. <xs:complexType>
  142. <xs:choice>
  143. <xs:sequence>
  144. <xs:element ref='candidate' minOccurs='0' maxOccurs='1'/>
  145. </xs:sequence>
  146. </xs:choice>
  147. </xs:complexType>
  148. </xs:element>
  149. <xs:element name='candidate'>
  150. <xs:complexType>
  151. <xs:simpleContent>
  152. <xs:extension base='empty'>
  153. <xs:attribute name='generation' type='xs:unsignedByte' use='required'/>
  154. <xs:attribute name='name' type='xs:string' use='required'/>
  155. <xs:attribute name='plane' type='xs:positiveInteger' use='optional'/>
  156. <xs:attribute name='pulse' type='xs:positiveInteger' use='optional'/>
  157. <xs:attribute name='psi-sig' type='xs:string' use='optional'/>
  158. <xs:attribute name='sign' use='optional'>
  159. <xs:simpleType>
  160. <xs:restriction base='xs:NCName'>
  161. <xs:enumeration value='Aquarius'/>
  162. <xs:enumeration value='Aries'/>
  163. <xs:enumeration value='Cancer'/>
  164. <xs:enumeration value='Capricorn'/>
  165. <xs:enumeration value='Gemini'/>
  166. <xs:enumeration value='Leo'/>
  167. <xs:enumeration value='Libra'/>
  168. <xs:enumeration value='Pisces'/>
  169. <xs:enumeration value='Sagittarius'/>
  170. <xs:enumeration value='Scorpio'/>
  171. <xs:enumeration value='Taurus'/>
  172. <xs:enumeration value='Virgo'/>
  173. </xs:restriction>
  174. </xs:simpleType>
  175. </xs:attribute>
  176. <xs:attribute name='time' use='optional'>
  177. <xs:simpleType>
  178. <xs:restriction base='xs:NCName'>
  179. <xs:enumeration value='future'/>
  180. <xs:enumeration value='past'/>
  181. <xs:enumeration value='present'/>
  182. </xs:restriction>
  183. </xs:simpleType>
  184. </xs:attribute>
  185. </xs:extension>
  186. </xs:simpleContent>
  187. </xs:complexType>
  188. </xs:element>
  189. <xs:simpleType name='empty'>
  190. <xs:restriction base='xs:string'>
  191. <xs:enumeration value=''/>
  192. </xs:restriction>
  193. </xs:simpleType>
  194. </xs:schema>
  195. ]]></code>
  196. </section2>
  197. <section2 topic='Informational Messages' anchor='schema-info'>
  198. <code><![CDATA[
  199. <?xml version='1.0' encoding='UTF-8'?>
  200. <xs:schema
  201. xmlns:xs=''
  202. targetNamespace=''
  203. xmlns=''
  204. elementFormDefault='qualified'>
  205. <xs:element name='message' type='xs:string'/>
  206. </xs:schema>
  207. ]]></code>
  208. </section2>
  209. </section1>
  210. </xep>