Abstract: | This specification provides canonical documentation of the obsolete Agent Information namespace. Note: This document has been superseded by XEP-0030: Service Discovery. |
Author: | Peter Saint-Andre |
Copyright: | © 1999 – 2018 XMPP Standards Foundation. SEE LEGAL NOTICES. |
Status: | Obsolete |
Type: | Historical |
Version: | 0.3 |
Last Updated: | 2003-10-08 |
WARNING: This document has been obsoleted by the XMPP Standards Foundation. Implementation of the protocol described herein is not recommended. Developers desiring similar functionality are advised to implement the protocol that supersedes this on (XEP-0030).
1. Introduction
2. Definition
3. Examples
4. Security Considerations
5. IANA Considerations
6. XMPP Registrar Considerations
7. XML Schema
Appendices
A: Document Information
B: Author Information
C: Legal Notices
D: Relation to XMPP
E: Discussion Venue
F: Requirements Conformance
G: Notes
H: Revision History
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 Service Discovery (XEP-0030) [1]. The protocol prior to Service Discovery was Jabber Browsing (XEP-0011) [2]. 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:
Example 1. Request for Agents List
<iq id='agents1' type='get' to='shakespeare.lit'> <query xmlns='jabber:iq:agents'/> </iq>
Example 2. Reply Containing Agents List
<iq to='juliet@capulet.com/balcony' from='shakespeare.lit' type='result' id='agents1'> <query xmlns='jabber:iq:agents'> <agent jid='users.shakespeare.lit'> <name>Jabber User Directory</name> <service>jud</service> <search/> <register/> </agent> <agent jid='chat.shakespeare.lit'> <name>Conferencing Service</name> <service>public</service> <groupchat/> </agent> </query> </iq>
There are no security features or concerns related to this proposal.
This document requires no interaction with the Internet Assigned Numbers Authority (IANA) [3].
No action on the part of the XMPP Registrar [4] is necessary as a result of this document, since 'jabber:iq:agents' is already a registered namespace.
<?xml version='1.0' encoding='UTF-8'?> <xs:schema xmlns:xs='http://www.w3.org/2001/XMLSchema' targetNamespace='jabber:iq:agents' xmlns='jabber:iq:agents' elementFormDefault='qualified'> <xs:element name='query'> <xs:complexType> <xs:sequence minOccurs='0'> <xs:element ref='agent' minOccurs='0' maxOccurs='unbounded'/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name='agent'> <xs:complexType> <xs:sequence> <xs:element ref='name' minOccurs='0' maxOccurs='1'/> <xs:element ref='description' minOccurs='0' maxOccurs='1'/> <xs:element ref='transport' minOccurs='0' maxOccurs='1'/> <xs:element ref='groupchat' minOccurs='0' maxOccurs='1'/> <xs:element ref='service' minOccurs='0' maxOccurs='1'/> <xs:element ref='register' minOccurs='0' maxOccurs='1'/> <xs:element ref='search' minOccurs='0' maxOccurs='1'/> </xs:sequence> <xs:attribute name='jid' type='xs:string' use='required'/> </xs:complexType> </xs:element> <xs:element name='name' type='xs:string'/> <xs:element name='description' type='xs:string'/> <xs:element name='transport'/> <xs:element name='groupchat'/> <xs:element name='service' type='xs:string'/> <xs:element name='register'/> <xs:element name='search'/> </xs:schema>
Series: XEP
Number: 0094
Publisher: XMPP Standards Foundation
Status:
Obsolete
Type:
Historical
Version: 0.3
Last Updated: 2003-10-08
Approving Body: XMPP Council
Dependencies: XMPP Core
Supersedes: None
Superseded By: XEP-0030
Short Name: iq-agents
Source Control:
HTML
This document in other formats:
XML
PDF
Email:
xsf@stpeter.im
JabberID:
peter@jabber.org
URI:
http://stpeter.im/
The Extensible Messaging and Presence Protocol (XMPP) is defined in the XMPP Core (RFC 6120) and XMPP IM (RFC 6121) specifications contributed by the XMPP Standards Foundation to the Internet Standards Process, which is managed by the Internet Engineering Task Force in accordance with RFC 2026. Any protocol defined in this document has been developed outside the Internet Standards Process and is to be understood as an extension to XMPP rather than as an evolution, development, or modification of XMPP itself.
The primary venue for discussion of XMPP Extension Protocols is the <standards@xmpp.org> discussion list.
Discussion on other xmpp.org discussion lists might also be appropriate; see <http://xmpp.org/about/discuss.shtml> for a complete list.
Errata can be sent to <editor@xmpp.org>.
The following requirements keywords as used in this document are to be interpreted as described in RFC 2119: "MUST", "SHALL", "REQUIRED"; "MUST NOT", "SHALL NOT"; "SHOULD", "RECOMMENDED"; "SHOULD NOT", "NOT RECOMMENDED"; "MAY", "OPTIONAL".
1. XEP-0030: Service Discovery <https://xmpp.org/extensions/xep-0030.html>.
2. XEP-0011: Jabber Browsing <https://xmpp.org/extensions/xep-0011.html>.
3. The Internet Assigned Numbers Authority (IANA) is the central coordinator for the assignment of unique parameter values for Internet protocols, such as port numbers and URI schemes. For further information, see <http://www.iana.org/>.
4. The XMPP Registrar maintains a list of reserved protocol namespaces as well as registries of parameters used in the context of XMPP extension protocols approved by the XMPP Standards Foundation. For further information, see <https://xmpp.org/registrar/>.
Note: Older versions of this specification might be available at http://xmpp.org/extensions/attic/
END