Updated protocol support information for the 2.3.0 release.

git-svn-id: http://svn.igniterealtime.org/svn/repos/messenger/trunk@2804 b35dd754-fafc-0310-a699-88a17e54d16e

Updated protocol support information for the 2.3.0 release.
git-svn-id: http://svn.igniterealtime.org/svn/repos/messenger/trunk@2804 b35dd754-fafc-0310-a699-88a17e54d16e
f724cb75 · Matt Tucker · matt · cea33d0e · f724cb75
Commit f724cb75 authored Sep 10, 2005 by Matt Tucker Committed by matt Sep 10, 2005
Hide whitespace changes
Inline Side-by-side

Showing with 37 additions and 30 deletions

protocol-support.html documentation/docs/protocol-support.html +37 -30

No files found.
--- a/documentation/docs/protocol-support.html
+++ b/documentation/docs/protocol-support.html
@@ -4,6 +4,11 @@
 <head>
    <title>Jive Messenger Protocol Support</title>
    <link href="style.css" rel="stylesheet" type="text/css">
+    <style type="text/css">
+    .supported { background-color:#D0FFCB }
+    .partially_supported { background-color:#FEFF94 } 
+    .unsupported { background-color:#FFB4B4 }
+    </style>
 </head>
 <body>
@@ -16,7 +21,7 @@
 <acronym title="Extensible Messaging and Presence Protocol">XMPP</acronym>
 specifications defined by <a href="http://www.xmpp.org/specs/rfc3920.html">RFC 3920</a> and
 <a href="http://www.xmpp.org/specs/rfc3921.html">RFC 3921</a>. In addition to full
-XMPP support, we are also working to provide support for numerous extensions to XMPP
+XMPP support, Jive Messenger also provides support for numerous extensions to XMPP
 that are defined through the
 <acronym title="Jabber Enhancement Proposals">JEP</acronym> process at
 <a href="http://www.jabber.org">Jabber.org</a>.  This document provides a
@@ -38,32 +43,33 @@ release.</p>
 <a name="basic"></a>
 <h2>Basic IM Protocol Suite Support</h2>
-<p>The table below details the level of support for the requirements set by
+<p>The basic suite includes full support of the XMPP RFC's as well as the most common extensions.
+The table below details the level of support for the requirements set by
 <a href="http://www.jabber.org/jeps/jep-0073.html">JEP-0073: Basic IM Protocol
 Suite</a>.</p>
 <table class="dbtable">
 <tr>
  <th>Specification</th>
-  <th>Supported</th>
+  <th width="35%">Supported</th>
 </tr><tr>
  <td><a href="http://www.xmpp.org/specs/rfc3920.html">RFC 3920</a>: XMPP Core</td>
-  <td>Yes/No (<a href="#rfc3920">see below</a>)</td>
+  <td class="partially_supported">Yes/No (<a href="#rfc3920">see below</a>)</td>
 </tr><tr>
  <td><a href="http://www.xmpp.org/specs/rfc3921.html">RFC 3921</a>: XMPP IM</td>
-  <td>Yes/No (<a href="#rfc3921">see below</a>)</td>
+  <td class="partially_supported">Yes/No (<a href="#rfc3921">see below</a>)</td>
 </tr><tr>
  <td><a href="http://www.jabber.org/jeps/jep-0030.html">JEP-0030</a>: Service Discovery</td>
-  <td>Yes</td>
+  <td class="supported">Yes</td>
 </tr><tr>
  <td><a href="http://www.jabber.org/jeps/jep-0077.html">JEP-0077</a>: In-Band Registration</td>
-  <td>Yes</td>
+  <td class="supported">Yes</td>
 </tr><tr>
  <td><a href="http://www.jabber.org/jeps/jep-0078.html">JEP-0078</a>: Non-SASL Authentication</td>
-  <td>Yes</td>
+  <td class="supported">Yes</td>
 </tr><tr>
  <td><a href="http://www.jabber.org/jeps/jep-0086.html">JEP-0086</a>: Error Condition Mappings</td>
-  <td>Yes</td>
+  <td class="supported">Yes</td>
 </tr>
 </table>
 <br>
@@ -71,41 +77,42 @@ Suite</a>.</p>
 <a name="intermediate"></a>
 <h2>Intermediate IM Protocol Suite Support</h2>
-<p>The table below details the level of support for the requirements set by
+<p>The intermediate suite includes the full basic suite as well as more advanced features in common use
+by XMPP clients. The table below details the level of support for the requirements set by
 <a href="http://www.jabber.org/jeps/jep-0117.html">JEP-0117: Intermediate IM Protocol
 Suite</a> [<a href="#fn1">1</a>].</p>
 <table class="dbtable">
 <tr>
  <th>Specification</th>
-  <th>Supported</th>
+  <th width="35%">Supported</th>
 </tr><tr>
  <td><a href="http://www.jabber.org/jeps/jep-0073.html">JEP-0073</a>: Basic IM Protocol Suite</td>
-  <td>No</td>
+  <td class="partially_supported">No</td>
 </tr><tr>
  <td><a href="http://www.jabber.org/jeps/jep-0004.html">JEP-0004</a>: Data Forms</td>
-  <td>Yes</td>
+  <td class="supported">Yes</td>
 </tr><tr>
  <td><a href="http://www.jabber.org/jeps/jep-0020.html">JEP-0020</a>: Feature Negotiation</td>
-  <td>No</td>
+  <td class="unsupported">No</td>
 </tr><tr>
  <td><a href="http://www.jabber.org/jeps/jep-0045.html">JEP-0045</a>: Multi-User Chat</td>
-  <td>Yes</td>
+  <td class="supported">Yes</td>
 </tr><tr>
  <td><a href="http://www.jabber.org/jeps/jep-0047.html">JEP-0047</a>: In-Band Bytestreams</td>
-  <td>Yes</td>
+  <td class="supported">Yes</td>
 </tr><tr>
  <td><a href="http://www.jabber.org/jeps/jep-0065.html">JEP-0065</a>: SOCKS5 Bytestreams</td>
-  <td>No</td>
+  <td class="unsupported">No</td>
 </tr><tr>
  <td><a href="http://www.jabber.org/jeps/jep-0071.html">JEP-0071</a>: XHTML-IM</td>
-  <td>Yes [<a href="#fn3">3</a>]</td>
+  <td class="supported">Yes [<a href="#fn2">2</a>]</td>
 </tr><tr>
  <td><a href="http://www.jabber.org/jeps/jep-0096.html">JEP-0096</a>: File Transfer</td>
-  <td>No</td>
+  <td class="unsupported">No</td>
 </tr><tr>
  <td><a href="http://www.jabber.org/jeps/jep-0115.html">JEP-0115</a>: Entity Capabilities</td>
-  <td>No</td>
+  <td class="partially_supported">Yes [<a href="#fn3">3</a>]</td>
 </tr>
 </table>
 <br>
@@ -143,7 +150,7 @@ JEPs that only require client-side support are omitted.</p>
  <td><a href="http://www.jabber.org/jeps/jep-0054.html">JEP-0054</a>: vcard-temp</td>
  <td>-</td>
 </tr><tr>
-  <td><a href="http://www.jabber.org/jeps/jep-0055.html">JEP-0055</a>: Jabber Search [<a href="#fn2">2</a>]</td>
+  <td><a href="http://www.jabber.org/jeps/jep-0055.html">JEP-0055</a>: Jabber Search [<a href="#fn1">1</a>]</td>
  <td>-</td>
 </tr><tr>
  <td><a href="http://www.jabber.org/jeps/jep-0077.html">JEP-0077</a>: In-Band Registration</td>
@@ -181,13 +188,12 @@ JEPs that only require client-side support are omitted.</p>
 <ul>
    <li><b>TLS</b> (<a href="http://www.xmpp.org/specs/rfc3920.html#tls">RFC3920.5</a>)  -- Jive
-    Messenger provides support for a dedicated TLS/SSL port (5223) as used by the older "Jabber"
+    Messenger provides support for client-to-server (c2s) TLS streams as defined in the RFC, but does not currently 
-    protocol but does not currently support TLS stream-negotiation as described in XMPP.</li>
+    provide support for TLS between servers (s2s).</li>
-    <li><b>Resource Binding</b> (<a href="http://www.xmpp.org/specs/rfc3920.html#bind">RFC3920.7</a>) </li>
    <li><b>SASL</b> (<a href="http://www.xmpp.org/specs/rfc3920.html#sasl">RFC33920.6</a>)  --
-    Jive Messenger currently relies on non-SASL authentication (JEP-0078) for authentication.</li>
+    Jive Messenger provides support for client-to-server (c2s) SASL authentication, but does not currently
+    provide support for SASL between servers (s2s).</li>
 </ul>
 <br>
@@ -204,11 +210,12 @@ JEPs that only require client-side support are omitted.</p>
 <a name="footnotes"></a>
 <h2>Footnotes</h2>
-  [<a name="fn1">1</a>] <u>JEP-0117: Intermediate IM Protocol Suite</u> is currently an experimental proposal, but it provides a good roadmap for future development.
+  [<a name="fn1">1</a>] Support for <u>JEP-0055: Jabber Search</u> is provided by the <a href="http://www.jivesoftware.org/messenger/plugins.jsp">Search plugin</a>.
-<br>  
+ <br>
-  [<a name="fn2">2</a>] Support for <u>JEP-0055: Jabber Search</u> is provided by the <a href="http://www.jivesoftware.org/messenger/plugins.jsp">Search plugin</a>.
+ [<a name="fn2">2</a>] Some requirements of <u>JEP-0117: Intermediate IM Protocol Suite</u> do not pertain to servers.
 <br>
- [<a name="fn3">3</a>] Some requirements of <u>JEP-0117: Intermediate IM Protocol Suite</u> do not pertain to servers.
+ [<a name="fn3">3</a>] The entity capabilities JEP is primarily for clients to implement. However, Jive Messenger does not support an optional server extensions defined by the JEP.
+<br>
 </body>
 </html>