JEPs That Volity Uses

Jabber uses an RFC-like system to document suggested extensions to the core XMPP protocol. Each of these documents is called a Jabber Enhancement Proposal, or a JEP, and is identifiable by a unique serial number (in the form "JEP-NNNN"). As with RFCs, JEPs keep their tenuous-sounding name even after they are recognized as official protocol extensions by the Jabber Council.

Here are the JEPs that can be found in use by Volity:

• [JEP-0004: Data Forms] Used when the server needs to send configuration information, a bot menu, or the like to a client.
• GameServers and ClientApplications.
• GameBrowser, the UI finder, and other services. See also ServiceDiscovery.
• GameTables.
• [JEP-0078: Non-SASL Authentication] This is the de facto standard for Jabber authentication (jabber:iq:auth), but it isn't included in the IETF standard drafts for various reasons. Pretty much every current Jabber library already supports this, both on the client and server side, but I'm listing it here for completeness. Volity implementations probably won't be supporting SASL any time soon. --dougo
• Entity Capabilities.
• [JEP-0128] Allows data forms to exist within service-discovery responses, allowing Volity entities to reveal a wide variety of information about themselves when browsed via disco.