From 04d16b2a818b64e80d6fa2c0cdf164ce910818bf Mon Sep 17 00:00:00 2001 From: stpeter Date: Mon, 9 Jan 2012 14:17:06 -0700 Subject: [PATCH] 0.0.2 --- inbox/network.xml | 182 +++++++++++++++++++++++++++++----------------- 1 file changed, 114 insertions(+), 68 deletions(-) diff --git a/inbox/network.xml b/inbox/network.xml index c8d01642..2b6e0d58 100644 --- a/inbox/network.xml +++ b/inbox/network.xml @@ -6,7 +6,7 @@
- XMPP Network Information Sharing + 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; xxxx @@ -21,6 +21,12 @@ NOT_YET_ASSIGNED &stpeter; + + 0.0.2 + 2012-01-09 + psa +

Second draft; added ad-hoc command and defined data sharing via PEP.

 + 0.0.1 2011-12-12 @@ -30,22 +36,23 @@
-

Several services (e.g., at xmpp.org and jabberes.org) have long provided information about public XMPP servers so that end users can more easily find a server to register with, gateways to use, etc. These services tend to rely on humans to gather and in some cases verify the information before providing it via the World Wide Web for use by end users and IM client software. However, relying on humans to gather and verify such information results in significant delays, errors, and out-of-date information.

-

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

+

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:

    -
  • A network information aggregator, xmpp.net (which can be thought of as an information sink)
    • -
  • A public XMPP server, jabber.org (which can be thought of as an information source).
    • +
  • A server directory: xmpp.net
    • +
  • A public XMPP service: jabber.org

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

| @@ -58,7 +65,7 @@ Aggregator Server |----presence subscribe------>| |<---presence subscribed------| | | - | [third, aggregator | + | [third, directory | | gathers server data] | | | |----disco info request------>| @@ -68,19 +75,17 @@ Aggregator Server |<---vcard response-----------| | | ]]> - - - -

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

- +

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

+ - ]]> - + - ]]> - + ]]> + - -

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

- +

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

+ - ]]> -

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

- +

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

+ - ]]> -

The aggregator also sends a subscription request to the server.

- +

The aggregator also sends a subscription request to the server.

+ - ]]> -

The server then approves that subscription request, as well.

- +

The server then approves that subscription request, as well.

+ - ]]> - + ]]> + - -

After the subscription handshake has been completed, the aggregator 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 aggregator sends a service discovery information request to the server.

- +

After the subscription handshake has been completed, the aggregator 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 aggregator 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 aggregator 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 aggregator 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;.

- +

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 aggregator 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 aggregator 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;.

+ - ]]> - + - ]]> -

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 URL (<registration xmlns='urn:xmpp:vcard:registration'/>)
    • -
+ ]]> +

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 URL (<registration xmlns='urn:xmpp:vcard:registration'/>)
    • +
+ + +

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/ + + + + + + + ]]> + +

Because a network information aggregator does not know about an XMPP server unless the administrator of the server initiates a presence subscription to the aggregator, 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.