From a82ec88046c28c52a6be805d52855a657b4e9d13 Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Mon, 3 Mar 2008 16:19:27 +0000 Subject: [PATCH] 0.2 git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1718 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0222.xml | 41 +++++++++++++++++++++++------------------ xep-0223.xml | 27 ++++++++++++++++----------- 2 files changed, 39 insertions(+), 29 deletions(-) diff --git a/xep-0222.xml b/xep-0222.xml index 393c25d8..28e538e0 100644 --- a/xep-0222.xml +++ b/xep-0222.xml @@ -6,12 +6,12 @@
- Persisting Objects via Pubsub - This document specifies protocol semantics for using the XMPP publish-subscribe extension to persistently store semi-public data objects such as public keys and personal profiles. + Best Practices for Persistent Storage of Public Data via Publish-Subscribe + This specification defines best practices for using the XMPP publish-subscribe extension to persistently store semi-public data objects such as public keys and personal profiles. &LEGALNOTICE; 0222 Experimental - Standards Track + Informational Standards JIG Council @@ -25,6 +25,12 @@ TO BE ASSIGNED &stpeter; + + 0.2 + 2008-03-03 + psa +

Removed hokey acronym; changed type to Informational; clarified text.

 + 0.1 2007-08-08 @@ -41,10 +47,9 @@ -

&xep0163; introduced the idea of a virtual &xep0060; service associated with an IM user's bare JID &LOCALBARE;. However, personal eventing (PEP) is not optimized for the persistent storage of semi-public data objects such as public keys or user profiles. Therefore this document defines a set of best practices that enable an IM user to persistently store semi-public data objects at their virtual pubsub service; in effect, we "sub-class" PEP by showing how a particular pubsub node can be configured for persisting objects (we call such a node a "POP node").

+

&xep0163; introduced the idea of a virtual &xep0060; service associated with an IM user's bare JID &LOCALBARE;. However, the default node configuration options associated with PEP nodes are not optimized for the persistent storage of semi-public data objects such as public keys or user profiles. Therefore this document defines a set of best practices that enable IM users to persistently store semi-public data objects at their virtual pubsub service; in effect, we "sub-class" PEP by showing how a particular pubsub node can be configured for persisting objects.

 -

This section provides a friendly introduction to persisting objects via pubsub (a.k.a. POP).

Imagine that you are a Shakespearean character named Juliet and that you want to persistently store information such as your public keys (see &xep0189;) and user profile (see &xep0154;).

We assume that you have three contacts with the following relationship to you:

    @@ -57,7 +62,7 @@ - + julietRSAkey1hash @@ -95,17 +100,17 @@

    Your publish request is a standard pubsub request except that:

    1. The item is persisted (pubsub#persist_items is true).
      2. -
    2. The last published item is never sent (i.e., items are pushed out only when modified).
      3. -
    3. In this case, access is limited to people in your Friends roster group.
      4. +
    4. The last published item is never sent (pubsub#last_published_item is set to "never" so that items are pushed out only when modified).
    -

    If all goes well (see Publishing an Item), your key will be pushed out to all appropriate individuals (in this case only Romeo). In particular, Romeo receives your key because he has auto-subscribed to the virtual pubsub service at your bare JID via a presence subscription and because his &xep0115; data indicated that he is interested in the "http://www.xmpp.org/extensions/xep-0189.html#ns" payload type.

    +

    (In this case, access is limited to people in your Friends roster group.)

    +

    If all goes well (see Publishing an Item), your key will be pushed out to all appropriate individuals (in this case only Romeo). In particular, Romeo receives your key because he has auto-subscribed to the virtual pubsub service at your bare JID via a presence subscription and because his &xep0115; data indicated that he is interested in the "urn:xmpp:tmp:pubkey" payload type.

    - + julietRSAkey1hash @@ -128,7 +133,7 @@ type='headline' id='keyfoo2'> - + julietRSAkey1hash @@ -149,7 +154,7 @@ type='headline' id='keyfoo3'> - + julietRSAkey1hash @@ -170,7 +175,7 @@ -

    Persisting objects via pubsub ("POP") re-uses the concepts already defined in XEP-0060 and XEP-0163. In order to optimize for object persistence instead of transient event notifications, a POP node MUST be configured as follows:

    +

    The best practices described herein re-use the concepts already defined in XEP-0060 and XEP-0163. In order to optimize for object persistence instead of transient event notifications, a node MUST be configured as follows:

    1. Set pubsub#persist_items to true.
    2. Set pubsub#last_published_item to "never".
      3. @@ -183,7 +188,7 @@ - + julietRSAkey1hash @@ -199,12 +204,12 @@ ]]> -

      If the node does not already exist, the virtual pubsubservice MUST create the node. As described in XEP-0163, this "auto-create" feature (defined in XEP-0060) MUST be supported by a PEP service. (Naturally, the account owner's client MAY follow the node creation use case specified in XEP-0060 before attempting to publish an item.)

      +

      If the node does not already exist, the virtual pubsub service MUST create the node. As described in XEP-0163, this "auto-create" feature (defined in XEP-0060) MUST be supported by a PEP service. (Naturally, the account owner's client MAY follow the node creation use case specified in XEP-0060 before attempting to publish an item.)

      In order for the client to reliably persist objects, the virtual pubsub service must also support the "publish-options" feature defined in XEP-0060. Typically, a client will publish with options so that the object is properly persisted.

      - + julietRSAkey1hash @@ -242,8 +247,8 @@

      If the publication logic dictates that event notifications shall be sent, the account owner's server generates notifications and sends them to all appropriate entities as described in the Receiving Event Notifications section of XEP-0163.

      - -

      Before an account owner attempts to complete the use cases defined herein, its client SHOULD verify that the account owner's server supports both PEP and the "publish-options" feature; to do so, it MUST send a &xep0030; information request to the server:

      + +

      Before an account owner attempts to complete the use cases defined herein, its client SHOULD verify that the account owner's server supports both PEP and the "publish-options" feature; to do so, it MUST send a &xep0030; information request to the server (or cache Entity Capabilities information received from the server).

      - Private Information via Pubsub - This document specifies protocol semantics for using the XMPP publish-subscribe extension to persistently store private information such as bookmarks and client configuration options. + Best Practices for Persistent Storage of Private Data via Publish-Subscribe + This specification defines best practices for using the XMPP publish-subscribe extension to persistently store private information such as bookmarks and client configuration options. &LEGALNOTICE; 0223 Experimental - Standards Track + Informational Standards JIG Council @@ -25,6 +25,12 @@ TO BE ASSIGNED &stpeter; + + 0.2 + 2008-03-03 + psa +

      Removed hokey acronym; changed type to Informational; clarified text.

       +       0.1 2007-08-08 @@ -41,13 +47,12 @@ -

      &xep0163; introduced the idea of a virtual &xep0060; service associated with an IM user's bare JID &LOCALBARE;. However, personal eventing (PEP) is not optimized for the persistent storage of data objects that are meant to be accessed only by the account owner, à la &xep0049;. Therefore this document defines a set of best practices that enable a user to persistently store private information at their virtual pubsub service; in effect, we "sub-class" PEP by showing how a particular pubsub node can be configured for storing private information (we call such a node a "PIP node").

      +

      &xep0163; introduced the idea of a virtual &xep0060; service associated with an IM user's bare JID &LOCALBARE;. However, the default configuration of PEP nodes is not optimized for the persistent storage of data objects that are meant to be accessed only by the account owner, à la &xep0049;. Therefore this document defines a set of best practices that enable IM users to persistently store private information at their virtual pubsub service; in effect, we "sub-class" PEP by showing how a particular pubsub node can be configured for storing private data.

       -

      This section provides a friendly introduction to private information via pubsub (a.k.a. PIP).

      Imagine that you are a Shakespearean character named Juliet and that you want to persistently store some private information such as bookmarks (&xep0048;).

      We assume that your server (capulet.lit) supports PEP along with the "publish-options" feature, and that your client discovered that support when you logged in.

      -

      You want to start bookmarking &xep0045; rooms so your client stores that data privately:

      +

      You want to start bookmarking &xep0045; rooms, so your client stores that data privately.

      @@ -81,7 +86,7 @@ ]]>

      Your publish request is a standard pubsub request except that:

        -
      1. The item is persisted (pubsub#persist_items is true).
        2. +
      2. The item is persisted (pubsub#persist_items is set to true).
      3. In this case, access is limited to yourself (the "whitelist" access model defaults to allowing access for the account owner, i.e., you).

      If all goes well (see Storing Data), your bookmarks will be stored and the information will be pushed out to all of your resources (here "balcony" and "chamber").

      @@ -131,10 +136,10 @@       -

      Personal information via pubsub ("PIP") re-uses the concepts already defined in XEP-0060 and XEP-0163. In order to optimize for object persistence of private information instead of transient event notifications related to semi-public data, a PIP node MUST be configured as follows:

      +

      The best practices defined herein re-use the concepts already defined in XEP-0060 and XEP-0163. In order to optimize for object persistence of private information instead of transient event notifications related to semi-public data, a node MUST be configured as follows:

        -
      1. Set pubsub#access_model to "whitelist".
      2. Set pubsub#persist_items to true.
        3. +
      3. Set pubsub#access_model to "whitelist".
       @@ -194,8 +199,8 @@

      If the publication logic dictates that event notifications shall be sent, the account owner's server generates notifications and sends them to all appropriate entities as described in the Receiving Event Notifications section of XEP-0163.

      - -

      Before an account owner attempts to complete any of the use cases defined herein, its client SHOULD verify that the account owner's server supports both PEP and the "publish-options" feature; to do so, it MUST send a &xep0030; information request to the server:

      + +

      Before an account owner attempts to complete any of the use cases defined herein, its client SHOULD verify that the account owner's server supports both PEP and the "publish-options" feature; to do so, it MUST send a &xep0030; information request to the server (or cache Entity Capabilities information received from the server).