%ents; ]>
Service Directories This specification shows how to combine and extend a number of existing XMPP protocols for improved sharing of information about XMPP servers. &LEGALNOTICE; 0309 Experimental Standards Track Standards Council XMPP Core NOT_YET_ASSIGNED &stpeter; 0.2 2012-01-25 psa

Added vCard extension for certification authority information; showed how to include software name in a vCard; recommended that the CA information and software name be added by the service directory, not included by the server itself.

 0.1 2012-01-10 psa

Initial published version.

 0.0.3 2012-01-09 psa

Defined ad-hoc command for triggering outbound presence subscription.

 0.0.2 2012-01-09 psa

Defined data sharing via PEP.

 0.0.1 2011-12-12 psa

First draft.

Several directories (e.g., at xmpp.org and jabberes.org) have long provided information about public XMPP services so that end users can more easily find servers to register with, add-on components to use for features such as &xep0045;, etc. These service directories tend to rely on humans to gather and in some cases verify the information they publish before providing it via the World Wide Web or the XMPP network for use by end users and IM client software. However, relying on humans to gather and verify such information can result in significant delays and errors. It would be better to automate the information-gathering functions as much as possible.

This document shows how to combine and extend a number of existing XMPP protocols for (mostly) automated gathering of information about public XMPP services. Widespread deployment of this specification will result in more timely, accurate information about the services available on the XMPP network.

The following scenario involves two entities:

Note: Although the entity that gathers information for a directory could be a client or a component, here we assume that it is a server ("xmpp.net").

These two entities use &xep0267;, &xep0030;, and &xep0292; in the following ways.

| | | | [second, entities become | | "buddies" per XEP-0267] | | | |<---presence subscribe-------| |----presence subscribed----->| |----presence subscribe------>| |<---presence subscribed------| | | | [third, directory | | gathers server data] | | | |----disco info request------>| |<---disco info response------| | | |----vcard request----------->| |<---vcard response-----------| | | ]]>

In order to determine the exact identity of the directory, the server sends a service discovery information request to the directory.

]]> ]]>

If the server wishes to have its information aggregated, it sends a presence subscription request to the directory as described in XEP-0267.

]]>

Upon receiving such the presence subscription request, the directory approves it.

]]>

The directory also sends a subscription request to the server.

]]>

The server then approves that subscription request, as well.

]]>

The server administator needs a way to trigger the server to send a presence subscription to the directory. This can be done by using &xep0050; as in &xep0133;. Therefore we define a new server administration use case. The command node for this use case SHOULD be "http://jabber.org/protocol/admin#server-buddy".

A sample protocol flow for this use case is shown below.

]]>

Unless an error occurs, the service SHOULD return the appropriate form.

Adding a Server Buddy Fill out this form to add a "server buddy". http://jabber.org/protocol/admin ]]> http://jabber.org/protocol/admin xmpp.net ]]> ]]>

After the subscription handshake has been completed, the directory queries the server for information. There are two aspects: service discovery information and vCard information.

In order to determine the exact identity of the server, the directory sends a service discovery information request to the server.

]]> ]]>

Note: If the server is a public node on the XMPP network, it includes a service discovery feature of "urn:xmpp:public-server". This feature is defined below.

Note: If the server allows &xep0077;, it includes a service discovery feature of "jabber:iq:register". If the server does not allow in-band registration but allows account registration at a website, it includes the registration URL in its vCard as described below.

The foregoing examples show the gathering of disco#info data (identity and supported features). An directory MAY also gather disco#items data about components and other services associated with the base XMPP server at a domain.

In order to gather additional information about the server, the directory sends a vCard information request to the server.

Note: Because vCard4 enables the XMPP community to more easily define extensions to vCard (e.g., for registration URLs), it is RECOMMENDED for servers to support &xep0292; in addition to, or instead of, &xep0054;.

]]> jabber.org IM service http://www.jabber.org/ 1 en IA US xmpp@jabber.org xmpp:jabber.org http://www.jabber.org/images/logo.png geo:42.25,-91.05 America/Chicago application https://register.jabber.org/ ]]>

It is RECOMMENDED for public server vCards to include the following information:

  • A friendly name for the service (<fn/>)
  • A URL for general information about the service (<url/>)
  • The country where the service is located (<adr><country/></adr>)
  • An email address or alias for contacting the administrators (<email/>)
  • The XMPP address for the service (<impp/>)
  • A vCard KIND of "application" (<kind><text>application</text></kind>)

It is OPTIONAL for public server vCards to include the following information:

  • Preferred language of communication with the administrators (<lang/>)
  • Region where the service is located (<adr><region/></adr>)
  • Logo for the service (<logo/>)
  • Geographical coordinates for the service (<geo/>)
  • Registration URI (<registration xmlns='urn:xmpp:vcard:registration:1'/> and its <uri/> child)
  • Certification authority name and URI (<ca xmlns='urn:xmpp:vcard:ca:0'/> and its <name/> and <uri/> children)
  • Software name (<name/> element qualified by the 'jabber:iq:version' namespace defined)

It is best for the server directory to discover the last two elements in-band (by means of TLS negotiation and &xep0092;), then add them to the contact vCard as described in the next section.

Currently, service directories such as xmpp.org and jabberes.org publish their information on the World Wide Web, typically via a human-friendly website and sometimes also via machine-readable files at a well-known URI for use by IM clients to pre-populate drop-down boxes showing XMPP servers that allow in-band registration. (For example, the xmpp.org service publishes a file listing registered public servers using the &xep0030; format.)

In addition to publishing such information on the web, this document defines a second publishing path: the XMPP network itself. The directory can do this by creating a public &xep0060; node at the directory's bare domain (e.g., xmpp.net) that pushes data in the vCard4 format shown above, as described more fully in XEP-0292. Other entities can then subscribe to this node to receive updated information about services that are added to or removed from the directory.

For example, the following stanza shows an information push from the xmpp.net directory about the jabber.org service, sent to a subscriber at example.com.

jabber.org IM service http://www.jabber.org/ 1 en IA US xmpp@jabber.org xmpp:jabber.org http://www.jabber.org/images/logo.png geo:42.25,-91.05 America/Chicago application https://register.jabber.org/ StartSSL http://www.startssl.com/ Isode M-Link ]]>

Because a service directory does not know about an XMPP server unless the administrator of the server initiates a presence subscription to the directory, information leakage is minimized.

Use of the "urn:xmpp:public-server" service discovery feature provides a way for an XMPP server to explicitly indicate that its information is public.

Use of the "directory/server" service discovery identity provides a way for a service directory to explicitly indicate that it gathers service information obtained from XMPP servers that contact it.

This document requires no interaction with &IANA;.

This document specifies that the 'urn:xmpp:vcard:registration' namespace is used to qualify the XMPP-specific vCard4 extension for account registration URLs.

The XMPP Registrar shall add this namespace to its registry at &NAMESPACES;.

This document specifies that a service directory is identified by the "directory" category and the "server" type within XMPP Service Discovery.

The XMPP Registrar shall add the "server" type to the "directory" category already listed in the registry at &DISCOCATEGORIES;. The registration is as follows.

directory server A directory of XMPP servers [TBD] ]]>

This document specifies that a public server on the XMPP network is identified by the "urn:xmpp:public-server" Service Discovery feature.

The XMPP Registrar shall add this feature to its registry at &DISCOFEATURES;. The registration is as follows.

urn:xmpp:public-server The server is a public node on the XMPP network [TBD}/doc> ]]> ]]> ]]>