Agent Information

%ents; ]>

Agent Information This specification provides canonical documentation of the obsolete Agent Information namespace. Note: This document has been superseded by XEP-0030: Service Discovery. &LEGALNOTICE; 0094 Obsolete Historical Standards JIG XMPP Core XEP-0030 iq-agents &stpeter; 0.3 2003-10-08 psa Per a vote of the Jabber Council, changed status to Obsolete. The protocol described herein is accurately defined but actively deprecated in favor of Service Discovery (XEP-0030). 0.2 2003-09-24 psa Added 'irc' to the values for the <service/> element; made several small textual changes. 0.1 2003-05-23 psa Initial version.

Over the years there have been three different protocols used in the Jabber community to discover information about other entities on the network. The most recent protocol, and the only one that is standards-track, is &xep0030;. The protocol prior to Service Discovery was &xep0011;. Before Jabber Browsing, there was the 'jabber:iq:agents' namespace. This specification provides historical documentation for the Agent Information protocol.

Note well that the Agent Information protocol is deprecated; applications desiring such functionality SHOULD implement Service Discovery. This specification is provided only in order to ensure complete documentation of earlier protocols.

The 'jabber:iq:agents' namespace was used to obtain a list of entities associated with another Jabber Entity; most commonly, the list of trusted services associated with a specific host.

When 'jabber:iq:agents' is used, information about available agents properties is contained within a <query/> element that is scoped by the 'jabber:iq:agents' namespace. The reply to a request of type "get" in the 'jabber:iq:agents' namespace contains zero or more <agent/> elements. The <agent/> element has a required 'jid' attribute that contains the Jabber Identifier of each agent. The <agent/> element in turn may contain the following children:

name - a natural-language name for the service
description - a short phrase describing the service
transport - inclusion of this empty element signals that the service is a gateway to a non-Jabber instant messaging system
groupchat - inclusion of this empty element signals that the service is multi-user chat service
service - the CDATA of this element specifies the type of gateway (aim, icq, irc, msn, yahoo), the type of conferencing service (public or private), or user directory (jud); these values were never standardized and are not registered with the XMPP Registrar
register - inclusion of this empty element signals that the service supports registration
search - inclusion of this empty element signals that the service supports searching

]]> Jabber User Directory jud Conferencing Service public ]]>

There are no security features or concerns related to this proposal.

This document requires no interaction with &IANA;.

No action on the part of the ®ISTRAR; is necessary as a result of this document, since 'jabber:iq:agents' is already a registered namespace.

]]>