Allow persistent input components emitting matches as intermediate events

extensions/inbox/rayo-asterisk.xml

@@ -0,0 +1,125 @@
+<?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>Rayo on Asterisk</title>
+  <abstract>This specification describes the best practices for implementing a Rayo server on top of Asterisk.</abstract>
+  <legal>
+    <copyright>This XMPP Extension Protocol is copyright (c) 2011 by the XMPP Standards Foundation (XSF).</copyright>
+    <permissions>Permission is hereby granted, free of charge, to any person obtaining a copy of this specification (the &quot;Specification&quot;), to make use of the Specification without restriction, including without limitation the rights to implement the Specification in a software program, deploy the Specification in a network service, and copy, modify, merge, publish, translate, distribute, sublicense, or sell copies of the Specification, and to permit persons to whom the Specification is furnished to do so, subject to the condition that the foregoing copyright notice and this permission notice shall be included in all copies or substantial portions of the Specification. Unless separate permission is granted, modified works that are redistributed shall not contain misleading information regarding the authors, title, number, or publisher of the Specification, and shall not claim endorsement of the modified works by the authors, any organization or project to which the authors belong, or the XMPP Standards Foundation.</permissions>
+    <warranty>## NOTE WELL: This Specification is provided on an &quot;AS IS&quot; BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. In no event shall the XMPP Standards Foundation or the authors of this Specification be liable for any claim, damages, or other liability, whether in an action of contract, tort, or otherwise, arising from, out of, or in connection with the Specification or the implementation, deployment, or other use of the Specification. ##</warranty>
+    <liability>In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall the XMPP Standards Foundation or any author of this Specification be liable for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising out of the use or inability to use the Specification (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if the XMPP Standards Foundation or such author has been advised of the possibility of such damages.</liability>
+    <conformance>This XMPP Extension Protocol has been contributed in full conformance with the XSF's Intellectual Property Rights Policy (a copy of which may be found at &lt;<link url='http://www.xmpp.org/extensions/ipr-policy.shtml'>http://www.xmpp.org/extensions/ipr-policy.shtml</link>&gt; or obtained by writing to XSF, P.O. Box 1641, Denver, CO 80201 USA).</conformance>
+  </legal>
+  <number>xxxx</number>
+  <status>ProtoXEP</status>
+  <type>Standards Track</type>
+  <sig>Standards</sig>
+  <approver>Council</approver>
+  <dependencies>
+    <spec>XMPP Core</spec>
+  </dependencies>
+  <supersedes/>
+  <supersededby/>
+  <shortname>NOT_YET_ASSIGNED</shortname>
+  <author>
+    <firstname>Ben</firstname>
+    <surname>Langfeld</surname>
+    <email>ben@langfeld.me</email>
+    <jid>ben@langfeld.me</jid>
+    <uri>http://langfeld.me</uri>
+  </author>
+  <revision>
+    <version>0.0.1</version>
+    <date>2011-12-05</date>
+    <initials>bl</initials>
+    <remark><p>First draft.</p></remark>
+  </revision>
+</header>
+<section1 topic='Introduction' anchor='intro'>
+
+</section1>
+<section1 topic='How it works' anchor='howitworks'>
+
+</section1>
+<section1 topic='Requirements' anchor='reqs'>
+
+</section1>
+<section1 topic='Terminology' anchor='terms'>
+  <section2 topic='Glossary' anchor='terms-glossary'>
+    <dl>
+      <di>
+        <dt>Gateway</dt>
+        <dd></dd>
+      </di>
+    </dl>
+  </section2>
+
+  <section2 topic='Conventions' anchor='terms-conventions'>
+    In examples, the following JIDs are used:
+    <ul>
+      <li><strong>juliet@capulet.lit/balcony, romeo@montague.lit/orchard</strong> - Potential controlling parties</li>
+      <li><strong>shakespeare.lit</strong> - The root domain of the Rayo service</li>
+      <li><strong>call.shakespeare.lit</strong> - The Rayo service's call domain</li>
+      <li><strong>mixer.shakespeare.lit</strong> - The Rayo service's mixer domain</li>
+    </ul>
+  </section2>
+</section1>
+<section1 topic='Concepts and Approach' anchor='concepts'>
+
+</section1>
+<section1 topic="Addressing Scheme" anchor='addressing'>
+
+</section1>
+<section1 topic='Session Flow' anchor='session'>
+
+</section1>
+<section1 topic='Formal Definition' anchor='def'>
+
+</section1>
+<section1 topic='Use Cases' anchor='usecases'>
+  <p>STRONGLY RECOMMENDED.</p>
+</section1>
+<section1 topic='Determining Support' anchor='support'>
+
+</section1>
+<section1 topic='Implementation Notes' anchor='impl'>
+
+</section1>
+<section1 topic='Security Considerations' anchor='security'>
+  <section2 topic='Denial of Service' anchor='security-dos'>
+    <p>Rayo sessions can be resource-intensive. Therefore, it is possible to launch a denial-of-service attack against an entity by burdening it with too many Rayo sessions. Care must be taken to accept sessions only from known entities and only if the entity's device is able to process such sessions.</p>
+  </section2>
+  <section2 topic='Communication Through Gateways' anchor='security-gateways'>
+    <p>Rayo communications can be enabled through gateways to non-XMPP networks, whose security characteristics can be quite different from those of XMPP networks. For example, on some SIP networks authentication is optional and "from" addresses can be easily forged. Care must be taken in communicating through such gateways.</p>
+  </section2>
+  <section2 topic='Information Exposure' anchor='security-info'>
+    <p>Mere negotiation of a Rayo session can expose sensitive information about the parties (e.g. IP addresses). Care must be taken in communicating such information, and end-to-end encryption should be used if the parties do not trust the intermediate servers or gateways.</p>
+  </section2>
+</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='registrar-ns'>
+    <p>This specification defines the following XML namespaces:</p>
+    <ul>
+      <li>urn:xmpp:rayo:gateway:1</li>
+      <li>urn:xmpp:rayo:node:1</li>
+    </ul>
+    <p>The &REGISTRAR; includes the foregoing namespaces in its registry at &NAMESPACES;, as governed by &xep0053;.</p>
+  </section2>
+  <section2 topic='Namespace Versioning' anchor='registrar-versioning'>
+    <p>If the protocol defined in this specification undergoes a major revision that is not fully backward-compatible with an older version, or that contains significant new features, the XMPP Registrar shall increment the protocol version number found at the end of the XML namespaces defined herein, as described in Section 4 of <cite>XEP-0053</cite>.</p>
+  </section2>
+</section1>
+<section1 topic='History' anchor='history'>
+</section1>
+<section1 topic='Acknowledgements' anchor='acknowledgements'>
+
+</section1>
+</xep>

extensions/inbox/rayo-clustering.xml

@@ -0,0 +1,132 @@
+<?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>Rayo Clustering</title>
+  <abstract>This specification describes an extension to the Rayo protocol to support clustering of Rayo servers and their presentation as a unified service.</abstract>
+  <legal>
+    <copyright>This XMPP Extension Protocol is copyright (c) 2011 by the XMPP Standards Foundation (XSF).</copyright>
+    <permissions>Permission is hereby granted, free of charge, to any person obtaining a copy of this specification (the &quot;Specification&quot;), to make use of the Specification without restriction, including without limitation the rights to implement the Specification in a software program, deploy the Specification in a network service, and copy, modify, merge, publish, translate, distribute, sublicense, or sell copies of the Specification, and to permit persons to whom the Specification is furnished to do so, subject to the condition that the foregoing copyright notice and this permission notice shall be included in all copies or substantial portions of the Specification. Unless separate permission is granted, modified works that are redistributed shall not contain misleading information regarding the authors, title, number, or publisher of the Specification, and shall not claim endorsement of the modified works by the authors, any organization or project to which the authors belong, or the XMPP Standards Foundation.</permissions>
+    <warranty>## NOTE WELL: This Specification is provided on an &quot;AS IS&quot; BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. In no event shall the XMPP Standards Foundation or the authors of this Specification be liable for any claim, damages, or other liability, whether in an action of contract, tort, or otherwise, arising from, out of, or in connection with the Specification or the implementation, deployment, or other use of the Specification. ##</warranty>
+    <liability>In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall the XMPP Standards Foundation or any author of this Specification be liable for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising out of the use or inability to use the Specification (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if the XMPP Standards Foundation or such author has been advised of the possibility of such damages.</liability>
+    <conformance>This XMPP Extension Protocol has been contributed in full conformance with the XSF's Intellectual Property Rights Policy (a copy of which may be found at &lt;<link url='http://www.xmpp.org/extensions/ipr-policy.shtml'>http://www.xmpp.org/extensions/ipr-policy.shtml</link>&gt; or obtained by writing to XSF, P.O. Box 1641, Denver, CO 80201 USA).</conformance>
+  </legal>
+  <number>xxxx</number>
+  <status>ProtoXEP</status>
+  <type>Standards Track</type>
+  <sig>Standards</sig>
+  <approver>Council</approver>
+  <dependencies>
+    <spec>XMPP Core</spec>
+  </dependencies>
+  <supersedes/>
+  <supersededby/>
+  <shortname>NOT_YET_ASSIGNED</shortname>
+  <author>
+    <firstname>Jose</firstname>
+    <surname>de Castro</surname>
+    <email>jdecastro@voxeo.com</email>
+    <jid>jdecastro@voxeo.com</jid>
+    <uri>http://voxeolabs.com</uri>
+  </author>
+  <author>
+    <firstname>Ben</firstname>
+    <surname>Langfeld</surname>
+    <email>ben@langfeld.me</email>
+    <jid>ben@langfeld.me</jid>
+    <uri>http://langfeld.me</uri>
+  </author>
+  <revision>
+    <version>0.0.1</version>
+    <date>2011-12-05</date>
+    <initials>jdc</initials>
+    <remark><p>First draft.</p></remark>
+  </revision>
+</header>
+<section1 topic='Introduction' anchor='intro'>
+
+</section1>
+<section1 topic='How it works' anchor='howitworks'>
+
+</section1>
+<section1 topic='Requirements' anchor='reqs'>
+
+</section1>
+<section1 topic='Terminology' anchor='terms'>
+  <section2 topic='Glossary' anchor='terms-glossary'>
+    <dl>
+      <di>
+        <dt>Gateway</dt>
+        <dd></dd>
+      </di>
+    </dl>
+  </section2>
+
+  <section2 topic='Conventions' anchor='terms-conventions'>
+    In examples, the following JIDs are used:
+    <ul>
+      <li><strong>juliet@capulet.lit/balcony, romeo@montague.lit/orchard</strong> - Potential controlling parties</li>
+      <li><strong>shakespeare.lit</strong> - The root domain of the Rayo service</li>
+      <li><strong>call.shakespeare.lit</strong> - The Rayo service's call domain</li>
+      <li><strong>mixer.shakespeare.lit</strong> - The Rayo service's mixer domain</li>
+    </ul>
+  </section2>
+</section1>
+<section1 topic='Concepts and Approach' anchor='concepts'>
+
+</section1>
+<section1 topic="Addressing Scheme" anchor='addressing'>
+
+</section1>
+<section1 topic='Session Flow' anchor='session'>
+
+</section1>
+<section1 topic='Formal Definition' anchor='def'>
+
+</section1>
+<section1 topic='Use Cases' anchor='usecases'>
+  <p>STRONGLY RECOMMENDED.</p>
+</section1>
+<section1 topic='Determining Support' anchor='support'>
+
+</section1>
+<section1 topic='Implementation Notes' anchor='impl'>
+
+</section1>
+<section1 topic='Security Considerations' anchor='security'>
+  <section2 topic='Denial of Service' anchor='security-dos'>
+    <p>Rayo sessions can be resource-intensive. Therefore, it is possible to launch a denial-of-service attack against an entity by burdening it with too many Rayo sessions. Care must be taken to accept sessions only from known entities and only if the entity's device is able to process such sessions.</p>
+  </section2>
+  <section2 topic='Communication Through Gateways' anchor='security-gateways'>
+    <p>Rayo communications can be enabled through gateways to non-XMPP networks, whose security characteristics can be quite different from those of XMPP networks. For example, on some SIP networks authentication is optional and "from" addresses can be easily forged. Care must be taken in communicating through such gateways.</p>
+  </section2>
+  <section2 topic='Information Exposure' anchor='security-info'>
+    <p>Mere negotiation of a Rayo session can expose sensitive information about the parties (e.g. IP addresses). Care must be taken in communicating such information, and end-to-end encryption should be used if the parties do not trust the intermediate servers or gateways.</p>
+  </section2>
+</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='registrar-ns'>
+    <p>This specification defines the following XML namespaces:</p>
+    <ul>
+      <li>urn:xmpp:rayo:gateway:1</li>
+      <li>urn:xmpp:rayo:node:1</li>
+    </ul>
+    <p>The &REGISTRAR; includes the foregoing namespaces in its registry at &NAMESPACES;, as governed by &xep0053;.</p>
+  </section2>
+  <section2 topic='Namespace Versioning' anchor='registrar-versioning'>
+    <p>If the protocol defined in this specification undergoes a major revision that is not fully backward-compatible with an older version, or that contains significant new features, the XMPP Registrar shall increment the protocol version number found at the end of the XML namespaces defined herein, as described in Section 4 of <cite>XEP-0053</cite>.</p>
+  </section2>
+</section1>
+<section1 topic='History' anchor='history'>
+</section1>
+<section1 topic='Acknowledgements' anchor='acknowledgements'>
+
+</section1>
+</xep>