Procedure for accepting/progressing Extension proposals
A requesting entity may want to discover information about another entity on the network., The target entity's identity, The features offered and protocols supported by the target entity.
requesting entity MUST send an IQ stanza of type "get",
Announce through XEP-0030, feature of "http://jabber.org/protocol/chatstates":
Discovering Items, Commands, Command Information i.e. 'config'
This specification defines an XMPP protocol extension for exchanging contact list items, including the ability to suggest whether the item is to be added, deleted, or modified in the contact list of the recipient, as well as the suggested roster group for the item.
This specification defines semantics for using the XMPP publish-subscribe protocol to broadcast state change events associated with an instant messaging and presence account. This profile of pubsub therefore enables a standard XMPP user account to function as a virtual pubsub service, easing the discovery of syndicated data and event notifications associated with such an account.
This specification defines an XMPP protocol extension for initiating and managing peer-to-peer media sessions between two XMPP entities in a way that is interoperable with existing Internet standards. The protocol provides a pluggable model that enables the core session management semantics (compatible with SIP) to be used for a wide variety of application types (e.g., voice chat, video chat, file transfer) and with a wide variety of transport methods (e.g., TCP, UDP, ICE, application-specific transports).
This specification defines how to communicate over local or wide-area networks using the principles of zero-configuration networking for endpoint discovery and the syntax of XML streams and XMPP messaging for real-time communication. This method uses DNS-based Service Discovery and Multicast DNS to discover entities that support the protocol, including their IP addresses and preferred ports. Any two entities can then negotiate a serverless connection using XML streams in order to exchange XMPP message and IQ stanzas.
This specification defines an XMPP protocol extension for message receipts, whereby the sender of a message can request notification that it has been received by the intended recipient.
This specification defines an XMPP protocol extension for communicating the fact that an XML stanza has been delivered with a delay, for example because a message has been stored on a server while the intended recipient was offline or because a message is contained in the history of a multi-user chat room.
This specification defines an XMPP protocol extension for generic publish-subscribe functionality. The protocol enables XMPP entities to create nodes (topics) at a pubsub service and publish information at those nodes; an event notification (with or without payload) is then broadcasted to all entities that have subscribed to the node. Pubsub therefore adheres to the classic Observer design pattern and can serve as the foundation for a wide variety of applications, including news feeds, content syndication, rich presence, geolocation, workflow systems, network management systems, and any other application that requires event notifications
This document defines an XMPP protocol extension for broadcasting and dynamically discovering client, device, or generic entity capabilities. In order to minimize network impact, the transport mechanism is standard XMPP presence broadcast (thus forestalling the need for polling related to service discovery data), the capabilities information can be cached either within a session or across sessions, and the format has been kept as small as possible.
Use Cases, Advertising Capabilities, Discovering Capabilities
This specification documents the existing protocol used for communication between servers and "external" components over the Jabber network
Client, Multiple resources (e.g., devices or locations) MAY connect simultaneously to a server on behalf of each authorized client, with each resource differentiated by the resource identifier of an XMPP address (e.g., <node@domain/ home> vs. <node@domain/work>), RECOMMENDED port for connections between a clientand a server is 5222
Stanza, Stanzas, <presence/>, Basic "broadcast" or "publish/subscribe", Types, 'unavailable', Signals that the entity is no longer available for communication., 'subscribe', The sender wishes to subscribe to the recipient's presence., 'subscribed', The sender has allowed the recipient to receive their presence., 'unsubscribe', The sender is unsubscribing from another entity's presence., 'probe', A request for an entity's current presence; SHOULD be generated only by a server on behalf of a user., 'error', An error has occurred regarding processing or delivery of a previously-sent presence stanza., 'unsubscribed', The subscription request has been denied or a previously-granted subscription has been cancelled., Reqs, In general, a publishing entity SHOULD send a presence stanza with no 'to' attribute, in which case the server to which the entity is connected SHOULD broadcast or multiplex that stanza to all subscribing entities., However, a publishing entity MAY also send a presence stanza with a 'to' attribute, in which case the server SHOULD route or deliver that stanza to the intended recipient., Child Elements, <show/>, away, chat, dnd, xa, <status/>, Human readable, <priority/>, <message/>, PUSH behavior, Types, 'chat', 'error', 'groupchat', 'headline', 'normal', Child Elements, <subject/>, Human readable, <body/>, Human readable, <thread/>, Non-human readable, <iq/>, Info/Query: request-response mechanism, interaction is tracked by the requesting entity through use of the 'id' attribute., 'get', 'set', 'result', 'error', Encapsulated through XML stream, common attributes, 'to', 'from', 'id', 'type', 'xml:lang', errors, <bad-request/>, <conflict/>, <feature-not-implemented/>, <forbidden/>, <gone/>, <internal-server-error/>, <item-not-found/>, <jid-malformed/>, <not-acceptable/>, <not-allowed/>, <not-authorized/>, <payment-required/>, <recipient-unavailable/>, <redirect/>, <registration-required/>, <remote-server-not-found/>, <remote-server-timeout/>, <resource-constraint/>, <service-unavailable/>, <subscription-required/>, <undefined-condition/>, <unexpected-request/>
XML Stream, attributes, 'to', 'from', 'id', 'receiver' to 'initiating' "session key", 'xml:lang', 'version', error conditions, <bad-format/>, <bad-namespace-prefix/>, <conflict/>, <connection-timeout/>, <host-gone/>, <host-unknown/>, <improper-addressing/>, <internal-server-error/>, <invalid-from/>, <invalid-id/>, <invalid-namespace/>, <invalid-xml/>, <not-authorized/>, <policy-violation/>, <remote-connection-failed/>, <resource-constraint/>, <restricted-xml/>, <see-other-host/>, <system-shutdown/>, <undefined-condition/>, <unsupported-encoding/>, <unsupported-stanza-type/>, <unsupported-version/>, <xml-not-well-formed/>