From 668990211c9a3518364305c0dc11323a2a91130b Mon Sep 17 00:00:00 2001 From: stpeter Date: Tue, 10 Jan 2012 12:27:16 -0700 Subject: [PATCH] 0.1 --- xep-0309.xml | 31 +++++++++++++++++++------------ 1 file changed, 19 insertions(+), 12 deletions(-) diff --git a/xep-0309.xml b/xep-0309.xml index aeec12d5..7dee54ec 100644 --- a/xep-0309.xml +++ b/xep-0309.xml @@ -9,7 +9,7 @@ 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 + 0309 Experimental Standards Track Standards @@ -21,6 +21,12 @@ NOT_YET_ASSIGNED &stpeter; + + 0.1 + 2012-01-10 + psa +

Initial published version.

 + 0.0.3 2012-01-09 @@ -52,6 +58,7 @@
  • A server directory: xmpp.net
  • A public XMPP service: jabber.org
    • +

    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.

    -

    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 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 aggregator as described in XEP-0267.

    +

    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 aggregator approves it.

    +

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

    ]]> -

    The aggregator also sends a subscription request to the server.

    +

    The directory also sends a subscription 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.

    +

    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 aggregator sends a service discovery information request to the server.

    +

    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 aggregator MAY also gather disco#items data about components and other services associated with the base XMPP server at a domain.

    +

    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 aggregator sends a vCard information request to the server.

    +

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

    -

    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.

    +

    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 network information aggregator to explicitly indicate that it aggregates information obtained from XMPP servers that contact it.

    +

    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.

     @@ -353,7 +360,7 @@ Directory Server

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

     -

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

    +

    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.