Difference between revisions of "Verify"

From XMPP WIKI
Jump to navigation Jump to search
 
Line 1: Line 1:
= XMPP Verification Suite =
= XMPP Verification Suite =
== Goal ==
To create a tool that will allow anyone to verify that their XMPP implementation is compliant with all relevant protocol specifications.
== Architecture ==
The tool will be written as a self-contained software package that can be run locally or as an online service at xmpp.org. Ideally it will have a modular architecture that will make it straightforward to add new test cases over time.
== Language ==
The tool will be created in a developer-friendly programming language that has good library support for XMPP, such as Python or Lua.
The language for test cases is yet to be determined.
== Phases ==
The first phase will focus on the basics of server-to-server communication as defined in RFC 6120 (streams, TLS) and XEP-0220 / RFC 3920 (server dialback).
The second phase will add the basics of client-to-server communication (SASL authentication, resource binding) as defined in RFC 6120.
The third phase will add the basics of instant messaging and presence (rosters, presence subscriptions) as defined in RFC 6121.
Later phases will add service discovery, entity capabilities, and other XMPP extensions.
== Timeline ==
The team will aim to finish at least the first phase in time for the XMPP Summit to be held in Brussels in February 2012. It would be great to finish (or make significant progress on) the second phase by then, as well, so that the hackfest could focus on coordinated interop testing and tool development.
== Team ==
The following people have volunteered to help with the project:
* Mike "bear" Taylor
* Peter Saint-Andre
* Florian Jensen


== Background ==
== Background ==
Line 10: Line 46:
* xmpp:interop@muc.xmpp.org?join
* xmpp:interop@muc.xmpp.org?join
* http://mail.jabber.org/mailman/listinfo/interop
* http://mail.jabber.org/mailman/listinfo/interop
== Focus ==
To create a suite of tests that will allow any to test and/or verify their server implementation as being compliant with all relevant XMPP RFCs and eventually XEPs.

Latest revision as of 22:21, 27 September 2011

XMPP Verification Suite

Goal

To create a tool that will allow anyone to verify that their XMPP implementation is compliant with all relevant protocol specifications.

Architecture

The tool will be written as a self-contained software package that can be run locally or as an online service at xmpp.org. Ideally it will have a modular architecture that will make it straightforward to add new test cases over time.

Language

The tool will be created in a developer-friendly programming language that has good library support for XMPP, such as Python or Lua.

The language for test cases is yet to be determined.

Phases

The first phase will focus on the basics of server-to-server communication as defined in RFC 6120 (streams, TLS) and XEP-0220 / RFC 3920 (server dialback).

The second phase will add the basics of client-to-server communication (SASL authentication, resource binding) as defined in RFC 6120.

The third phase will add the basics of instant messaging and presence (rosters, presence subscriptions) as defined in RFC 6121.

Later phases will add service discovery, entity capabilities, and other XMPP extensions.

Timeline

The team will aim to finish at least the first phase in time for the XMPP Summit to be held in Brussels in February 2012. It would be great to finish (or make significant progress on) the second phase by then, as well, so that the hackfest could focus on coordinated interop testing and tool development.

Team

The following people have volunteered to help with the project:

  • Mike "bear" Taylor
  • Peter Saint-Andre
  • Florian Jensen

Background

Discussion Forums